I'm having a similar issue. I have things to a point where neither instance sees more than one "node". Both are seeing the elasticsearch indicies (one local, one not). The master node seems mostly operational. I set up a "slave" node for only one reason. The Graylog user levels made it necessary to add another instance so users have full search capability but no way to delete an index by mistake. It appears things have changed and that strategy won't work anymore. The only step you mention that I haven't done is clone the mongo. Right now my slave instance sees the indices, but none of the searches ever load, and I see errors that no master is selected, along with can't retrieve retention or rotation config. I presume I'm reaching elasticsearch, but not the master graylog? I see no connection errors in either mongo log.
On Wednesday, May 11, 2016 at 12:32:27 AM UTC-7, Jochen Schalanda wrote: > > 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 > > > -- 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 graylog2+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/ba8884d7-041f-4021-9b7a-ecbbf28f76f2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
