cluther wrote:
>
> from Products.ZenHub.services.SnmpPerfConfig import getDeviceConfig
> cfg = getDeviceConfig(find("PROBLEM_DEVICE_NAME"))
>
> If the configuration is successfully built without errors you should
> just get another >>> prompt. If errors are encountered, the associated
> traceback will be printed. This traceback should contain useful
> information for determining where the problem is.
Thanks for the suggestion. This produces the following output:
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "/usr/local/zenoss/zenoss/Products/ZenHub/services/SnmpPerfConfig.py",
line 50, in getDeviceConfig
for comp in dev.os.getMonitoredComponents(collector="zenperfsnmp"):
File "/usr/local/zenoss/zenoss/Products/ZenModel/Device.py", line 533, in
getMonitoredComponents
collector=collector, type=type)
File "/usr/local/zenoss/zenoss/Products/ZenModel/Device.py", line 563, in
getDeviceComponents
return [c.getObject() for c in brains]
File
"/usr/local/zenoss/zenoss/lib/python/Products/ZCatalog/CatalogBrains.py", line
77, in getObject
parent = parent.unrestrictedTraverse(path[:-1])
File "/usr/local/zenoss/zenoss/lib/python/OFS/Traversable.py", line 221, in
unrestrictedTraverse
next=obj[name]
File "/usr/local/zenoss/zenoss/lib/python/OFS/ObjectManager.py", line 713, in
__getitem__
raise KeyError, key
KeyError: '2008'
-------------------- m2f --------------------
Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=38666#38666
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
