Nagios Support Forum

Hi @Sandip2705,

This error looks like you are seeing database corruption with the nagios.nagios_logentries table. I would highly recommend opening a support case with the support team.

https://supportportal.nagios.com/s/arti ... ing-a-Case

Glad you were able to find a solution that worked for you! Yeah it's difficult to trace DNS and caching issues like that, who knows, maybe Cent 7 didn't have DNS cache enabled but the new Ubuntu server does, or there is something caching requests in front of one of the servers but not the other. It'...

Hey @JohnFLi ,

That does sound like there are some weird DNS/caching things going on. However, you should be able to edit the hostname to the correct one in the wizard.

Hi JohnFLi , This sounds to me like some sort of networking issue on the new Ubuntu 24.04 XI server. Are you by chance using IPv6 or a mix of IPv6 and IPv4? Are you trying to resolve a hostname and not an IP address from the XI Wizard? It could be there are both IPv6 and IPv4 namerecords and there i...

Hey @sawdusty,

The new version of Nagios XI released earlier today (2026R1.6), you might want to give that install a try.

https://assets.nagios.com/downloads/nag ... 1.6.tar.gz

Hey @KWGagel,

Okay, thank you for the further clarification. An alternative to removing the entire host object, is you should be able to go into the CCM -> Services and remove the old/bad passive service check(s) for that host. Hopefully this helps!

Ahh thanks kg2857 for help clarifying that. KWGagel It sounds when you are adding the passive the checks they are showing up in the old host object. This is happening because the old host object and the new unconfigured object have the same hostname in Nagios. One thing you can do to prevent this fr...

Hey @KWGagel,

Unfortunately deleting the host from Nagios and re-adding the new unconfigured object is the simplest way that I know of also.

Hi Jordan, I would make sure that httpd/apache2, postfix, and the cron services are stopped as well. systemctl stop apache2 systemctl stop postfix systemctl stop crond I would also double check that the nagios service is stopped even though you issued the stop command: ps -ef | grep nagios systemctl...

Hi @op-team ,

I believe you are correct that this is not normal behavior for eventman.php.

I would highly recommend opening a support case to help diagnose and resolve the underlying problem.