I tried that. Didn't make it go away. Then I tried a reinstall and a zenmigrate, the KeyError problem persists.
I even deleted all of the devices from the top of the tree, but the key error persists. Right now I'm trying: a combination of zendump/zenload and zendevicedump/ zendeviceload to reconstruct my Devices tree, rrdTemplates, command templates, and perfConf settings before reloading the devices, so it does what I need with SNMP discovery w.r.t. unwanted interfaces, etc. Perhaps a full zendump/zenload would have covered it, but I'd already deleted all the devices as a troubleshooting step. On Mon, Feb 12, 2007 at 02:25:54PM -0500, Eric Newton wrote: > Hi David, > > You can try to reindex all the object relations: > > $ zendmd > >>> reindex() > >>> commit() > > -Eric > > > David Carmean wrote: > >Arg. Frustrating. Even after removing the device this KeyError > >remains. Also tried removing the network where this device was and > >the error remains. > > > >How can I help track this down? I ran zencommand under strace > >and produced a 300MB file (I have > 500 devices) that reduced to 80mb > >when I grepped out the futex() calls. > > > > > >On Fri, Feb 09, 2007 at 07:39:24AM -0800, David Carmean wrote: > > > > > >> KeyError: 'or-term6.lab.netapp.com' > >> > > > > > > > > _______________________________________________ > zenoss-users mailing list > [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users -- David Carmean Network Appliance, Inc Infosystems Architect, 495 E. Java Drive Java (Sunnyvale) Engineering Lab Services Sunnyvale, CA 94089 _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
