Univention Bugzilla – Bug 36672
How to handle a failed release upgrade
Last modified: 2020-07-02 17:20:24 CEST
A SDB article is missing which describes what an Admin could do if the release upgrade to a new UCS version failed. Currently, the preup refers to 'dpkg --configure -a'. This should be replaced with a link to the new SDB article. We could start with: 1. dpkg --configure -a 2. Re-run univention-upgrade 3. Activate new version in sources.list, e.g. python2.6 /usr/sbin/ucr set version/version=4.0 version/patchelevel=0 apt-get -f install # check output ...
From a 3.1-1 to 3.2 test upgrade configured to not write apport reports Fehler traten auf beim Bearbeiten von: winbind univention-samba univention-samba-slave-pdc E: Sub-process /usr/bin/dpkg returned an error code (1) root@test:~# dpkg --configure winbind winbind (2:3.6.8-1.601.201311261618) wird eingerichtet ... Starting the Winbind daemon: winbind failed! invoke-rc.d: initscript winbind, action "start" failed. dpkg: Fehler beim Bearbeiten von winbind (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Fehler traten auf beim Bearbeiten von: winbind root@test:~# ps -ef | grep -i winbin root 2862 9272 0 12:29 pts/2 00:00:00 grep -i winbin root 12865 1 0 08:27 ? 00:00:00 /usr/sbin/winbindd root 13062 12865 0 08:28 ? 00:00:00 [winbindd] <defunct> root 13063 12865 0 08:28 ? 00:00:00 [winbindd] <defunct> root 13309 12865 0 08:28 ? 00:00:00 [winbindd] <defunct> root 16515 12865 0 08:37 ? 00:00:00 [winbindd] <defunct> root 18250 12865 94 08:42 ? 03:32:39 /usr/sbin/winbindd root@test:~# /etc/init.d/winbind stop Stopping the Winbind daemon: winbind. root@test:~#
First draft online
Changes and improvements for SDB entries aren't tracked in Bugzilla anymore, so I close these entries. Please comment on help.univention.com or get in touch with the Univention Support team in case you have any suggestions for the SDB.