ERROR: Failed to successfully connect to ElasticSearch. Make sure your cluster status is not red and that ElasticSearch is working correctly

Question

I referenced Configure graylog2 server using elasticsearch in a stray machine and I have the correct version of ElasticSearch.

I also added the correct options for Graylog2 and ElasticSearch according to the tutorial .

ERROR: Could not successfully connect to ElasticSearch. Check that your cluster state is not RED and that ElasticSearch is running properly. Need help? * Official documentation: http://support.torch.sh/help/kb * Mailing list: http://support.torch.sh/help/kb/general/forums-mailing-list * Issue tracker: http://support.torch.sh/help/kb/general/issue-trackers * Commercial support: http://www.torch.sh/ But we also got some specific help pages that might help you in this case: * http://support.torch.sh/help/kb/graylog2-server/configuring-and-tuning-elasticsearch-for-graylog2-v0200 Terminating. :( 

I still get this error on startup:

 sudo java -jar /opt/graylog2-server/graylog2-server.jar --debug 

I also checked that ElasticSearch is working correctly -

 central@central :~$ curl -XGET 'http://127.0.0.1:9200/_cluster/health?pretty=true' { "cluster_name" : "graylog2", "status" : "green", "timed_out" : false, "number_of_nodes" : 1, "number_of_data_nodes" : 1, "active_primary_shards" : 0, "active_shards" : 0, "relocating_shards" : 0, "initializing_shards" : 0, "unassigned_shards" : 0 } 

Any suggestions on what I should do? I do not understand what the problem is.

Answer 1

I got a setup to run with the following additions -

 # /etc/elasticsearch/elasticsearch.yml cluster.name: graylog2 node.master: true node.data: true bootstrap.mlockall: true ES_HEAP_SIZE: 8192 (@ 16GB memory) discovery.zen.ping.multicast.enabled: false discovery.zen.ping.unicasts.hosts: ["127.0.0.1", "SERVER IP"] # /etc/graylog2.conf elasticsearch_discovery_zen_ping_multicast_enabled = false elasticsearch_discovery_zen_ping_unicast_hosts = IP_ARR:9300 

Answer 2

I am not sure why question A23 is ignored. I also failed to start graylog2-server. The key seems to set the value of elasticsearch_discovery_zen_ping_unicast_hosts to a valid IP set.

This, of course, is not mentioned in the graylog docs as a parameter that should be changed in the graylog2.conf file:

http://www.graylog2.org/resources/documentation/setup/server

This is a bit annoying.