cluther wrote: > 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.
But if you'll read in my post on 11/5: seth wrote: > The only maintenance window that the Linux servers partake in is the Sunday > morning scheduled reboot window from 2:45am - 4:00am. So the linux servers are only affected by one window, yet I have linux servers that participate in this weekly oddity. And if my problems were because of overlapping windows it would only be happening on (let me count...) 6 domain controllers and 7 app servers, not (counting again...) 55 servers (including the 13 mentioned). The 6 DCs and 7 app servers are the only servers that participate in overlapping windows. So why do I have another 42 servers that are only in one window not getting their state reset correctly? cluther wrote: > I hope this helps you better understand why this is happening to you. You > would be best served by avoiding these overlapping windows. I understand that Zenoss can't handle overlapping maintenance windows right now, and if that's what my problem was, I could easily solve it. But I do hope it's understood that overlapping maintenance windows do happen in the real world, so it might be something to look into for a future release. Thank you for your quick response. I appreciate all the help! --seth -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=13398#13398 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
