On Mar 13, 2008, at 4:18 PM, webpass wrote:
Thanks... here's the errors I'm getting from zenhub:
2008-03-13 11:29:37 ERROR zenhub: device CORE2-SFO
Traceback (most recent call last):
File "/usr/local/zenoss/Products/ZenHub/services/CommandConfig.py",
line 39, in getDataSourceCommands
cmdinfo = dev.getDataSourceCommands()
File "/usr/local/zenoss/Products/ZenModel/Device.py", line 651, in
getDataSourceCommands
for o in self.getMonitoredComponents(collector="zencommand"):
File "/usr/local/zenoss/Products/ZenModel/Device.py", line 530, in
getMonitoredComponents
collector=collector, type=type)
File "/usr/local/zenoss/Products/ZenModel/Device.py", line 553, in
getDeviceComponents
return [c.getObject() for c in brains]
File "usr/local/zenoss/lib/python/Products/ZCatalog/
CatalogBrains.py", line 77, in getObject
parent = parent.unrestrictedTraverse(path[:-1])
File "usr/local/zenoss/lib/python/OFS/Traversable.py", line 221, in
unrestrictedTraverse
next=obj[name]
File "usr/local/zenoss/lib/python/OFS/ObjectManager.py", line 713,
in __getitem__
raise KeyError, key
KeyError: 'Network'
This is caused by an object existing in the componentSearch catalog,
but not really existing anymore. You can try to fix it by running
zendmd as the zenoss user and running the following commands:
dmd.Devices.reIndex()
commit()
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
