Bug#312810: Apache2 consumes 100% CPU after several LDAP authenticated requests
Geert Nijpels wrote:
>
> It looks like this problem is related to bug #307567. Apache starts
> consuming 100% CPU after some requests. Restarting Apache lets it serve
> pages for a few minutes again.
>
> Downgrading to apache* 2.0.54-2 fixed the problem. We use
> apache2-mpm-prefork on an up-to-date sarge installation.
Well, that's just bizarre, since 2.0.54-2 is the version with the new
util_ldap code from upstream, while 2.0.54-4 is completely reverted to the
tried and tested code from 2.0.53 and previous. Everyone else (so far)
has found 2.0.54-4 to be much more stable and useable.
Are you pushing a LOT of LDAP requests through apache2? If so, I could
see how the 2.0.53 (2.0.54-4) code might eventually lead to a bunch of
hung connections (though, it's always been like this), but you'd have to
be pushing a LOT of LDAP requests through, or have a serious CPU/RAM
shortage for it to spike your system really badly.
At any rate, given everyone else's track record so far with these
versions, I think it's safe to say that the version in Sarge will stay as
it is, however in Sid we will be getting apache2 2.0.55 soon, which has
the newer code (with LDAP connection timeouts), but it's actually meant to
work now, rather than randomly segfaulting and spiking the CPU.
... Adam
Reply to: