Michel Jouvin wrote:
> Graham,
>
> I played a little bit with worker MPM parameters. In particular I tested
> your suggestion to increase to 2 StartServers. This has no effect on the
> problem. I also tried to raise MaxSpareThread to MaxClient and
> suppressed child recycling (MaxRequestPerChild=0) to suppress restart of
> child as it seems to trig the problem with mod_pyton. No effect.
>
> I also checked the load during all these tests. Almost no request. So
> the heavy load syndroma you described doesn't seem to apply in this case.
>
> Again, one month ago I tested during 2 or 3 days an Apache configuration
> with mod_python loaded and without any url to trig its usages. And the
> problem was already the same. So it seems this is not related to
> mod_python usage (it happens even if you didn't execute any Python code)
> but rather to mod_python interaction with other Apache components.
>
> Michel


Michel,

I'm not able to reproduce the behaviour on debian stable (i386) with
apache 2.0.54, but I'm not sure if I'm testing this correctly.

Could you create a test script (bash or python) that will produce the
error? That way I can know for sure that I'm testing in the same way.

Jim

[ Post a follow-up to this message ]