I hope I'm not speaking too fast, but I think I "fixed" it. It seems it was the zenping daemon itself who could not follow (weird, because we only monitor 10 servers or so). I got no errors in zenping.log, zenstatus.log or events about the zenping daemon, so in typical zenoss fashion it was more about randomly changing settings and seeing things improve.
I changed: * Maximum Ping Packets in Flight: 75 -> 200 * Process Parallel Jobs: 10 -> 20 I haven't had a device down event for the last 40 minutes so I hope it stays okay.. -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=38199#38199 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
