Paul Lesneiwski reportedly babbled: > > [EMAIL PROTECTED] wrote: >> Hi SM users, >> >> The problem: >> >> Intermittently SM would grab 100% of cpu. This was on a 4 processor machine, >> so /usr/bin/sar would show user-level cpu stepping up and down by 25%. >> Sometimes reaching all 4 cpus (100%). Systems staff would usually have to >> kill the runaway process ids on Monday morning. There was no obvious >> connection between times of start of cpu hogging and SM activity as logged >> on httpd access or error logs, but there was usually SM activity at most a >> few >> hours beforehand. >> >> We know it was SM related because cpu hogging started the day it was >> installed, >> and ceased when SM was turned off for a week. >> >> As open source advocates in an organization with Microsoft addicted >> system support department, this has proved to be quite an >> embarrassing episode. > > Sandy, > > Sorry no one had any ideas for you. I've never heard of this problem > but would be interested to know if you were able to track it down.
Interesting... I have a similar problem (same??) here. I am running FC1 on a Compaq dual Intel box, PHP 4.3.9, UW Imap 2004e, Apache 2.0.52 and SM 1.4.4. The box will ocasionally just flatline the cpu usage and the only way to "fix it" is to kill and restart Apache. So since I am pretty busy most of the time and have not gone into this further and the box is several hundred miles away and un attended, I have a cron job that just looks for cpu usage once every minute and if it is hosed up, I punch the webserver in the nose and restart it. But I know when it has happened because the web server will hang on the pending request and times out and I can't get any web pages until the cron job has figured out that the web server needs to be restarted. When it times out and the cron job has happened, I can just hit refresh and everything works fine again.. until the next time. :-) Anybody else see anything like this?? -R -- ------------------------------------------------------------------------ Rich Hall [EMAIL PROTECTED] http://www.netlynx.us/rich/ ham radio: kf6arx ------------------------------------------------------------------------ No trees were destroyed in the sending of this message; however, a significant number of electrons were terribly inconvenienced. ------------------------------------------------------------------------ And remember - if it ain't broke, hit it again. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click -- squirrelmail-users mailing list Posting Guidelines: http://squirrelmail.org/wiki/wiki.php?MailingListPostingGuidelines List Address: [email protected] List Archives: http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
