Hi Ariel, just for reference, I'll paraphrase the explanation from IRC:
Each Graylog node "registers" itself (node id, URI to the Graylog REST API, > timestamp of the last heartbeat) in MongoDB (see the nodes collection). > The timeout/cleanup interval is quite aggressive (2s, see > stale_master_timeout > <https://github.com/Graylog2/graylog2-server/blob/2.0.3/misc/graylog.conf#L371-L372>), > > so if your system clock is off by a minute or so, the information in > MongoDB will be considered stale and the node is trying to re-register > itself. Cheers, Jochen On Monday, 20 June 2016 18:13:52 UTC+2, Ariel Godinez wrote: > > Hello, > > I am getting the following related warnings from the graylog server every > 5 to 30 minutes. > > Warning (from graylog system messages page) : *Notification condition > [NO_MASTER] has been fixed.* > Warning (from graylog server logs): *WARN : > org.graylog2.periodical.NodePingThread - Did not find meta info of this > node. Re-registering.* > > Upon googling these warnings I saw that multiple people were able to get > these warnings to stop after installing NTP and synchronizing their > system(s). > > I am running a single node configuration ( *my graylog server.conf: > is_master = true* ) ,have installed NTP, and configured it. Graylog is > working as expected but I just wanted to see if anyone had an idea as to > what might be causing these annoying warnings and how I could get them to > stop. > > Any input would be much appreciated. > > System: > Oracle Linux Server release 6.5 > Red Hat Enterprise Linux Server release 6.5 (Santiago) > > Thanks, > Ariel Godinez > > > > -- 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/824dddee-a881-439b-a3ff-4de8a3663785%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
