Ah, as you'll note from the stacktraces in fact, I've managed to turn on
connection debug output and am also attaching the section of "errors" for the
same period of time that contains all the conncection logging info...
Interestingly, it registers a few new "connections" during the pause:
[24/Jul/2014:13:54:56 +0000] - new connection on 278
[24/Jul/2014:13:54:58 +0000] - new connection on 165
[24/Jul/2014:13:54:59 +0000] - new connection on 182
[24/Jul/2014:13:55:02 +0000] - new connection on 190
[24/Jul/2014:13:55:04 +0000] - new connection on 165
and then a a few dozen new conenctions at 13:55:06 when the flood gates seem to re-open.
On Thu, Jul 24, 2014 at 11:08:15AM -0400, Thomas Walker wrote:
On Wed, Jul 23, 2014 at 06:23:24PM -0600, Rich Megginson wrote:
> Not sure. This is a complex area.
> Are you using IdM/FreeIPA or just plain 389?
Just plain old 389 (backend for sssd) with a load balancer inbetween (which is flapping
when we get erratic response times to simple bind attempts).
A lightly loaded server is fine but once we get more than a frew dozen connections, the
pauses become a real problem...