Try running zenperfsnmp with debug:
zenperfsnmp run -v 10 --cycle
For even more debug, at the beginning of zenperfsnmp.py, line 370, add a
line of debug:
'decode responses from devices and store the elements in RRD files'
# even more debugging
self.log.debug('storeValues %s %s', updates, deviceName)
proxy = self.proxies.get(deviceName, None)
You can also run zenperfsnmp on a single device:
zenperfsnmp run -v 10 -d troublesome-device
Finally, if you really want to find out what is going on, strace the
process for network events:
strace -e trace=network zenperfsnmp run -v 10 -d troublesome-device
I would be happy to pour through any of this if you want to send it on.
-Eric
Dennis B.Hopp wrote:
Is there any way I can determine what is causing this? I'm still getting these
messages and I have completely removed the AIX boxes from monitoring.
--Dennis
On Fri, 04 Aug 2006 15:15:32 -0400, Eric Newton <[EMAIL PROTECTED]> wrote:
It could if the oid list is long and some of the responses timeout
because the device does not respond.
-Eric
Dennis B.Hopp wrote:
On Fri, 04 Aug 2006 14:58:14 -0400, Eric Newton <[EMAIL PROTECTED]>
wrote:
Hi Dennis,
This message means "not all of the devices have responded for two
cycles: I'm going to start over with all the devices". We regularly
monitor 500 devices in a minute, so something is probably wrong. One
possibility is that your devices are down and they have not yet been
removed from the list of devices to be monitored by zenping.
None of my devices are down, but I am trying to add some AIX boxes and I
can't seem to get the OIDs right and so it's complaining about bad OIDs in
the Events, could this cause that?
--Dennis
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
