cluther wrote: > This error indicates that there is a problem with your maintenance > windows catalog. You can try rebuilding the index by running > "zenmigrate --step=TwoTwoIndexing" as the zenoss user then restarting > zenactions. > > _______________________________________________ > zenoss-users mailing list > [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users
Rebuilding the index yielded the exact same message, is there a database clean-up script or anything I can use to provide more info; I can tell the script dies for a reason but there is too little info. You probably are right on it being a maintenance issue; the log did indicate the following line: > 2008-04-20 04:53:28 WARNING zen.Schedule: Run zenmigrate to index your > maintenance windows. But then the message stops after one hour or so and at 22:46:26, it was the last time 0 rules were processed. I guess zenactions never ran since then but as the box has only just been comissioned to go into full scale production. This morning we had a couple of outages, due to power glitches, which ZenOSS recorded correctly but were not alerted to. As luck would have it, I found the problems and resolved before anyone even called. > I was able to resolve exactly the same error by re-creating Alerting Rules > that were no longer viable. I had deleted a user account with Alerting Rules > just before this issue started. Now that I've recreated the user account and > alerting rules (exactly as they were before) the message has changed > slightly: > > File "/usr/local/zenoss/products/zenevents/zenactions.py", line 643, in ? > za.run() > File "/usr/local/zenoss/products/zenevents/zenactions.py", line 496, in run > self.schedule.run() > File "/usr/local/zenoss/products/zenevents/schedule.py", line 82, in run > self.runEvents() > File "/usr/local/zenoss/products//zenevents/schedule.py", line 111, in > runEvents > work = self.makeWorkList(now, self.workList) > File "/usr/local/zenoss/Products/ZenEvents/Schedule.py", Line 85, in > makeWorkList > work - [(mw.nextEvent(now), mw) for mw in workList] > AttributeError: nextEvent > > I tried running zenmigrate --step=TwoTwoIndexing to no avail In that case, it sounds like DB corruption...maybe I better not go that route as it may create a bigger mess. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=19421#19421 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
