I followed your step 1 through 4 instructions on recreating the
MaitenanceWindowCatalog and it is throwing out alerts at last. But there is the
lingering issue of this message:
> WARNING zen.Schedule: Run zenmigrate to index your maintenance windows.
I did use the 2.2 reindex to no-avail but what else is required? I am not
convinced that the change set will fix it;
Code:
catalog = getattr(self.dmd, 'maintenanceWindowSearch', None)
if catalog is not None:
result.extend(x.getObject() for x in catalog())
for brain in catalog():
try:
ob = brain.getObject()
except KeyError:
# We're just catching the symptom for now, but an actual
# fix will be forthcoming.
# http://dev.zenoss.org/trac/ticket/3105
pass
else:
result.append(ob)
else: # Should be removed in 2.3.
self.log.warn('Run zenmigrate to index your maintenance windows.')
Based on this, code, it looks like something else may be going on to trigger
the warning. So why is the catalog none?
cluther wrote:
>
> > 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.
> > >
> >
> > 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.
> >
> > In that case, it sounds like DB corruption...maybe I better not go
> > that route as it may create a bigger mess.
> >
>
> You could try applying the changeset below to see if it helps. Before
> trying that you could try the following to wipe and rebuild the
> maintenanceWindowSearch catalog.
>
> 1. Go to http://yourzenoss:8080/zport/dmd/manage
> 2. Delete the maintenanceWindowsSearch catalog
> 3. Run zenmigrate --step=MaintenanceWindowCatalog
> 3. Run zenmigrate --step=TwoTwoIndexing
> 4. Restart zenactions
>
> Changeset r9174:
> http://dev.zenoss.org/trac/changeset/9174
>
> _______________________________________________
> zenoss-users mailing list
> [email protected]
> http://lists.zenoss.org/mailman/listinfo/zenoss-users
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=19496#19496
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
