Univention Bugzilla – Bug 46388
Upgrade to UCS 4.3 via UMC fails
Last modified: 2018-03-15 16:06:58 CET
I've started a upgrade from UUS 4.2-3 to 4.3 via UMC and the update was killed. It looks like the atd restart kills the at upgrade job: root@master421:~# tail -n 20 /var/log/univention/updater.log ; echo Entpacken von nscd (2.24-11+deb9u1) über (2.19-18+deb8u10) ... Vorbereitung zum Entpacken von .../libc6_2.24-11+deb9u1_amd64.deb ... Checking for services that may need to be restarted... Checking init scripts... Entpacken von libc6:amd64 (2.24-11+deb9u1) über (2.19-18+deb8u10) ... Trigger für systemd (215-17+deb8u7A~4.2.3.201801211553) werden verarbeitet ... Trigger für man-db (2.7.0.2-5) werden verarbeitet ... Trigger für libc-bin (2.19-18+deb8u10) werden verarbeitet ... libc6:amd64 (2.24-11+deb9u1) wird eingerichtet ... Checking for services that may need to be restarted... Checking init scripts... Restarting services possibly affected by the upgrade: slapd: restarting...done. saslauthd: restarting...done. smbd: restarting...done. postfix: restarting...done. openbsd-inetd: restarting...done. cron: restarting...done. atd: restarting... root@master421:~#
I've changed the sysetmd KillMode from control-group to process. That means systemd doesn't kill the atd child process. Thanks to Philipp for the hint. Fixed in preup.sh and postup.sh: https://git.knut.univention.de/univention/ucs/commit/5e2264dfd4163bc802e2adbaca01ff57f9b198fb * Ensure the at daemon is not restared during the release upgrade. Otherwise the upgrade is killed if it was started via UMC (Bug #46388) Changelog: https://git.knut.univention.de/univention/ucs/commit/42369ef03968ae260cbb84f4fff3213039c4a3bb https://git.knut.univention.de/univention/ucs/commit/2ce4bdf0b272f2abecc9f821a841570c95050371
Ok, works and changelog is ok.
UCS 4.3 has been released: https://docs.software-univention.de/release-notes-4.3-0-en.html https://docs.software-univention.de/release-notes-4.3-0-de.html If this error occurs again, please use "Clone This Bug".
*** Bug 46058 has been marked as a duplicate of this bug. ***