Elastic Search is Not Starting

Document ID : KB000107857
Last Modified Date : 09/08/2018
Show Technical Document Details
Issue:
After logging into AXA, most dashboards do not display data. The Elastic Search process is not starting. 
Environment:
AXA On Premise 17.3.x
Cause:
Reviewing the /aoPlatform/jarvis/logs/elasticsearch.log, the following error is observed...
[WARN ][o.e.b.ElasticsearchUncaughtExceptionHandler] [MASTER-DATA-<hostname>] uncaught exception in thread [main]
org.elasticsearch.bootstrap.StartupException: BindTransportException[Failed to bind to [9300-9400]]; nested: BindException[Cannot assign requested address];
    ...
Caused by: org.elasticsearch.transport.BindTransportException: Failed to bind to [9300-9400]
    ...
Caused by: java.net.BindException: Cannot assign requested address

This error occurs if the Elastic Search process cannot bind to the host or ip address assigned in 
 /aoPlatform/jarvis/elasticsearch-<version>/config/elasticsearch.yml. 
Resolution:
To correct this issue...

1 - Verify the assigned ports mentioned in the error message, "Failed to bind to [9300-9400]", are not in use on the server.
2 - Try updating  /aoPlatform/jarvis/elasticsearch-<version>/config/elasticsearch.yml 's network.host to 0.0.0.0

# Set the bind address to a specific IP (IPv4 or IPv6):
#
  network.host: 0.0.0.0

3 -Then restart Elastic Search