Skip to main content

Hi,

When I set those downtimes I checked if they were effectively set, that was the case (apparently). But today I learn that one of our users told me he had to set another downtime because there wasn’t any. Checking the downtime list I see this:

 


So, those downtimes were started, canceled, but also never started.

Who cares about new fancy dashboards and responsive design when basics things like downtimes do this? Maybe an executive manager who decides what tool is the best after reading a commercial leaflet and is in position to pay for it, but clearly not the technicians and engineers who do need to get things done. IMHO of course!

Maybe?

https://docs.centreon.com/docs/23.10/releases/centreon-os/#centreon-broker-2

  • [Broker] Fixed an issue in the installation process that emptied the retention.dat file, causing the temporary loss of all resources' statuses and the permanent loss of current acknowledgements and downtimes.

What makes you think this bug could be related?
The downtimes have been set well after the upgrade, in 23.10.11, as the dates on the screenshot suggest…

🤔, what else? 

  • are they on the same poller?
  • within the check period?
  • services working ok?
  • 🤔

Hi @Stéphane ,

If you see "Never Started" in the "Actual end" column, it means that the downtime have been cancelled by someone before it start.
If you see "N/A", may be it means that downtime have been sent to Centreon Engine but the attached resources are still in OK status so the downtime never start yet.

Hi @Laurent 

OK. But it makes no sens having “Yes” in the “Started” column.

@ponchoh : I don’t know what else but it sure has no relation.

“The downtimes have been set well after the upgrade, in 23.10.11, as the dates on the screenshot suggest…”

I clearly see the problem you are referring to as I had it during a previous upgrade (20.10.… → 20.10.19). The problem is obviously different here.

Subject is close to me. If you consider displaying that a downtime can be “started while never started” is not an issue, well, let’s say it isn’t then…

Reply


Terms & ConditionsCookie settings