Nagios Support Forum

I renamed some hosts today using CCM.

Afterwards these specific hosts are showing up as "Host check is pending...".
But from other views it looks OK

From the first screenshot you can see that there is no "Schedule an immediate check" link.

I've tried rebooting the Nagios XI server, no change.

With one of the hosts I've tried

• disabling host
  applying config
  deleting host
  applying config
  creating host
  applying config

However the same problem exists.

Help

Nagios XI 2011R1.1 running on ESXi 4.1 Update 1 VM.

Hmmmm - I suspect this is a bug in the XI code that fetches host information. Can you email us to provide us with the host name the host is currently using? That will help us in debugging. Send it to: [email protected]

Thanks!

Just emailed it through.

If you're running 2011R1.1, I would recommend upgrading to our latest release as soon as it's feasible for you. We discovered a bug in 1.1 that may cause table corruption in the ndoutils tables. I might recommend running the following repair procedure and see if this resolves your issue:

http://library.nagios.com/library/produ ... i-database

Sure thing, I've done the following:

• Ran the repair procedure
  No change
  Upgraded to 2011 R1.3
  No change
  Rebooted XI sever
  No change
  Ran the repair procedure
  No change
  Ran the repair procedure
  No change

After this I did a quick test:

• Created a new host called 2150-vault16-2
  Applied config
  All working OK
  Renamed host as 2150-VAULT16-2
  Applied config
  Same problem occurs as described in first post, there is no "Schedule an immediate check" link, host is showing up as "Host check is pending...".

I think I've seen this on one of my own test boxes, but I thought it was something I broke since it was my development test box ; ) I'll do some digging on this and see what I can find out, but it looks like this could be a bug since another user is reporting the exact same thing.

Bug Confirmed. We found the cause of it and we're working on a fix as we speak.

http://tracker.nagios.com/view.php?id=155

Great stuff

Our patch appears to have fixed this. This should be taken care of in 2011R1.4 when it's released.

I can confirm that this problem no longer occurs when I upgraded to 2011R1.5. I didn't get around to trying 1.4.