Nope, didn't do the trick.
After creating a new class under 'Linux' (and no, the class isn't 'SAS') I got
this at the tail end of zenhub.log (after restarting Zenoss from top to bottom):
Code:
2008-02-22 21:29:57 ERROR zenhub: device myserver1
Traceback (most recent call last):
File "/opt/zenoss/Products/ZenHub/services/CommandConfig.py", line 39, in
getDataSourceCommands
cmdinfo = dev.getDataSourceCommands()
File "/opt/zenoss/Products/ZenModel/Device.py", line 651, in
getDataSourceCommands
for o in self.getMonitoredComponents(collector="zencommand"):
File "/opt/zenoss/Products/ZenModel/Device.py", line 530, in
getMonitoredComponents
collector=collector, type=type)
File "/opt/zenoss/Products/ZenModel/Device.py", line 553, in
getDeviceComponents
return [c.getObject() for c in brains]
File "/opt/zenoss/lib/python/Products/ZCatalog/CatalogBrains.py", line 77, in
getObject
parent = parent.unrestrictedTraverse(path[:-1])
File "/opt/zenoss/lib/python/OFS/Traversable.py", line 221, in
unrestrictedTraverse
next=obj[name]
File "/opt/zenoss/lib/python/OFS/ObjectManager.py", line 713, in __getitem__
raise KeyError, key
KeyError: 'SAS'
Open to suggestions at this point.
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=16552#16552
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
