Hello again!
It seems that new patch does not always honor the process limits.
For example I have this in my configuration:
<IfModule peruser.c>
ServerLimit 200
MaxClients 200
MinSpareProcessors 1
MinProcessors 5
MaxProcessors 150
MaxRequestsPerChild 10000
ExpireTimeout 30
IdleTimeout 10
MinMultiplexers 5
MaxMultiplexers 15
MultiplexerIdleTimeout 10
ProcessorWaitTimeout 10
</IfModule>
(I know the timeouts are very low, just don't want to wait for the
children to die)
So if I send a request spike to the server (10k requests for example)
and then wait for the idle timeout to kick in, then my server
environment will not always have 5 workers (which is my minimum limit).
In fact many cases I tested, my server environment has no workers at all.
The case actually gets worse as it sometimes works the same way with
multiplexers. I have been using this patch on my development server
(which has very low traffic) and sometimes if I just leave the server
running and check back later, then I see a dead server, because all the
multiplexers have died.
There are no errors or warnings about children segfaulting or anything
suggesting that server is killing the children by itself.
--
Taavi Sannik
DataCode OY
_______________________________________________
Peruser mailing list
[email protected]
http://www.telana.com/mailman/listinfo/peruser
