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
--
-----------------------
Jan Tomasek aka Semik
http://www.tomasek.cz/