30 seems rather low - we had a problem (since fixed) with our Atlassian
Crowd server (which we use to gateway JIRA, Stash, etc authentication to
389DS via LDAP) where it wouldn't release connections and would have 900+
connections before the 389DS server would stop accepting connections and
we'd ha
On 11/04/2013 09:08 AM, Jan Tomasek wrote:
On 11/04/2013 05:04 PM, Rich Megginson wrote:
Does the script open a connection to the same server it is being called
from?
Yes.
So this is a case of self-deadlock? I don't understand. What is it
exactly that you expect will happen?
--
389 use
On 11/04/2013 05:04 PM, Rich Megginson wrote:
Does the script open a connection to the same server it is being called
from?
Yes.
--
---
Jan Tomasek aka Semik
http://www.tomasek.cz/
--
389 users mailing list
389-us...@lists.fedoraproject.org
https://admin.fedoraproject.org/m
On 11/04/2013 09:00 AM, Jan Tomasek wrote:
On 11/04/2013 04:12 PM, Rich Megginson wrote:
Looks like you do not have the right debuginfo packages installed. But
there may be enough information in the stack trace anyway.
Your pam script is waiting:
Thread 11 (Thread 0x7f60c97ea700 (LWP 10146)):
#
On 11/04/2013 04:12 PM, Rich Megginson wrote:
Looks like you do not have the right debuginfo packages installed. But
there may be enough information in the stack trace anyway.
Your pam script is waiting:
Thread 11 (Thread 0x7f60c97ea700 (LWP 10146)):
#0 0x7f60f0b4209d in waitpid () from /li
