I'm still getting the same notifications after upgrading to Graylog2 0.20.0-rc.3.
Cheers, Jochen On 13.02.2014 16:05, Lennart Koopmann wrote: > Thanks for your reports! I think this might be related to not waiting > for a wrong MongoDB write concern and your systems being too fast. ;) > Please don't press the TURBO button on your PC!! > > Fix will be included in rc.3 later today. :) > > On Thu, Feb 13, 2014 at 2:32 PM, Jochen Schalanda <joc...@schalanda.name> > wrote: >> Hi, >> >> I get the same notification on a single-node setup (Graylog2 >> 0.20.0-rc.2) and the notification reappears every few minutes after >> closing it. >> >> But there doesn't seem to be a problem (at least none I am aware of). >> Everything is working as it should. >> >> I have been running Graylog2 0.20.0-rc.1 on the same machine before and >> upgraded to Graylog2 0.20.0-rc.2 without purging MongoDB or the >> Elasticsearch index, but I recreated the configuration file and the >> node-id file. >> >> >> Cheers, >> Jochen >> >> >> On 13.02.2014 14:19, Lennart Koopmann wrote: >>> Does it appear again if you just close it? Maybe you restarted you >>> graylog2-server nodes a bit too fast. >>> >>> On Thu, Feb 13, 2014 at 10:31 AM, Şahin Koç <shn...@gmail.com> wrote: >>>> I am getting following warning and don't know how to fix it: >>>> >>>> >>>> Check the system clocks of your graylog2-server nodes. 12 minutes ago >>>> >>>> A graylog2-server node detected a condition where it was deemed to be >>>> inactive immediately after being active. This usually indicates either a >>>> significant jump in system time, e.g. via NTP, or that a second >>>> graylog2-server node is active on a system that has a different system >>>> time. >>>> Please make sure that the clocks of graylog2 systems are synchronized. >>>> >>>> >>>> I have only one graylog node with only one elastic search cluster. They are >>>> both present at the same server. System clock is set to local time of the >>>> location which is Istanbul. Please help me to fix it. Thanks >>>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "graylog2" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to graylog2+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
