>From emailed replies I noticed that there are more people experiencing this
>problem, but so far nobody seems to know a real solution. I think it is an
>Apache 1.3-problem since the Apache is not reporting errors in the error_log
>about anything wrong with the other settings, say for the number of child
>processes. Accept for the fact that Apache doesn't accept as many connections
>as it should according to the MaxClients setting nothing appears to be wrong.
Are the other people experiencing this problem running Linux too? If so,
track kernel versions, patch levels etc. and try to find a common thread.
Quote:>I've been unable to find a group dedicated to the Apache webserver, but since
>it's used so often I guess I must have overlooked it. Can anyone tell me
>which group it is... If there's anyone outthere that has the same kind of
>experiences, or hints in what direction I should look to solve or identify
>the cause, please post a reply...
Were you running any version of Apache in this same environment prior
to Apache 1.3.x? If so, did you notice any similar problem? If you
really think this is 1.3.x, you could try downgrading to 1.2.6 and
see if your problem goes away.
If this problem doesn't occur in 1.2.6, then report it as a bug in 1.3.x by
using the Apache bug database:
However, I would guess that this is something more subtle related to your