Nagios Support Forum

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.

This is most unusual. I'd like you to go into the user edit page (the pencil icon next to the user name) on the manage users admin page. Down at the bottom there's an Auth type link. In turn, select LDAP and AD in the list and see if the fields that show up are populated. If they aren't, you may hav...

A couple of questions for you. Had you enabled LDAP integration at some point in the past? And are there by chance any sessions on Admin->User sessions that might be LDAP enabled?

When you were attempting to join to an existing cluster were you doing that from the initial screen at http://ip.address/nagioslogserver/install, after doing the fullinstall command? Or someplace else. I'm trying to figure out where the relevant issue should be written. Thanks much!

Most likely it is. As Centos 7 is going to be EOL on June 30, I'm glad to see you're testing it in a newer distro of Linux. That was going to be my first suggestion. Can you tell us if you're experiencing this problem on your Ubuntu 22 test system? If not making the cutover might be the easiest solu...