Ok, I've done some debugging (yay for free software), and I think I've figured it out.
Briefly, the problem seems to be that Zenoss first (1) retrieves a list of the names of all processes, and then (2) a list of the arguments of all processes (probably because the structure of the SNMP MIB makes it easier that way). Then it combines the two to check for running processes. If a process happens to start or terminate between (1) and (2), it will only appear in one of the two lists - then Zenoss will not find it, because it assumes that there is a 1-to-1 correspondence between the two lists. Of course, this only occurs if you let Zenoss check process name _and_ parameters (i.e. "Ignore Parameters=False" for the Process class in Zenoss). Also, it only happens occasionally, and only if you have processes that appear/disappear frequently. I guess that's why it's escaped the testers so far. For details, see trac: http://dev.zenoss.org/trac/ticket/1683 ------------------------ Sebastian Leske -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=7226#7226 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
