Skip to main content

Hi,

Currently, if a service which is in a downtime period is renamed, cancelling the downtime doesn’t work. It requires the engine to be restarted, a simple reload isn’t sufficient. In addition, after the restart, the downtime, while effectively cancelled, is still shown as “Nerver started” in the downtime list.

Is it something that one can expect to be fixed? If it can’t be handled as if the service hasn’t been renamed, could it be possible that a simple reload does the job? Because restarting the engine on a poller with thousands of service isn’t something which is absolutely transparent: it takes a couple of minutes and the poller may appear as not running for a little while and services as being in a unknown state.

As a service has an ID, changing its description (ie: name) shouldn’t have an impact on downtimes.

If it can’t be fixed because it would require too much modification of the code, would it be possible to prevent the renaming with a message telling that the service can’t be renamed while in downtime? 

Hi Stéphane,

I had the same problem today. Changing the name back to the old one for those downtimes that were stull current allowed me to caoncel them and rename again the services. For those downtimes already finished but the services were still showed in downtime I had to duplicate the service and delete the old one.

I’ll try restarting the engine next time. Thanks for sharing!

Regards,

Enrique

Hello,

I don't know if it is the same problem but in version 22.04 when I modified the services of an already existing Recurring Downtime they disappeared when saved. When I came back in it was blank.

For it to work I had to create a new one and not modify it.

 

Regards,

 

Carlos

We’re planning to start using our new 22.10 platform in production the 13/03, I’ll see then quickly if there are issues with the recurring downtimes.

 

Reply


Terms & ConditionsCookie settings