These are basically the same issues I have been encountering in this thread: http://forums.zenoss.com/viewtopic.php?t=8997 (see my summary post about third one down.)
Using "top" I can see that the zenhub and zenmodeler process are consuming entire processors. I've found that if I stop or kill the zenmodeler process, and then restart the zenhub, most of the daemons (and the web site) function normally. (I have a separate issue with the zenwin and zeneventlog processes and have disabled wmi on all my windows servers to stop a segfault.) I found that if I run zenmodeler as a daemon, I get thousands of log entries stating: INFO zen.ZenModeler: Collecting for path /Devices If I use "zenmodeler run -v10" in the foreground, the process completes without error. In the interim, I am running zenmodeler manually to model the system. (You could schedule a cron job). Try shutting down zenoss (make sure all daemons are killed). Start zenoss, but immediately afterward, stop the zenmodeler. See if your system settles down after its initial data gathering, (Web site behaves normally. Errors in your logs disappear, etc.) If you have an incomplete model, run zenmodeler in the forground "zenmodeler run -v10". Once it completes, check you logs for errors. Out of curiosity, how many devices are you monitoring? [/list] -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=32359#32359 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
