Service Status stuck in pending

[Box293]

Code: Select all

mkdir /tmp/hosts_backup
mkdir /tmp/services_backup
mv /usr/local/nagios/etc/hosts/*.* /tmp/hosts_backup/
mv /usr/local/nagios/etc/services/*.* /tmp/services_backup/

Go into CCM
Quick Tools > Apply Configuration
Click the Apply Configuration button

Does this fix your problem?

[weapon]

No, that still does not help

[tgriep]

Could you run the following in a shell on the XI server and schedule an immediate check for that service and post back the results of the tail command?

Code: Select all

tail -f /usr/local/nagiosxi/var/cmdsubsys.log

[weapon]

I had to submit a passive result first before I could force a immediate check - it is still reporting a passive OK state after I submitted the command.

I have got the tail you requested attached.

[lmiltchev]

I had to submit a passive result first before I could force a immediate check - it is still reporting a passive OK state after I submitted the command.

Why did you have to submit a passive check before you could force an immediate check?

Do you have any mysql errors?

Code: Select all

tail -50 /var/log/mysqld.log

[weapon]

I have to submit a passive check first as when it is stuck in pending, I can't force and intimidate check.

Doesn't look like I have any SQL errors

[abrist]

If the check is stuck as "Pending", then it is not getting scheduled at all, or it is getting recheduled before the check is run. Is there a scheduled next check time on the check's details page in XI?

If core is displaying it correctly, then it is an issue with ndo - it is either not getting inserted into the db, or it is getting read from the db correctly.
This may be a very fast resolution through a remote if you wish to open a ticket.

[weapon]

It is stuck in pending because the backend is publishing the wrong date for when the state last changed.
How do I open a ticket to get this resolved?

[Box293]

Send an email to [email protected] referencing this forum post.

[tmcdonald]

We have received your ticket so I will be locking this thread.