Univention Bugzilla – Bug 37782
UMC updater fails immediately without feedback if another update process runs
Last modified: 2019-01-03 07:17:47 CET
When installing a release upgrade (e.g. update to 4.0-1) the UMC opens the logpane which shows no content and immediately fails when another univention-upgrade process currently runs. The UMC does not say that there is already a upgrade process. If i execute univention-upgrade via CLI it tells me: # univention-upgrade Another updater process is currently running - abort Locked by PID 32543. Check lockfile /var/lock/univention-updater The reason why univention-upgrade currently runs is a cronjob: root 3580 0.0 0.0 13408 316 ? Ss Jan22 0:08 /usr/sbin/cron root 32342 0.0 0.0 100808 0 ? S Feb01 0:00 \_ /USR/SBIN/CRON root 32358 0.0 0.0 4192 0 ? Ss Feb01 0:00 \_ /bin/sh -c [ -x /usr/share/univention-updater/univention-updater-check ] && /usr/sbin/jitter 600 /usr/share/univention-updater/univention-updater-check 2> /dev/nul l > /dev/null root 32359 0.0 0.0 9244 0 ? S Feb01 0:00 \_ /bin/bash /usr/share/univention-updater/univention-updater-check root 32543 0.0 0.0 44000 8 ? S Feb01 0:00 \_ /usr/bin/python2.7 /usr/sbin/univention-upgrade --check --setucr root 32546 0.0 0.0 4192 0 ? S Feb01 0:00 \_ /bin/sh -c univention-config-registry commit /etc/apt/sources.list.d/20_ucs-online-component.list; LC_ALL=C apt-get update >/dev/null; LC_ALL=C 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 -us dist-upgrade root 32547 0.0 0.0 33904 8 ? S Feb01 0:00 \_ /usr/bin/python2.7 /usr/sbin/univention-config-registry commit /etc/apt/sources.list.d/20_ucs-online-component.list root 32548 0.0 0.0 43468 4 ? S Feb01 0:00 \_ /usr/bin/python2.7 UMC should give the stdoutput of univention-upgrade in this case.
Happened again to me: root 30709 0.0 0.0 4188 0 ? Ss 13:05 0:00 \_ /bin/sh -c [ -x /usr/share/univention-updater/univention-updater-check ] && /usr/sbin/jitter 600 /usr/share/univention-updater/univention-updater-check 2> /dev/null > /dev/null root 30710 0.0 0.0 9228 0 ? S 13:05 0:00 \_ /bin/bash /usr/sbin/jitter 600 /usr/share/univention-updater/univention-updater-check root 31207 0.5 0.2 386292 2164 ? S 13:08 0:00 \_ /usr/bin/python2.7 /usr/sbin/univention-management-console-module -m updater -s /var/run/univention-management-console/31993-1450267698947.socket -d 2 -l en_US.UTF-8
Note: this happens also if apt is just blocked by the cronjob / jitter thing.
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016. Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.