Another Monday, another morning of setting half my servers back to
Production mode.
This is one of the few bugs that is keeping me from recommending
Zenoss as a replacement to our existing monitoring system. If there
is anything I can do to help track down this issue, I will do it in
a heartbeat. I need this to work or else I might as well abandon
this project.
Please let me know just how I can help you guys troubleshoot this
issue. I'm tired of having to manually reset my servers to whatever
state they're supposed to be in.
This is likely happening because of the following scenario. You have
the following two maintenance windows:
Window A:
Start time: 00:00
End time: 08:00
Start production state: Maintenance
Stop production state: Original
Window B:
Start Time: 02:00
End Time: 10:00
Start production state: Maintenance
Stop production state: Original
The problem is due to Window B's begin time overlapping Window A's end
time and both of them using Original as the stop production state.
What happens is this.
00:00) Device is set to maintenance mode and original production state
is recorded as Production
02:00) Device is set to maintenance mode and original production state
is recorded as Maintenance
08:00) Device is set to Window A's original production state which is
production
10:00) Device is set to Window B's original production state which is
maintenance
I hope this helps you better understand why this is happening to you.
You would be best served by avoiding these overlapping windows.
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
