[users@httpd] Re: Apache spawns hundreds of processes, logging problem?

[meer <s....@gmail.com>]

Vincent Bray napisał(a):
> What are you using for the log rotation? In case it's a disk error,
> check your /var/log/messages for the time the problem's occuring?

Apache logs are rotated by system's logrotate daemon and there are no 
interesting entries in /var/log/messages.

> Apache logs requests as the final stage of processing, and any
> blockage here will lead to the process build up you're seeing.
> Requests will still get services, but only until you either run out of
> memory or hit MaxClient (which should happen first if the value is set
> correctly).

To be completely honest, I don't really know what to do in this 
situation... the system was always fully functional and now It acts like 
this. I applied an connlimit to the firewall but it didn't work also.

-- 
meer


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: [users@httpd] Re: Apache spawns hundreds of processes, logging problem?

[Vincent Bray <no...@gmail.com>]

On 13/08/07, meer <s....@gmail.com> wrote:
> Vincent Bray napisał(a):
> > What are you using for the log rotation? In case it's a disk error,
> > check your /var/log/messages for the time the problem's occuring?
>
> Apache logs are rotated by system's logrotate daemon and there are no
> interesting entries in /var/log/messages.

logrotate typically sends the server -HUP, meaning 'restart', rather
than -USR1 meaning 'gracefully restart'. The difference being that the
former kills existing connections and the later doesn't. In both cases
the parent process isn't restarted. However it isn't clear that this
issue has anything to do with log rotation.. Does the problem happen
while the logs are being rotated?

Assuming that the restart is failing somehow, try watching the blocked
processes using strace, or your system's equivalent.

http://httpd.apache.org/dev/debugging.html

> To be completely honest, I don't really know what to do in this
> situation... the system was always fully functional and now It acts like
> this. I applied an connlimit to the firewall but it didn't work also.

What gave you the impression that the processes were blocked waiting
on the logging phase? Can you post strace output?

-- 
noodl