On Sat, 2003-04-12 at 22:45, Robin H.Johnson wrote:
> On Sat, Apr 12, 2003 at 10:32:00PM +0200, Benjamin Podszun wrote:
> > The Apache-Version is the same, so is the configuration.
> > The only thing that I noticed is that one apache instance sucks up to
> > 99% CPU... It never uses less than 30% ..
> > And since this is a Compaq Server with Dual P3 1GHz and 2GB RAM I doubt
> > that this is right (tm).
> Do you use PHP (and possibly MySQL) on that machine? I saw that problem
> on my Slackware box a few months ago. I never did find the solution tho,
> as I upgraded to Apache2. I did confirm that the bug didn't occur when
> PHP wasn't being used for me. For some reason, PHP seemed to be in a
> massive loop after the page was sent, eating CPU and memory.

Uhm.. Yes, I use Apache and PHP. MySQL as well, but not on that host (3
production servers, two of them only with apache/php, both compaq as
stated above, the third only serves as DB-Server. Both Webserver have
that problem.

You upgraded to Apache2? I guess (hope?) that you don't talk about
production environments? I tried to use Apache2 with PHP twice and
wouldn't recommend it to anyone.. It's just buggy and not usable. As my
current Gentoo-Servers are.. *cough*

> A good temporary workaround is to have a little watcher shell script
> that looks for any apache processes that have been eating >80% CPU for
> the all of the last 30 seconds (I checked at 30 second intervals) and
> send a SIGKILL to them.

Well, that's an ugly hack.. Yes, thanks for the hint, but I already
thought about something like this.. And I don't think that it solves a
single problem, nor is it a suitable solution on a (I love this word)
production environment.