Nagios Support Forum

Ideally you'd go to 2024R1.3.7. However, the only thing you need that for is if you have Active Driectory or LAP integration enabled, with TLS-enabled directory servers that you need to migrate the certificates automatically for. You can do that just by adding the certificates manually either before...

That makes sense. we configure the local rsyslog to send to port 5544.

Posting this for anyone else who encounters a similar problem; you can also edit the rsyslog config to point it back to port 514 on the log server machine.

That's great to hear!

Unfortunately I'm beginning to think that this is deeper than what we can dig into on the forum here. Do you have active support where you can open up a support ticket for this? They'll have a better ability to work with you to track this down better.

did you change the Logstash Inputs configuration to use port 514 instead of 5544? that may be the problem

When you say that another user can see the dashboard, are you looking at the same dashboard or a different one?

ALso out of curiosity, how old is this Nagios Log Server deployment?

Ho about netstat -anp. What java processes are showing as running? How about systemctl status logstash.srvice?

That's very unusual and unexpected. Can you log in as a different user and look at a dashboard? Or navigate to http://fqdn/nagioslogserver/dashboard?d ... id=default

does running netstat -a show anything listening on port 5544?

Can you hit F11 while you're in your browser, and post the URL (feel free to redact your IP address) of the item that shows the 404 error while its loading dashboards?