unattended-upgrade fails and doesn't log why

  • Done
  • quality assurance status badge
Details
2 participants
  • Jesse Gibbons
  • Ludovic Courtès
Owner
unassigned
Submitted by
Jesse Gibbons
Severity
normal
J
J
Jesse Gibbons wrote on 24 Aug 2020 02:58
(address . bug-guix@gnu.org)
27e5ca8d-0595-b2e4-fd87-5487aa206214@gmail.com
An example is the attached log. It says the process failed with status
1, but it doesn't say what failed or even reference a log in
/var/log/guix. The only way to find out what could have caused it is to
run the command, which might not fail the second time if it was a
network error or (IIUC) if the issue was fixed between failure and retry.
[2020-08-23T01:30:00-0600] starting upgrade...
command "/gnu/store/a3qjvkp2z4h96ycc9afir5yrqbbsixbf-guix-1.1.0-18.218a67d/bin/guix" "time-machine" "-C" "/gnu/store/qkccph0zyh7nmwab6hisbhya7agsfb3y-channels.scm" "--" "system" "reconfigure" "/run/current-system/configuration.scm" failed with status 1
L
L
Ludovic Courtès wrote on 24 Aug 2020 23:26
(name . Jesse Gibbons)(address . jgibbons2357@gmail.com)(address . 43011@debbugs.gnu.org)
87o8mzzqe5.fsf@gnu.org
Hi Jesse,

Jesse Gibbons <jgibbons2357@gmail.com> skribis:

Toggle quote (7 lines)
> An example is the attached log. It says the process failed with status
> 1, but it doesn't say what failed or even reference a log in
> /var/log/guix. The only way to find out what could have caused it is
> to run the command, which might not fail the second time if it was a
> network error or (IIUC) if the issue was fixed between failure and
> retry.

The logging issue is fixed by commit
fe42e5f39c9b36f02beec246b376a50e41114b84. At least you should now have
useful output in /var/log/unattended-upgrade.log.

Make sure to reconfigure and to ‘herd restart mcron’ by Sunday. :-)

Let us know how it goes!

Thanks,
Ludo’.
L
L
Ludovic Courtès wrote on 28 Aug 2020 23:31
control message for bug #43011
(address . control@debbugs.gnu.org)
87mu2emp8t.fsf@gnu.org
tags 43011 fixed
close 43011
quit
?