I'm experiencing something similar. If I catch it early enough, I can
ssh and kill processes and restart apache and lasso which gets things
going again. Error log shows thousands of "child process xxxx still
did not exit, sending a SIGTERM". reinstalled apache and lasso and a
day later same thing. Haven't come up with a solution yet. right now
cron is periodically restarting both apache and lasso services.
Getting ready to move all sites from that server to another one in
case there's a disk problem.
I know this isn't helpful but at least you know that the problem
exists elsewhere.
Tim Taplin
On Nov 26, 2008, at 12:29 PM, Steve Upton wrote:
>
> Hi All,
>
> This morning one of our web servers (OS X 10.4, Lasso 8.5.5, Apache
> 1.x) choked on over 500 httpd processes. I couldn't kill them no
> matter what I tried, no pages were being served and I couldn't soft-
> reboot the machine.
>
> Finally a power cycle cleared things up.
>
> Has anyone else seen this problem? Any idea what might cause it or
> how it can be detected / guarded against?
>
> thanks!
>
> Steve
>
>
>
> --
>
>
> --
> This list is a free service of LassoSoft:
http://www.LassoSoft.com/> Search the list archives:
http://www.ListSearch.com/Lasso/Browse/> Manage your subscription:
http://www.ListSearch.com/Lasso/>
--
This list is a free service of LassoSoft:
http://www.LassoSoft.com/Search the list archives:
http://www.ListSearch.com/Lasso/Browse/Manage your subscription:
http://www.ListSearch.com/Lasso/
Locked
