Viewing Incoming/6678
Full headers

Major security issue: yes  no

Notes:
not enough info
Notification:

Date: Wed, 20 Oct 2010 08:33:54 +0000
From: Frank.Offermanns@caseris.de
To: openldap-its@OpenLDAP.org
Subject: slapd.exe does not respond anymore

Full_Name: Frank Offermanns
Version: 2.4.23
OS: Windows
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (217.6.189.243)


We are using OpenLDAP 2.4.23 on windows.

We are doing a lot of LDAP work every morning at 5 AM. About every 3rd day the
slapd.exe hang's up while doing this work.
The LDAP client then also hangs. The search never comes back. 
It is no longer possible to bind to the server. Slapd.exe can't be stopped
regulary (must be terminated). 
After restart of slapd.exe everything works fine.
It does not matter if we specify a (search/open) timeout at client side - it
always hangs. The log attached is without timeout. 
It also does not matter if replication is configured or not (currently
replication is activated).

I have uploaded a part of the slapd.log (with loglevel 264) and my configuration
file as Frank-Offermanns-101020.log and Frank-Offermanns-101020.conf.
To better analyse the log at 5 AM I added timestamps to the logging. 

At the attached log you can watch the way of "conn=3005" which results in a
search, which never comes back. 

Would it make sense to adjust the loglevel. If so what loglevel would be
helpfull? 

Followup 1

Date: Thu, 30 Dec 2010 16:47:08 -0800
From: Howard Chu <hyc@symas.com>
To: openldap-its@openldap.org
Subject: ITS#6678

The best thing to do in a hang situation is to attach to the server with gdb 
and get a stack trace of all of the active threads.

http://www.openldap.org/faq/data/cache/59.html

-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/