Univention Bugzilla – Bug 47592
Allow examination of updater.log when a release update failed
Last modified: 2018-08-22 14:26:26 CEST
After a release update failed (e.g., due to a PREUP check), the update is aborted. The user (hopefully) finds details in the updater.log. This file cannot be examined in UMC except during the very release update. Suggestion: Parse /var/lib/univention-updater/univention-updater.status. If status=FAILED, allow opening the log file in the Updater module.
Becomes particularly important when no log file is shown during release update ("Maintenance mode").
Fixed in univention-updater 13.0.1-56A~4.3.0.201808151350 A warning is shown when the last release update failed. The UMC module then shows a "View log file" button which loads the last updater.log. Two notes: 1. I decided to put the information in the rather unrelated "updater/maintenance_information" call. The reason is that I sometimes witnessed multiple updater module processes being created if too many UMCP commands were called at once. 2. On my machine, the updater.log rotated out before I finished the work on the bug. This led me to add a clumsy sentence about log rotation. Also, if this happens, UMC does not give the Administrator any chance of looking into the "correct" log file; this would have to be done on the terminal. Yet, my guess is that the new feature shows the log file of interest most of the times as the button should be clicked quickly after the update failed.
Package installed: OK Advisories&Changelog: OK Possibility to view log in Updater Module: OK (*) (*) There is no warning about log rotation in UMC. This messages got removed again.
<http://errata.software-univention.de/ucs/4.3/210.html>