I have "resolved" this issue. I am documenting it here because the behavior may be interesting to the devs.
Looking at the logs, I noticed the following: Code: 2008-09-18 11:51:24 INFO zen.zenperfsnmp: total=15 good=0 bad=0 time=0.000038 2008-09-18 11:51:24 INFO zen.zenperfsnmp: total=15 good=1 bad=0 time=0.285671 2008-09-18 11:51:24 INFO zen.zenperfsnmp: total=15 good=2 bad=0 time=0.290306 2008-09-18 11:51:24 INFO zen.zenperfsnmp: total=15 good=3 bad=0 time=0.294834 2008-09-18 11:51:24 INFO zen.zenperfsnmp: total=15 good=4 bad=0 time=0.299367 2008-09-18 11:51:24 INFO zen.zenperfsnmp: total=15 good=5 bad=0 time=0.303916 2008-09-18 11:51:24 INFO zen.zenperfsnmp: total=15 good=6 bad=0 time=0.315542 2008-09-18 11:51:24 INFO zen.zenperfsnmp: total=15 good=7 bad=0 time=0.465231 2008-09-18 11:51:24 INFO zen.zenperfsnmp: total=15 good=8 bad=0 time=0.503591 2008-09-18 11:51:24 INFO zen.zenperfsnmp: total=15 good=9 bad=0 time=0.523892 2008-09-18 11:51:24 INFO zen.zenperfsnmp: total=15 good=10 bad=0 time=0.558961 2008-09-18 11:51:24 INFO zen.zenperfsnmp: total=15 good=11 bad=0 time=0.593691 2008-09-18 11:51:24 INFO zen.zenperfsnmp: total=15 good=12 bad=0 time=0.652868 2008-09-18 11:51:32 INFO zen.zenperfsnmp: total=15 good=12 bad=1 time=8.273533 2008-09-18 11:51:32 WARNING zen.zenperfsnmp: snmp agent down 2008-09-18 11:56:24 WARNING zen.zenperfsnmp: There are still 2 devices to query 2008-09-18 11:56:24 WARNING zen.zenperfsnmp: Problem devices: ['tourmalet.smilecontent.dk', 'hautcam.smilecontent.dk'] 2008-09-18 11:56:24 WARNING zen.zenperfsnmp: Waiting one more cycle period 2008-09-18 12:01:24 WARNING zen.zenperfsnmp: There are still 2 devices to query 2008-09-18 12:01:24 WARNING zen.zenperfsnmp: Problem devices: ['tourmalet.smilecontent.dk', 'hautcam.smilecontent.dk'] 2008-09-18 12:01:24 WARNING zen.zenperfsnmp: Devices status is not clearing. Restarting. As you can see, two seemingly unrelated hosts were not responding to SNMPv3 requests (because they were configured to use SNMPv2c). This, somehow, caused the zenperfsnmp process to kill and restart itself. This, in turn, caused the problem for my unrelated, correctly answering device. When I configured Zenoss to monitor the two hosts using SNMPv2c instead of v3, the problems went away. This behavior, however, is quite contrary to what one would expect. -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=25214#25214 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
