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