On Mar 16, 2008, at 10:39 PM, HerbertS wrote:
Like you can see using the links im my last posting, performance
graphs are created for a short time period after rebooting /
restarting zenoss service.
I've seen this happen before due to the incremental device loading
code in zenperfsnmp. When you first start it, you aren't guaranteed to
poll all devices on the first run. Then on subsequent cycles
zenperfsnmp loads in a device that is broken. This is normally caused
by an invalid catalog. Try the following to rebuild the related
catalogs.
As the zenoss user, run zendmd. At the zendmd prompt run the following
two commands:
dmd.Devices.reIndex()
commit()
_______________________________________________
zenoss-users mailing list
zenoss-users@zenoss.org
http://lists.zenoss.org/mailman/listinfo/zenoss-users
