You are currently reviewing an older revision of this page.
Following a restart of the search-servers and application servers in an HA/Distributed environment with multiple application servers, some subset of users experience an HTTP Status 404 - Not Found error when attempting to access the environment:
In the application server logs for at least one of the application servers, the below error will be displayed during the application server's startup:
YYYY-MM-DD HH:MM:SS SEVERE [localhost-startStop-X] org.apache.catalina.core.StandardContext.listenerStart Exception sending context initialized event to listener instance of class [com.appiancorp.common.startup.WaitForStatefulComponentsListener] java.lang.reflect.UndeclaredThrowableException... 26 more Caused by: MasterNotDiscoveredException[null]
No application server logging will occur following the startup.
For the same application server node where the above error message is printed, the below message is printed repeatedly in the search-server.log located in the <APPIAN_HOME>/logs/search-server directory:
[WARN ][org.elasticsearch.discovery.zen.ZenDiscovery] [unknown] not enough master nodes discovered during pinging...
Followed by the below messages:
[DEBUG][org.elasticsearch.action.admin.cluster.health.TransportClusterHealthAction] [unknown] no known master node, scheduling a retry...[INFO ][com.appian.es.logging.HealthStatusLoggingListener] [unknown] Cluster health changed for [cluster name=appian-search-cluster]. Status changed from [none] to [RED]. Current cluster information: [status=RED]...
This behavior results from the Appian Web application failing to successfully deploy into Tomcat. This is a result of the
This section is required for this template and contains the steps to resolve the issue. If an issue in an article is solved by a hotfix and/or major version of Appian, use the following language to indicate that:
If there is a product issue with Engineering that is open and a workaround for that issue exists, include it in the Action section until the fix is available. After the fix is made available, use that as a workaround instead.
Otherwise, the content in this section should wholly solve a customer’s issue without producing any undesirable side effects. If there is at least one valid action that doesn’t cause undesirable side effects, all other actions with negative side effects should go in the Workaround section.
If there is no action or workaround that resolves the issue, use the following language:
This section is optional and should only be used as an alternative action if there is a massive technical debt associated with performing the action in the above section for customers (such as upgrading). It can also be used if there is a solution to the issue in the article but is more inconvenient to implement or it causes other undesirable behavior and wouldn’t warrant being an action.
This section includes any relevant version information for Appian or other third/party configurations. Some examples of valid affected versions are as follows:
Last Reviewed: Month YYYY