I'm still relatively new to using zenoss but bumped into the issue that is described. As part of running the system through tests to see if I wanted to use it I set up a basic httpd process monitor for a linux box of mine. I modeled the system while httpd was on and had the httpd process show up as a monitored item. Then I turned the httpd down, did a #zenprocess run, and watched the httpd go into an alert state. Next I turned the httpd back on, did another zenprocess run and it still showed as down.
I wasted a good day playing with this but I think I came to understand a little better how the system operates. I think when modeling happens the system will take inventory of process id's, store them in a db table (probably) and then compare them with what was obtained from the zenprocess run command. I only launched zenprocess by hand because I didn't want to wait for the system to automatically do it every couple of minutes. Anyway, when I turned the httpd down and then back on again I think I got new process id's. Zenoss apparently is not smart enough to figure out that an outage is over and that it should relearn what the process id's are...I'm not blaming zenoss here (this should be something that the developers should work on though...a workflow or business logic should be built in to address this). The fix for me was to move the events to history (not really needed but I like to tidy things up), then re-model the device in question once I've made certain the system is operational again. So far the system appears to be doing what it is supposed to...you just have to spend some time learning how to deal with its quirks. There really needs to be an operations manual on how to use this thing in real world scenarios. I'll be writing one for myself and my team if zenoss passes my requirements tests. Zenoss should consider hiring me to write it. lol -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=23394#23394 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
