GNU bug report logs - #43011
unattended-upgrade fails and doesn't log why

Previous Next

Package: guix;

Reported by: Jesse Gibbons <jgibbons2357 <at> gmail.com>

Date: Mon, 24 Aug 2020 00:59:02 UTC

Severity: normal

Tags: fixed

Done: Ludovic Courtès <ludo <at> gnu.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 43011 in the body.
You can then email your comments to 43011 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-guix <at> gnu.org:
bug#43011; Package guix. (Mon, 24 Aug 2020 00:59:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to Jesse Gibbons <jgibbons2357 <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Mon, 24 Aug 2020 00:59:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jesse Gibbons <jgibbons2357 <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: unattended-upgrade fails and doesn't log why
Date: Sun, 23 Aug 2020 18:58:34 -0600

[Message part 1 (text/plain, inline)]
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.

[unattended-upgrade.log (text/x-log, attachment)]
Information forwarded to bug-guix <at> gnu.org:
bug#43011; Package guix. (Mon, 24 Aug 2020 21:28:02 GMT) Full text and rfc822 format available.

Message #8 received at 43011 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Jesse Gibbons <jgibbons2357 <at> gmail.com>
Cc: 43011 <at> debbugs.gnu.org
Subject: Re: bug#43011: unattended-upgrade fails and doesn't log why
Date: Mon, 24 Aug 2020 23:26:58 +0200

Hi Jesse,

Jesse Gibbons <jgibbons2357 <at> gmail.com> skribis:

> 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’.
Added tag(s) fixed. Request was from Ludovic Courtès <ludo <at> gnu.org> to control <at> debbugs.gnu.org. (Fri, 28 Aug 2020 21:32:02 GMT) Full text and rfc822 format available.
bug closed, send any further explanations to 43011 <at> debbugs.gnu.org and Jesse Gibbons <jgibbons2357 <at> gmail.com> Request was from Ludovic Courtès <ludo <at> gnu.org> to control <at> debbugs.gnu.org. (Fri, 28 Aug 2020 21:32:02 GMT) Full text and rfc822 format available.
bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Sat, 26 Sep 2020 11:24:04 GMT) Full text and rfc822 format available.
This bug report was last modified 3 years and 206 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.