[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Locker killed to resolve a deadlock
- To: Quanah Gibson-Mount <quanah@symas.com>, openldap-technical@openldap.org
- Subject: Re: Locker killed to resolve a deadlock
- From: Jorgen Lundman <lundman@lundman.net>
- Date: Tue, 26 Sep 2017 08:56:16 +0900
- Dkim-filter: OpenDKIM Filter v2.10.3 mail.lundman.net B1A0912E9DE
- Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=lundman.net; s=dkim; t=1506383777; bh=zpIwnWKSrCmFPp92+BpexiqEo1L93QGBvMthBg2cjxk=; h=Subject:To:References:From:Date:In-Reply-To; b=FONUNGdO3aIyK38edNzhudkiuK9qJie8umCQv87lIdN2jXiAQLuvBiDIW0l/XCPHB iVM8QfIKcVnS8nu8+a0vR/RdHJ8ZCvjDtbUcixKgsCWIm7E0/z9jy4FtGmoAm5FrS7 XwcxBR/uCgCQvrD33K+Ye4FanVx+F1eVbDLOasys=
- In-reply-to: <9A332F98FDB129D03958FF0E@[192.168.1.30]>
- References: <f3d675b7-01bb-374d-d4fc-cb66c1c17321@lundman.net> <WM!b03cc88e9b714810279bbfbf658c740c0e7e9cbef844b3435f7ad162ae4797b8f3094a3c5978b7eaf56721c0f346a91c!@mailstronghold-2.zmailcloud.com> <9A332F98FDB129D03958FF0E@[192.168.1.30]>
- User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:56.0) Gecko/20100101 Firefox/56.0 SeaMonkey/2.53a1
Unfortunately, this is not our experience - although it is possible the
message is just a distraction.
slapd stops all syncrepl, and responding, until they call us to restart it.
Sep 22 06:07:49 vmx02. slapd[14039]: [ID 859137 local4.debug] slap_queue_cs
n: queing 4952b70 20170921210749.085779Z#000000#000#000000
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)
Sep 22 06:13:37 vmx02. last message repeated 36 times
Sep 22 06:13:44 vmx02. slapd[14039]: [ID 960831 local4.debug] =>
bdb_idl_delete_key: c_get failed: DB_LOCK_DEADLOCK: Locker killed to
resolve a deadlock (-30994)
Sep 22 06:20:17 vmx02. last message repeated 39 times
Sep 22 06:20:34 vmx02. slapd[14039]: [ID 960831 local4.debug] =>
bdb_idl_delete_key: c_get failed: DB_LOCK_DEADLOCK: Locker killed to
resolve a deadlock (-30994)
Sep 22 06:26:49 vmx02. last message repeated 39 times
Sep 22 06:27:00 vmx02. slapd[14039]: [ID 960831 local4.debug] =>
bdb_idl_delete_key: c_get failed: DB_LOCK_DEADLOCK: Locker killed to
resolve a deadlock (-30994)
Sep 22 06:33:32 vmx02. last message repeated 38 times
Sep 22 06:33:42 vmx02. slapd[14039]: [ID 960831 local4.debug] =>
bdb_idl_delete_key: c_get failed: DB_LOCK_DEADLOCK: Locker killed to
resolve a deadlock (-30994)
Sep 22 06:36:20 vmx02. last message repeated 15 times
Sep 22 06:36:27 vmx02. slapd[14039]: [ID 543694 local4.debug] daemon:
shutdown requested and initiated.
That's about 30 mins of slapd no longer doing work, and then we shoot it.
That is the only indicator we get that it is unresponsive, so we assumed it
is related. Is it also not strange to get deadlock resolve on, for example,
an ldapslave? There are no writers except syncrepl.
Lund
Quanah Gibson-Mount wrote:
>
> These can be safely ignored. See
> <http://www.openldap.org/lists/openldap-software/200810/msg00055.html>
>
>
> --Quanah
--
Jorgen Lundman | <lundman@lundman.net>
Unix Administrator | +81 (0)90-5578-8500
Shibuya-ku, Tokyo | Japan