1 |
On Sat, 2003-04-12 at 22:45, Robin H.Johnson wrote: |
2 |
> On Sat, Apr 12, 2003 at 10:32:00PM +0200, Benjamin Podszun wrote: |
3 |
> > The Apache-Version is the same, so is the configuration. |
4 |
> > The only thing that I noticed is that one apache instance sucks up to |
5 |
> > 99% CPU... It never uses less than 30% .. |
6 |
> > And since this is a Compaq Server with Dual P3 1GHz and 2GB RAM I doubt |
7 |
> > that this is right (tm). |
8 |
> Do you use PHP (and possibly MySQL) on that machine? I saw that problem |
9 |
> on my Slackware box a few months ago. I never did find the solution tho, |
10 |
> as I upgraded to Apache2. I did confirm that the bug didn't occur when |
11 |
> PHP wasn't being used for me. For some reason, PHP seemed to be in a |
12 |
> massive loop after the page was sent, eating CPU and memory. |
13 |
|
14 |
Uhm.. Yes, I use Apache and PHP. MySQL as well, but not on that host (3 |
15 |
production servers, two of them only with apache/php, both compaq as |
16 |
stated above, the third only serves as DB-Server. Both Webserver have |
17 |
that problem. |
18 |
|
19 |
You upgraded to Apache2? I guess (hope?) that you don't talk about |
20 |
production environments? I tried to use Apache2 with PHP twice and |
21 |
wouldn't recommend it to anyone.. It's just buggy and not usable. As my |
22 |
current Gentoo-Servers are.. *cough* |
23 |
|
24 |
> A good temporary workaround is to have a little watcher shell script |
25 |
> that looks for any apache processes that have been eating >80% CPU for |
26 |
> the all of the last 30 seconds (I checked at 30 second intervals) and |
27 |
> send a SIGKILL to them. |
28 |
|
29 |
Well, that's an ugly hack.. Yes, thanks for the hint, but I already |
30 |
thought about something like this.. And I don't think that it solves a |
31 |
single problem, nor is it a suitable solution on a (I love this word) |
32 |
production environment. |