I just remembered that the postinst failure I mentioned in my previous post wasn't triggered by the restart of the slapd daemon, but rather by another step that the postinst script was attempting to do at that time.
So, in your case, did the apt upgrade/configure cycle appear to complete normally, and it wasn't until afterwards you discovered that the slapd daemon wasn't actually running?
(Similarly, James, did your "do-release-upgrade -d" process appear to finish normally, or did you get an error during the slapd package install that cause the release-upgrade to abort?)
I just remembered that the postinst failure I mentioned in my previous post wasn't triggered by the restart of the slapd daemon, but rather by another step that the postinst script was attempting to do at that time.
So, in your case, did the apt upgrade/configure cycle appear to complete normally, and it wasn't until afterwards you discovered that the slapd daemon wasn't actually running?
(Similarly, James, did your "do-release-upgrade -d" process appear to finish normally, or did you get an error during the slapd package install that cause the release-upgrade to abort?)