Nagios Support Forum

I'd recommend at least going to a 5.10 release of Nagios XI, and preferably something newer than that. We have a guide for it here:

https://nagiosenterprises.my.site.com/s ... Conversion

It looks like it can be found here:

https://github.com/NagiosEnterprises/nc ... HANGES.rst

The master branch doesn't appear to have been updated yet.

Incidentally, I've opened up an internal issue to automatically create an alert for host freshness, instead of leaving it blank. I can't promise that we'll ever do anything about it but its there.

Yeah that seems like a big problem with Logstash, and even though Elasticsearch is the big memory user, it does make me wonder if Logstash isn't running out of memory to use somehow. As for supporting Centos 7, what you read is correct going forward. Centos 7 itself is going end of life on June 30th...

I'm sorry for the confusion I created. The bits that I'm looking for are going to be in /usr/local/nagioslogserver/logstash/logs, most likely the plaintext file.

kg2857 wrote: ↑Mon May 06, 2024 10:50 pm In the meantime you may want to set a cron to restart logstash.
In my experience logstash was pretty reliable BTW.

Yes, it is generally quite reliable. The big question largely across the board with the ELK stack is system RAM.

Can you get me more of the logs from the logstash log right before that bad file descriptor line?

Looks like you have an extraneous " character near the end of the command after v3=v4, right here:

v1=v2=v3=v4""}'

I've been corrected. It appears that you are using the "-S 0" option for the check which re-arranges the output of the plugin depending on what is in Warning or Critical state. -S, --short=<type>[,<where>,<cut>] <type>: Make the output shorter : 0 : only print the global result except the ...

I don't have a quick solution, and this does indeed look buggy. I've opened an internal issue for the matter.