scheduled downtime

[jkinning]

It appears that my scheduled downtime is broken once again after updating to 5.4.4. I had a couple months in advance for our maintenance window which usually fall on the 3rd Sunday of each month. My hosts are showing they are scheduled for downtime next Sunday the 28th and I have no entries. If I just use a single date everything appears to work. Am I misunderstanding the scheduled downtime? Is it meant to use for single schedules? Meaning I cannot schedule a year's worth of maintenance dates, set it and forget it type of thing.

In the past I had these issues and I was provided with an updated recurringdowntime.pl file which I had to replace in the /usr/local/nagiosxi/cron directory. Anyone else having this issue?

Attaching recurringdowntime.pl file I currently have running.

[tgriep]

I setup a recurring downtime the way you described and I do see that the host in the menu as being scheduled.
If you can post the following files here so I can check the settings and the log and see if I can recreate the issue?

Code: Select all

/usr/local/nagios/etc/recurringdowntime.cfg
/usr/local/nagiosxi/var/recurringdowntime.log

Thanks

[jkinning]

How frustrating...is there a size limit? I am unable to attach the files.

[jkinning]

Appears the log files are too big to attach.

[tgriep]

Yes, there is a size limit, if the file is too large, you would have to zip it up before you upload it.
In the 3rd Sunday schedules, you only have the 25th as the Days in Month field, since the 25th does not fall on this Sunday, those hosts and services will not get scheduled this weekend.
If you edit those entries and put the following in the Days in Month field

Code: Select all

23,24,25,26,27,28

This will set the recurring downtime schedule to do every 3rd Sunday of the month.

[jkinning]

Right, I updated it for the month of June. Since Father's Day is the 3rd Sunday we drop down to the 4th Sunday. Normally our maintenance is the 3rd Sunday.

Why are my hosts and services showing a scheduled downtime for the 28th?

I also zipped up the log file and it must still be too large. It doesn't attach.

[tgriep]

I don't know why the host and services are scheduled for this Sunday. Maybe somebody did a onetime scheduled downtime.
Can you open that log file, delete most of the content except the last thousand lines or so and upload that?
Can you run the following as root and post the output?

Code: Select all

ls -l  /etc/logrotate.d/

Thanks

[jkinning]

I shortened the log.

ls -l /etc/logrotate.d/
total 28
-rw-rw-r-- 1 root root 135 Jan 17 2016 ConsoleKit
-rw-r--r-- 1 root root 139 May 12 2016 dracut
-rw-r--r-- 1 root root 185 Dec 9 06:54 httpd
-rw-r--r-- 1 root root 871 Jan 26 17:25 mysqld
-rw-r--r-- 1 root root 351 Oct 4 2016 nagiosxi
-rw-r--r-- 1 root root 210 Dec 10 2014 syslog
-rw-r--r-- 1 root root 87 Mar 22 01:32 yum

I am the sole administrator so someone else scheduling would not have happened.

[tgriep]

I was able to recreate the issue and filed a bug report for the issue.
The task ID for the bug is 11882 for future reference.

[jkinning]

Is there anyway to fix this now? Every time I clear this out they return.

This has happened numerous times after I have upgraded to various versions in the past.