Page 1 of 1

Year Change to 2018

Posted: Tue Jan 02, 2018 6:22 am
by saleemthupsee
Hello,

my nagioslogserver installation stopped ingesting logs on the 31/12/2017 @ around mignight. I had to reboot for all ingest functions to start back today.

Is that a known behaviour ?

REgards,
Saleem
Paris

Re: Year Change to 2018

Posted: Wed Jan 03, 2018 11:01 am
by cdienger
This would be the first instance we've heard of related to the new year and It could just be coincidence. I would check the logs in /var/log/elasticsearch/ and /var/log/logstash/ for errors and warnings around the time the problem was noticed. The problem you described could indicate a crash of either the logstash or elasticsearch process.

Re: Year Change to 2018

Posted: Fri Jan 05, 2018 5:44 am
by CBoekhuis
We had the same problem, at midnight new year almost all logging stopped. After restarting all logstash and elasticsearch services (NLS 1.4.4) on all cluster nodes everything was back to normal. So that makes 2.... ;)

Greetings..Hans Blom

Re: Year Change to 2018

Posted: Fri Jan 05, 2018 12:44 pm
by kyang
@CBoekhuis,

That would make 2 cases.

Did you happen to see any notable logs in /var/log/elasticsearch/ and /var/log/logstash/.

Re: Year Change to 2018

Posted: Mon Jan 08, 2018 3:26 am
by CBoekhuis
Hi Kyang,

no nothing in the elasticssearch/logstash logfiles. That's also the reason I didn't investigate it any further.

Re: Year Change to 2018

Posted: Mon Jan 08, 2018 9:03 am
by mcapra
For posterity, this appears to be a "gotcha" between logstash-output-elasticsearch and Joda:
https://github.com/logstash-plugins/log ... issues/541
https://github.com/logstash-plugins/log ... issues/354

I think the solution is to change the default index template used by Nagios Log Server for its ElasticSearch output, but I don't have an instance to check against currently.

Re: Year Change to 2018

Posted: Mon Jan 08, 2018 12:09 pm
by kyang
Thanks for the help @mcapra! It certainly fits the part.

Strange enough, but since a restart of logstash and elasticsearch or rebooting Nagios Log Server got everything back to normal. I'm not sure where to exactly classify this.

If we see this as a strong enough issue, I'm sure someone will look into it.