Hey All,

I'm testing an upgrade from 2.2.0 to 2.2.3. I have three devices in Zenoss that 
are acting as global data collectors for our datacenters. I've built a custom 
RPM for them with SNMP pass-through scripts so I can gather metrics on our 
critical systems.

I have no problems with data collection and graphing in 2.2.0. All data points 
collect and graph flawlessly. 

When I upgrade to 2.2.3 and tail the zenperfsnmp log, I now see this:

2008-07-30 12:24:22 WARNING zen.zenperfsnmp: Problem devices: ['XXX 
Datacenter', 'XXX Datacenter', 'XXX Datacenter']

2008-07-30 12:24:22 WARNING zen.zenperfsnmp: Waiting one more cycle period

XXX == our location code (I blanked them out).

After the upgrade, some data points collect for these devices and others do not.

Why are these devices now 'Problem devices'? Is there any advanced data 
collection debugging I can do? If I set logseverity to 10 (debug), will that 
give me any useful info?

There are no errors in the zenbuild.log. This is a source install/upgrade. I've 
cleared the cache, deleted pickle files and all the usual suspects.

Thanks.




-------------------- m2f --------------------

Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=23071#23071

-------------------- m2f --------------------



_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to