Nagios Support Forum

I checked the forums, but didnt see anything that fit for what were seeing.

We can schedule a regular downtime for hosts and services, and that gets logged correctly in /var/log/messages, however, recurring downtime seems to be getting ignored. We did some testing and found that the entries get places in the recurringdowntime.cfg correctly, but never get entered in the log upon entry, and at the time they should trigger a downtime for a host or service, they dont. No log entries, nothing. The file permissions appear correct, apache:nagios, -rw-rw-r-- on recurringdowntime.cfg. The modification time is also accurately reflects the time we entered the downtime. As a test, I attempted to import this file via CCM > Tools > Import Config Files, but got no conformation, it just thought about it for a second and then did nothing.

Is this a known issue with 2011r3.2? I can PM the recurringdowntime.cfg to whomever, and I have attached the profile.txt to this post. Any ideas of where I can begin looking?

When creating recurring downtimes, it only runs the cron to create the downtimes once per hour

Ok, Ill check the cron job. We have had recurring downtime set for weeks that is being consistently ignored. Thanks for the pointer.

Yeah, you're looking for the one that calls /usr/local/nagiosxi/cron/recurringdowntime.pl

You also can run that file directly to see if you are getting any errors

In checking the cron job, I was lead to the log (/usr/local/nagiosxi/var/recurringdowntime.log) where I see every host set for recurring downtime throwing this one error: "ERROR: Invalid host Blah!"

I can copy and paste that host name into nagios and it comes up, so its not a case sensitivity issue. All of the other fields seem to check out. Why would it believe that these valid hosts are invalid?

Actually there was a bug that was fixed since 3.2 relating to exactly this.

I have attached the new file you can place in
/usr/local/nagiosxi/cron

Ha! I think we just found it and fixed it... Im assuming regarding the wildcard issue. Its working for us now.. but thank you!

actually it had to do with line endings in the nagios.cfg if you can believe that...