Skip to main content
February 27, 2025
Question

Tomcat 401 Unauthorized - Waiting for Appian component Search Server to be healthy...

  • February 27, 2025
  • 4 replies
  • 0 views

Upgrading to Appian version 24.4 and cannot get the Tomcat server to initialize completely.

The following is a snippet from the tomcat-stdout.log:

"host [http://localhost:9200], URI [/], status line [HTTP/1.1 401 Unauthorized]
{"error":{"root_cause":[{"type":"security_exception","reason":"missing authentication credentials for REST request [/]","header":{"WWW-Authenticate":["Basic realm=\"security\", charset=\"UTF-8\"","ApiKey"]}}],"type":"security_exception","reason":"missing authentication credentials for REST request [/]","header":{"WWW-Authenticate":["Basic realm=\"security\", charset=\"UTF-8\"","ApiKey"]}},"status":401}"

.....

[wait-for-component] INFO  com.appiancorp.common.startup.WaitForStatefulComponents - Waiting for Appian component Search Server to be healthy...

I've ensured the apiKeys match in <APPIAN_HOME>/conf/custom.properties and <APPIAN_HOME>/search-server/conf/custom.properties as identified in KB-2227 regarding apiKey mismatch

Does anyone have any suggestions on what else I can look at?

Thanks!

4 replies

davidj137213
February 27, 2025

Is search server running and healthy?

February 27, 2025

From what I can tell, yes.

search-server.log snippet

[INFO ][org.elasticsearch.cluster.routing.allocation.AllocationService] [localhost] current.health="GREEN" message="Cluster health status changed from [RED] to [GREEN] (reason: [shards started [[.security-7][0]]])." previous.health="RED" reason="shards started [[.security-7][0]]"

I should have prefaced my initial question with the fact that I'm a Red Hat Admin who has been thrust into getting this running. I have ZERO prior experience with any Appian software, so forgive any ignorant questions I have

davidj137213
February 27, 2025

Exceute status.bat located inside services/bin folder and share results.

The syntax is status.bat -p <PASSWORD>