On 11/04/2013 08:05 AM, Jan Tomasek wrote:
Hi Rich,

On 11/01/2013 04:28 PM, Rich Megginson wrote:
If there is 30 or more parallel connections 389 hangs for ever. Very
often killing process ldapsearch process does not help. Server is very
often unable to restart so I have to kill it with -9.

Please provide a stack trace - http://port389.org/wiki/FAQ#Debugging_Hangs

stack trace is attached.

I'm running:

[root@pdap ~]# yum list installed |grep 389
389-admin.x86_64                   1.1.29-1.el6 @epel
389-admin-console.noarch           1.1.8-1.el6 @epel
389-admin-console-doc.noarch       1.1.8-1.el6 @epel
389-adminutil.x86_64               1.1.15-1.el6 @epel
389-console.noarch                 1.1.7-1.el6 @epel
389-ds.noarch                      1.2.2-1.el6 @epel
389-ds-base.x86_64                 1.2.11.15-22.el6_4 @updates
389-ds-base-libs.x86_64            1.2.11.15-22.el6_4 @updates
389-ds-console.noarch              1.2.6-1.el6 @epel
389-ds-console-doc.noarch          1.2.6-1.el6 @epel
389-dsgw.x86_64                    1.1.10-1.el6 @epel

Thank you

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  0x00007f60f0b4209d in waitpid () from /lib64/libpthread.so.0
No symbol table info available.
#1  0x00007f60e033f2c1 in ?? () from /lib/security/pam_script.so
No symbol table info available.
#2  0x00007f60e033f68a in pam_sm_authenticate () from /lib/security/pam_script.so
No symbol table info available.
#3  0x00007f60e8aa2cee in ?? () from /lib64/libpam.so.0
No symbol table info available.
#4  0x00007f60e8aa2600 in pam_authenticate () from /lib64/libpam.so.0
No symbol table info available.
#5  0x00007f60e8cb1e24 in ?? () from /usr/lib64/dirsrv/plugins/libpam-passthru-plugin.so
No symbol table info available.
#6  0x00007f60e8cb22ca in pam_passthru_do_pam_auth () from /usr/lib64/dirsrv/plugins/libpam-passthru-plugin.so
No symbol table info available.

It holds the lock in pam_passthru_do_pam_auth which causes all of the other threads to block.

Why is the script not exiting?



--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users