Univention Bugzilla – Bug 48121
timestamps are missing in updater.log
Last modified: 2020-07-13 10:46:51 CEST
There is a sudden change in the 'updater.log' but we can't track down the circumstances because there is no according timestamp. In this incident there is no update available but in the UMC a message is telling the opposite. ============================================================ Starting univention-upgrade. Current UCS version is 4.3-2 errata291 Checking for package updates: none Checking for app updates: none Checking for release updates: none Starting univention-upgrade. Current UCS version is 4.3-2 errata291 Checking for package updates: none Checking for app updates: none Checking for release updates: none Starting univention-upgrade. Current UCS version is 4.3-2 errata291 Checking for package updates: found Please rerun command without --check argument to install. Starting univention-upgrade. Current UCS version is 4.3-2 errata291 Checking for package updates: found Please rerun command without --check argument to install. ============================================================ Would be easier if the log tells when... ============================================================ 29.10.2018 8:00:02.156 - Starting univention-upgrade. Current UCS version is 4.3-2 errata291 Checking for package updates: none Checking for app updates: none Checking for release updates: none 05.11.2018 8:00:03.034 - Starting univention-upgrade. Current UCS version is 4.3-2 errata291 Checking for package updates: found Please rerun command without --check argument to install. ============================================================
This is still true in 4.4 and very annoying. The problem is in base/univention-updater/python/univention-upgrade. In main() a logger is defined (with a timestamp), but it is never used! The function that is actually used to log is: print >>logfd, msg