Bug 39683 - Update to UCS 4.1 fails due to failing slapd start
Update to UCS 4.1 fails due to failing slapd start
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: General
UCS 4.1
Other Linux
: P5 normal (vote)
: UCS 4.1
Assigned To: Stefan Gohmann
Arvid Requate
: interim-2
Depends on:
Blocks: 47452
  Show dependency treegraph
 
Reported: 2015-10-30 12:48 CET by Erik Damrose
Modified: 2018-08-06 17:34 CEST (History)
1 user (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Damrose univentionstaff 2015-10-30 12:48:40 CET
updater.log:
...
slapd (2.4.42+dfsg-2.207.201509161547) wird eingerichtet ...
...
invoke-rc.d: initscript slapd, action "start" failed.
dpkg: Fehler beim Bearbeiten von slapd (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück
Trigger für python-support werden verarbeitet ...
Fehler traten auf beim Bearbeiten von:
 slapd
E: Sub-process /usr/bin/dpkg returned an error code (1)
Error: Failed to execute "apt-get -o DPkg::Options::=--force-confold -o DPkg::Options::=--force-overwrite -o DPkg::Options::=--force-overwrite-dir --trivial-only=no --assume-yes --quiet=1 -u dist-upgrade"
exitcode of univention-updater: 1
ERROR: update failed.

slapd start failed because there was already a running slapd process. This is caused by listener modules, which perform a slapd graceful-restart instead of a crestart.

We should adapt umc-service-providers.py and ldap_extension.py
Comment 1 Stefan Gohmann univentionstaff 2015-10-30 20:04:04 CET
I've changed the following packages:

- univention-directory-logger/debian/post* r65019 + Changelog (r65025)
- univention-saml/univention-saml-schema.postinst: r65020 + Changelog (r65025)
- management/univention-management-console-frontend/92univention-management-console-web-server.inst: r65021 + No changelog, code is new
- management/univention-ldap/listener/ldap_extension.py: r65022 + Changelog (r65025)
- management/univention-management-console/umc-service-providers.py: r65023 + No changelog, code is new
Comment 2 Stefan Gohmann univentionstaff 2015-10-31 11:40:48 CET
It happened again but I don't see a slapd restarted triggered by any listener module, join script or package upgrade. I'll check and modify the slapd postinst.
Comment 3 Stefan Gohmann univentionstaff 2015-10-31 12:04:26 CET
r15407: The slapd is now stopped in the postinst before it will start again.
Comment 4 Arvid Requate univentionstaff 2015-11-03 16:46:33 CET
* r15407: Ok, despite beeing run with set -e the stop works:
  /etc/init.d/slapd stop; /etc/init.d/slapd stop && echo ok  -> ok

reopen for this:

univention-samba4.prerm  still contains a slapd restart. I guess it would be better to crestart there as well.


The other remaining restarts are probably not that relevant:
* univention-ad-connector-exchange.postinst
* univention-directory-manager-module-example-schema.postinst
* univention-demo-configuration.postinst
* univention-demo-configuration.postrm


The hard restart in univention-ldap-server.postinst is ok.
Changelog entries are Ok.
Comment 5 Stefan Gohmann univentionstaff 2015-11-03 17:09:43 CET
(In reply to Arvid Requate from comment #4)
> reopen for this:
> 
> univention-samba4.prerm  still contains a slapd restart. I guess it would be
> better to crestart there as well.

Fixed with: r65147
Changelog: r65148
Comment 6 Arvid Requate univentionstaff 2015-11-05 11:20:23 CET
Ok.
Comment 7 Stefan Gohmann univentionstaff 2015-11-17 12:12:10 CET
UCS 4.1 has been released:
 https://docs.software-univention.de/release-notes-4.1-0-en.html
 https://docs.software-univention.de/release-notes-4.1-0-de.html

If this error occurs again, please use "Clone This Bug".