Univention Bugzilla – Bug 44915
Update aborted due to detected problems sysv-rc.postinst
Last modified: 2017-07-26 14:38:55 CEST
Update aborted on customer system (DC slave) from 4.1-4 to 4.2-0: Looks like a dependency loop of the init.d scripts was found by insserv and this killed the update. ---[cut]--- Entpacken von sysv-rc (2.88dsf-59A~4.2.0.201703021459) über (2.88dsf-41.43.201408220944) ... sysv-rc (2.88dsf-59A~4.2.0.201703021459) wird eingerichtet ... info: Reordering boot system, log to /var/lib/insserv/run-20170630T1223.log error: Something failed while migrating. error: Unable to migrate to dependency based boot sequencing. See http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot for more information about dependency based boot sequencing. To reattempt the migration process run 'dpkg --configure sysv-rc'. dpkg: Fehler beim Bearbeiten des Paketes sysv-rc (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Fehler traten auf beim Bearbeiten von: sysv-rc ---[cut]--- After moving /etc/init.d/univention-directory-policy away, it was possible to continue the update and the postinst of sysv-rc ran successfully. Afterwards the new version was moved back and now it looks okay.
Created attachment 8990 [details] Logfile mentioned in the postinst output (consecutive, duplicate lines have been removed via "uniq")
Same issue here at another customer environment. UCS: 4.1-4 errata439 App Center compatibility: 4 Installed: squid=3.1
Created attachment 9003 [details] insserv/run-20170706T1550.log
We should "fix" it in our 4.2-0 preup.sh script.
Again in Ticket 2017071721000475
again in Ticket 2017072021000441
(In reply to Nico Stöckigt from comment #6) > again in Ticket 2017072021000441 in this environment also 'univention-saml' had to been moved away to do the trick!
Added a check to preup.sh (on test mirror and in SVN) to try to detect these kind of problems before the update.
again in a customer environment (started with UCS 3.1) both init-scripts are conflicting. - univention-directory-policy - univention-saml
(In reply to Tobias Birkefeld from comment #3) > Created attachment 9003 [details] > insserv/run-20170706T1550.log according to the log these init-scripts depends on plymouth which is removed from system.
*** Bug 44924 has been marked as a duplicate of this bug. ***
We could also check the insserv --dryrun output for messages like insserv: script postfix: service mail-transport-agent already provided! Additionally we could make all init scripts have the "INIT INFO" headers in 4.1-4 already to not have race conditions during the update.
Created attachment 9058 [details] exim4 Reproducible with: * UCS 4.1- copy the exim4 init script to /etc/init.d/ * insserv -n returns 0 * start update to 4.2 * postfix will fail (although the new "insserv" -n returns 0, insserv -n postfix fails, and this is what update-rc.d postfix defaults calls, and this is started in postfix.postinst during the update)
OK, works, please copy this to updates.software-univention.de
(In reply to Felix Botner from comment #14) > OK, works, > > please copy this to updates.software-univention.de done
OK
new version is public