Hi Ross, make sure that elasticsearch_network_host (see https://github.com/Graylog2/graylog2-server/blob/2.0.0/misc/graylog.conf#L187-L194 and http://docs.graylog.org/en/2.0/pages/upgrade.html#default-network-host) is set to an IP address (or host name) which the other Elasticsearch and Graylog nodes can access.
Additionally make sure that the two Graylog nodes are using the same MongoDB database and the same password_secret (see https://github.com/Graylog2/graylog2-server/blob/2.0.0/misc/graylog.conf#L9-L11 ). Cheers, Jochen On Tuesday, 10 May 2016 23:17:45 UTC+2, Ross wrote: > > I've got a graylog cluster set up with two graylog server nodes on AWS. > Both of the nodes function fine on their own, but don't see each other. The > rest API endpoints are bound to their internal 10.x endpoint and both hosts > can communicate with each other. When I look at the elasticsearch cluster, > I see all the nodes I expect- three ES nodes, two Graylog nodes. In the > logs, I can even see the other node show up in the Elasticsearch cluster > join message. > > I can't specifically figure out where to start since neither of the nodes > are complaining about anything. Does anyone have advice on how to > troubleshoot graylog node connectivity? Not a whole lot to go on in the > docs. > -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/d3a87963-c4fd-4c73-94fe-81834a5a6420%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
