-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with old downtimes #42
Comments
It seems that when worker is down, the worker does not detect the end downtime.
No more errors after a restarted service but the obsolete downtimes are still there.. Even if it's a worker problem, In any case the interface should still not display expired downtimes. |
This sounds interesting. Basically this is a worker related issue. How ever, the worker forks a MiscChild which will handle Notifications, Downtimes and Acknowledgements and a separate PerfdataChild which process performance data. Normally whatever happens to the perfdata child should not cause any side effects to other processes / workers.
I will do some investigation into this. |
Yes I noticed that I had no side effect with the worker errors. My problem is still present, I can't find the source of the problem to reproduce it. Currently I manually clean the MySQL database, it is not very clean. |
Is this still a thing? |
I recently updated to the latest version, I am looking to see if the problem comes back or not ;-) |
The command "/opt/statusengine/worker/bin/Console.php cleanup" should not clean up old ACK / DOWNTIME? I still have DOWNTIME from "23:59 12.13.2020"...
|
Hi,
I have a problem with Upcoming downtimes. My old downtimes are still present with the status "Downtime currently running" and "Cancel" button.
Do you know why?
The text was updated successfully, but these errors were encountered: