[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Locker killed to resolve a deadlock

To: Jorgen Lundman <lundman@lundman.net>, openldap-technical@openldap.org
Subject: Re: Locker killed to resolve a deadlock
From: Quanah Gibson-Mount <quanah@symas.com>
Date: Fri, 22 Sep 2017 08:17:11 -0700
Content-disposition: inline
In-reply-to: <WM!b03cc88e9b714810279bbfbf658c740c0e7e9cbef844b3435f7ad162ae4797b8f3094a3c5978b7eaf56721c0f346a91c!@mailstronghold-2.zmailcloud.com>
References: <f3d675b7-01bb-374d-d4fc-cb66c1c17321@lundman.net> <WM!b03cc88e9b714810279bbfbf658c740c0e7e9cbef844b3435f7ad162ae4797b8f3094a3c5978b7eaf56721c0f346a91c!@mailstronghold-2.zmailcloud.com>

--On Friday, September 22, 2017 4:26 PM +0900 Jorgen Lundman<lundman@lundman.net> wrote:

This has started to cause trouble, in the last month or so. The errors
are:

Sep 22 06:08:26 vmx02 slapd[14039]: [ID 960831 local4.debug] =>
bdb_idl_delete_key: c_get failed: DB_LOCK_DEADLOCK: Locker killed to
resolve a deadlock (-30994)

These can be safely ignored. See<http://www.openldap.org/lists/openldap-software/200810/msg00055.html>



--Quanah

--

Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>

Follow-Ups:
- Re: Locker killed to resolve a deadlock
  - From: Jorgen Lundman <lundman@lundman.net>

References:
- Locker killed to resolve a deadlock
  - From: Jorgen Lundman <lundman@lundman.net>

Prev by Date: Re: Olc deployment vs slapd.conf based deployment
Next by Date: Re: slapd: null_callback : error code 0x14
Index(es):
- Chronological
- Thread