Host not Entering Recurring Downtime

[matt.uebel]

I have a host that does a weekly reboot. I have the recurring downtime scheduled in XI as such:

[Host] <case sensitive hostname>
[Type] host
[Service] N/A
[Comment] Weekly Reboot
[Start Time] 1:50
[Duration] 40
[Weekdays] fri
[Days of Month] All

This morning at 2:03 (the time of reboot), I received a host down notification when Nagios failed to ping the host.

When I search /usr/local/nagios/var/nagios.log, I fail to find a DOWNTIMESTART or END for this host.

In fact, I also have Recurring Downtime scheduled for a few Hostgroups as well, and I don't see any of their DOWNTIMESTART entries in the nagios.log.

Is there some other location I can look to tell if a specific host is actually entering downtime? Why did I receive a notification for a host that I have downtime scheduled for?

[lmiltchev]

Do you see the host that you tried to schedule a downtime for in the log?

Code: Select all

tail /usr/local/nagiosxi/var/recurringdowntime.log

Run the following command and show us the output:

Code: Select all

ll /usr/local/nagiosxi/cron/recurringdowntime.pl

[matt.uebel]

looking in /usr/local/nagiosxi/var/recurringdowntime.log I find:

Weekly Reboot: <case sensitive hostname>
ERROR: Invalid host <case sensitive hostname>!

-rwxr-xr-x. 1 nagios nagios 17747 Apr 1 17:00 /usr/local/nagiosxi/cron/recurringdowntime.pl

[lmiltchev]

Go to CCM->Hosts-><case sensitive hostname>View Text Config and PM me the output. Also, go to Home->Recurring Downtime, and PM me a screenshot of this page.

[matt.uebel]

The host in question does not have any Services.

[lmiltchev]

This is definitely the issue. We will let you know as soon as the bug is fixed. I already filed an internal bug report.

[matt.uebel]

Thanks.

Another bit of weirdness... the restart will happen tonight, and so I am trying to run the downtime command using the XI interface. When I start entering the hostname, normally I would expect the system to start trying to autocomplete the hostname. However, when typing in the troubled hostname, at no point doesn't it suggest the full hostname.

It will suggest other hosts as I continue to type the name, but not the one in question.

Do you know what would prevent a host from being found for the schedule downtime interface's autocomplete mechanism for the "Host Name" field?

I am going to enter the name and try to schedule anyhow.

EDIT: The schedule downtime command worked. Also found that I have 2 other servers with similar names that don't show up in autocomplete.

[lmiltchev]

This is really strange. I tested your config and auto-complete worked just fine. The search is done by hostname and alias, and it is not case sensitive.
So, when I change the description of the "localhost" host under CCM to "test", and apply configuration, then I type "t" in the "Host" field under "Add Recurring Downtime Schedule", all of my hosts that start with "t" or have aliases, that start with "t" show up (including "localhost"). I am not sure why auto-complete doesn't work for some of your hosts. I haven't been able to recreate the issue so far.

[matt.uebel]

If I type into the search box on the home page, it turns up all the hosts I would expect, including the one I have trouble with.

Now, going back to the External Command Interface to schedule downtime for a host (nagiosxi/includes/components/nagioscore/ui/extinfo.php?type=6) when typing into the Host Name box I am actually finding the problem host show up, but not the others of a similar name.

This seems to be using two different mechanisms... maybe the External Command Interface is just using the browsers autocomplete history(I had previously entered the host name in this field), where the Home Page actually has a search mechanism.

At any rate, I suppose all this is beside the point. Thanks for checking though.

[lmiltchev]

maybe the External Command Interface is just using the browsers autocomplete history

I can check on that with one of our developers, however, I don't believe it is true. If you delete your browser's history, cache, etc. and try again, you will see that autocomplete works despite of the fact that you haven't typed these hostnames before.