I ran into a schedule issue a few weeks ago where I was setting the schedule for an rule to occur in the past. Like I wanted it to start at 8:30-AM and run for 9 hours every week day and I started the schedule at 12PM. Thinking that the schedule would just start the following day when 8:30 rolled around. I read that you can't do this and you have to set the event to start in the future. For example if it's 12 noon on Monday and I set the schedule to begin at 8:30 on Tuesday and run for 9 hours weekdays only with a repeat of "1," the rule will start working on Tuesday and send alerts from 8:30-5:30 only. This worked in a test env, but when I rolled it out to production, I got a page at 6:30AM. The date on the linux server (zenoss) is fine. I don't know why this schedule didn't work. The way I see it, when the rule is matched, I should not get a page on weekends, or between 5:31 and 8:29 on weekdays. I even have my messages section setup with text fields so I can be sure which rule sent the alert. Like, applications_9-5, so I know which set of rules triggered the alert. The rule worked just the way it should, no double pages from other rules, so something is up with the scheduling of zenoss. Does this have something to do with the repeat of "1." Does that mean it will only run once? All schedules were enabled with start time in the "future" this time around. In this case the rules was enabled 10 hours in advance of the start time.
-------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=18960#18960 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
