Bug 56887 - Automatic updates do not write any logs to updater.log
Automatic updates do not write any logs to updater.log
Status: NEW
Product: UCS
Classification: Unclassified
Component: Update - univention-updater
UCS 5.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2023-11-30 14:44 CET by Christina Scheinig
Modified: 2023-11-30 18:04 CET (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.069
Enterprise Customer affected?:
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2023113021000055
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christina Scheinig univentionstaff 2023-11-30 14:44:28 CET
A customer has automatic updates installed. Unfortunately a regression hit them, but nothing was logged to updater.log.
Reproducing this issue the normal update way the logfile shows meaningful logmessages, which would have helped during debugging

======================
updater.log:
libnss-winbind:amd64 (2:4.18.3-1A~5.0.0.202311271227) wird eingerichtet ...
First installation detected, adding winbind to /etc/nsswitch.conf...
======================
Comment 1 Philipp Hahn univentionstaff 2023-11-30 14:59:57 CET
Look in /var/log/apt/history.log and /var/log/apt/term.log; that's a feature of APT itself.
Comment 2 Christina Scheinig univentionstaff 2023-11-30 18:04:22 CET
I checked /var/log/apt/history.log and /var/log/dpkg.log and there was nothing like this
libnss-winbind:amd64 (2:4.18.3-1A~5.0.0.202311271227) wird eingerichtet ...
First installation detected, adding winbind to /etc/nsswitch.conf...
mentioned.
I have not checked term.log, because it was never helpful for me before!