Recurring downtime not working after upgrade to 5.5.1

[gmackey]

Hello,

We recently upgraded from 5.4.13 to 5.5.1. Before the upgrade we were having no issues whatsoever. The upgrade itself had a message in red that it failed but I couldn't see any failures in the huge log as I scrolled through it and it shows it's on 5.5.1 now. Everything seems to be working except for recurring downtime. I just checked /usr/local/nagiosxi/var/recurringdowntime.log and noticed that the downtime is now being measured in seconds rather than minutes. The two errors "Duration (2 s) is shorter than minimum (5 m)" tipped me off to this since I have two recurring downtimes set up for 2 minutes each (they were 1 minute each before I changed them for troubleshooting). These are supposed to be in minutes, not seconds, as clearly indicated in the interface, so I believe this is a bug with 5.5.1. Please let me know what needs to be done to resolve this bug. Thanks!

Edit: Also, just as an addendum, I have a 360-minute recurring downtime for another service that's been there for quite a few months and isn't working either. None of the recurring downtime entries for individual hosts and services are showing up in scheduled downtime after the update to 5.5.1.

-Greg

[scottwilkerson]

Greg,

We are testing this now.

Were all these recurring downtimes setup before the upgrade?

[scottwilkerson]

We have confirmed this behavior on some systems and are sending to the developers as a bug report.

We also did confirm if we removed the recurring downtimes we has set and re-added them we had success.

We realize this is not ideal but wanted to let you know our findings

[gmackey]

Thank you. One of them was added after the upgrade but it wasn't getting applied since it was under the 5-minute threshold (it would be nice if the interface indicated a 5-minute minimum as I wasn't aware of this). I did not try removing and re-adding the 6-hour downtime but I believe it would only be 360 seconds rather than minutes if I did so, so I'll wait on the fix before changing values to seconds since I'd have to change them back after the fix, I imagine. Thanks!

[scottwilkerson]

The code changed and I believe the problem is that the recurring downtimes were created with the only code.

How many recurring downtimes to you have set? I ask because our only option will likely be to create new ones and delete the old ones.

[gmackey]

We have the following recurring downtimes configured.

Hosts: 4
Services: 6
Hostgroups: 27
Servicegroups: 2

If we have to do it, recreating them won't be too much of an issue given those numbers. I just don't want to do anything at the moment if the downtime that's supposed to be in minutes is being set in seconds (as recorded in the log), as I'd then have to go back and change things again after that gets fixed. I'll at least wait for that fix so downtimes are set in minutes before recreating them. Thanks.

[scottwilkerson]

Unfortunately, it appears that the problem is that it was saved in the database in the past with the minutes value, and these changed to a seconds value.

At present I don't see another way to fix them.

[gmackey]

Can I get confirmation that this value has intentionally changed to seconds and won't be changed back to minutes as part of the fix? The wizards still say "Duration of the scheduled downtime in minutes." for the caption, so that text needs to be changed if the duration is now going to be in seconds from 5.5 forward. Thank you.

[scottwilkerson]

Can I get confirmation that this value has intentionally changed to seconds and won't be changed back to minutes as part of the fix? The wizards still say "Duration of the scheduled downtime in minutes." for the caption, so that text needs to be changed if the duration is now going to be in seconds from 5.5 forward. Thank you.

It is going to remain minutes, the calculation is in the backend