Ok.. So I have a monitored RHEL 4 server which up until last week was working fine. SNMP was configured properly, and the stats in Zenoss prove it.
However, all of a sudden, Zenoss decided that it couldn't get the CPU Idle stats, and now won't stop alerting on it, despite having done: a) restarted SNMP on the server and checked config hasn't changed b) removed the threshold (as per a previous post, potentially broken net-SNMP) c) deleted and re-created the device in Zenoss d) flushed the event cache, heartbeats and reloaded the event schema Even after "deleting" the device, flushing the cache etc, I re-add it, and it's as if I never removed it! What's even more annoying is that on the zenoss server, if I use snmpwalk to look at the mibs feeding the CPU Idle graph, i.e. 1.3.6.1.4.1.2021.11.50.0, it can pull down the data just fine using the same SNMP community as is configured within Zenoss. Before I wade into the MySQL database and delete any reference to this server, is there anything else I can try before I either reboot the machine I'm trying to monitor (not necessarily all that simple, it's semi-live) or kill off the zenoss database, and start again? -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=16405#16405 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
