From bf612ae1438bf792bc94a157e5915b3174a9f453 Mon Sep 17 00:00:00 2001 From: Mark Reynolds Date: Thu, 12 Oct 2017 16:04:02 -0400 Subject: [PATCH] Ticket 49402 - Server can hang at shutdown after backend with same name is deleted and re-created Bug Description: When an instance is destroyed, it checks if its busy, but it also sets the instance as busy while its being deleted, but it never unsets the busy flag. This can hang the server at shutdown. Fix Description: Set the instance as not busy after it's deleted from the config. https://pagure.io/389-ds-base/issue/49402 Reviewed by: ? --- ldap/servers/slapd/back-ldbm/ldbm_instance_config.c | 1 + 1 file changed, 1 insertion(+) diff --git a/ldap/servers/slapd/back-ldbm/ldbm_instance_config.c b/ldap/servers/slapd/back-ldbm/ldbm_instance_config.c index c2e49d5..7e7610b 100644 --- a/ldap/servers/slapd/back-ldbm/ldbm_instance_config.c +++ b/ldap/servers/slapd/back-ldbm/ldbm_instance_config.c @@ -1352,6 +1352,7 @@ ldbm_instance_delete_instance_entry_callback(Slapi_PBlock *pb __attribute__((unu "Bringing %s offline...\n", instance_name); slapi_mtn_be_stopping(inst->inst_be); dblayer_instance_close(inst->inst_be); + instance_set_not_busy(inst); slapi_ch_free((void **)&instance_name); return SLAPI_DSE_CALLBACK_OK; -- 2.9.5