[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Upgrade to 2.4.35 Causes Instability, Errors
- To: openldap-technical@openldap.org
- Subject: Upgrade to 2.4.35 Causes Instability, Errors
- From: Tim Gustafson <tjg@ucsc.edu>
- Date: Wed, 17 Jul 2013 07:34:18 -0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ucsc.edu; s=ucsc-google; h=mime-version:date:message-id:subject:from:to:content-type; bh=n/4FaxMpxk7sz9fCRPPxWZ3O1ukPj3UPIFCac0s7zzw=; b=ZxmEABWldJ5tSuwSkWtY2AG3b9kgrDrjbkJ6/kjynATlAqTQRwMZOWRs1007pB5L9M +Gm9rVd1g7UNQoLmKCbNEvDp4GK729wXRj1V6wh5he5LMH/15jTTyrXfqp2DOge0ovD2 J7GQdMRcbhssx4RL8YMYDsEC/cBt62i0JA100=
I recently upgraded OpenLDAP to 2.4.35 and I'm now experiencing some
instability issues, and also seeing a bazillion of the following error
in my log file:
bdb_dn2id_delete 0x108c68: delete failed: DB_LOCK_DEADLOCK: Locker
killed to resolve a deadlock -30995
I'm using the BDB backend at the moment. One Google search hit I
found suggested I switch to MDB instead. Would this help?
--
Tim Gustafson
tjg@ucsc.edu
831-459-5354
Baskin Engineering, Room 313A