On 06/01/2011 02:02 PM, Howard Chu wrote:
Kartik Subbarao wrote:
On 06/01/2011 09:08 AM, Kartik Subbarao wrote:
Update: It's not a locks issue.
Another update -- after I reduced the idletimeout to 60 seconds, the
problem seems to have gone away. It would still be useful to know what
might be causing this problem and to be able to support higher levels of
idletimeout, but at least I have another workable option now.
As usual, when investigating a hang, you should attach to slapd with gdb
and get a snapshot of what all the threads are doing. Working around it
before you know what caused it isn't all that useful in the long run.
Unfortunately this instance of slapd doesn't have debugging symbols
enabled (it's a stock Debian 2.4.25 slapd package), so I didn't think gdb
would be that helpful...But now that you mention it, I could probably get
some basic stack trace info that might yield some clues.
Thanks for the reminder :-)