6.3-STABLE Apache 2.0 uses high CPU when restarted....

[Mel]

On Thursday 21 February 2008 18:57:38 Forrest Aldrich wrote:

> >> Here's a recent output of "top" :
> >>
> >> PID USERNAME  THR PRI NICE   SIZE    RES STATE  C   TIME   WCPU COMMAND
> >> 94711 www         1 117    0 41036K 13852K RUN    0   1:43 98.69% httpd
> >>

Is this memory rising? If the below suggestion doesn't narrow down the 
problem, could you look into ktrace(1) and see what it's doing all this time?
You could also try to narrow down the problem, by looking at what request was 
served last by that child. Enable mod_info for that.

> The only thing I see are multiple lines of these errors in error_log:
>
> [Thu Feb 21 00:00:12 2008] [error] child process 63633 still did not
> exit, sending a SIGKILL
> [Thu Feb 21 00:00:12 2008] [error] child process 63634 still did not
> exit, sending a SIGKILL
> [Thu Feb 21 00:00:12 2008] [error] child process 63635 still did not
> exit, sending a SIGKILL
> [Thu Feb 21 00:00:12 2008] [error] child process 63636 still did not
> exit, sending a SIGKILL
> [Thu Feb 21 00:00:12 2008] [error] child process 63637 still did not
> exit, sending a SIGKILL
> [Thu Feb 21 00:00:12 2008] [error] child process 63983 still did not
> exit, sending a SIGKILL
> [Thu Feb 21 00:00:12 2008] [error] child process 64048 still did not
> exit, sending a SIGKILL
>
>
> Which is correct, as the process is not exiting.  For some reason it's
> hanging.  The old binary did not do this.
>
> I could try another system update today (make/build/install world and
> recompile the apache executable and dependencies) to see if this solves
> the problem...

I doubt it would help. I've seen this lots of times when the php module exit 
code is hanging. At the same time, the php CLI binary should be crashing on 
exit.
Re-order your modules, there's a thread about it in the archives. If it wasn't 
for that useless piece of crap ht-dig, I'd have a link for you. :p

Anyway, to test if it's this problem, run php -v and see if you get coredump. 
If you don't have CLI available, you could try disabling php in apache and 
see if the problem persists.
-- 
Mel