Daniel, all,
Just wanted to post the solution to this issue. I wanted to wait a significant
amount of time to make sure we had this solved.
The root caused was the LDAP Caching mechanism. I am guessing there is a bug in
that code that causes the server to go haywire after n-number of items being
2015-01-30 1:03 GMT+01:00 Mark Jacquet :
> Problem: Apache server will stay up for random amount of time, usually
> days, but eventually enters a hung state. When hung the CPU load gradually
> spikes on the machine
> and new web server requests are unresponsive.
>
> Error logs typically contain l
Problem: Apache server will stay up for random amount of time, usually days,
but eventually enters a hung state. When hung the CPU load gradually spikes on
the machine
and new web server requests are unresponsive.
Error logs typically contain lots of these:
Wed Jan 28 16:06:58.667188 2015]
