NagiosXI 5.10.0 Monitor Process Fails to Start

[NickF]

Hello! First time poster here.

I am stumped and looking for some advice. My NagiosXI system 5.10.0 (Virtual - built from the packaged .ova) passes all pre-flight checks when restarting but my Monitor Engine Process never starts. What lead me down this rabbit hole was our "Last Check Times" on the hosts and services is stuck on a date from a couple weeks ago. Forcing an Immediate Check on the hosts yields a generic "An error occurred processing your request".

Things I have tried:
Checked out Nagios Core to see lots of these: 08-03-2023 08:47:06] Caught SIGTERM, shutting down...
systemctl restart nagios
Rebooting the system entirely
Writing the Configuration to check for errors
Rolling back to a replication (The replication still had the errors on it.. )

Things I have not tried:
Sorcery.

Any guidance would be appreciated!! Thanks!

[eloyd]

We had a customer that had this problem with an earlier version of Nagios (maybe, 5.8.something?). For them, it was a broker that they added to do some work. Took the broker out, and things went back to normal. Have you done any broker work?

[lgute]

Hi @NickF, thanks for reaching out.

Have you updated Nagios XI? A similar issue was reported by users who updated to 5.11.0.

Please look at the last 3 lines of the /usr/local/nagios/etc/ndo.cfg file.

If it looks like this, where two lines have been concatenated, insert a line before `downtime_history_data` or the appropriate entry, in your case.

Code: Select all

mysql_set_charset_name=utf8downtime_history_data=0
comment_history_data=0

So your file has each entry on a separate line.

Code: Select all

mysql_set_charset_name=utf8
downtime_history_data=0
comment_history_data=0

Save the file and then restart nagios - `systemctl restart nagios`.

Thank you @GldRush98! for decoding this issue viewtopic.php?t=65770

Please let me know how it goes.

[eloyd]

Ha. Now that @lgute mentions that, I forgot all about it! Mainly because we never recommend upgrading to a .0 release - always wait for the .1.

In this case, I'm guessing that is the problem though. Good catch and good luck!