There appears to be an issue with jffnms leaving orphans behind. My system was running fine for 31 days, but this morning there were over 34,000 orphaned. These processes were mostly php or fping with a smattering of id and sendmail. These defunct processes are unkillable and brought my system to a crawl. I had to reboot to clear them.
>From what I understand the orphans are caused when a process forks a child and then exits before the child finishes. When this happens the forked process' parent changes to init, which should normally clean them up when they finish running. When a process is defunct before init inherits them, init is unable to clean them and they stay in the system forever or until the system is rebooted. The only reason I can think of for the child to be passed to init as defunct is high load causing a delay between when the real parent exits and the child finishes running with another delay between the parent exiting and the child being passed to init. The only solution I can see to this is to ensure that all children have completed before allowing the parent process to exit. I do not know which specific module left the orphans behind, but it must be one of the pollers as I am not running auto discovery on any hosts. Little problems like these are hardly enough to make me stop using this great product Javier, you should be proud of it. I just wanted to bring it to your attention. Regards; Brad -- Brad Hudson Systems Analyst [EMAIL PROTECTED] Telephone: (613) 694-2681 Fax: (613) 759-1651 ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ jffnms-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jffnms-users
