From: "Ludovic Courtès" <ludo@gnu.org>
To: Jesse Gibbons <jgibbons2357@gmail.com>
Cc: 43011@debbugs.gnu.org
Subject: bug#43011: unattended-upgrade fails and doesn't log why
Date: Mon, 24 Aug 2020 23:26:58 +0200 [thread overview]
Message-ID: <87o8mzzqe5.fsf@gnu.org> (raw)
In-Reply-To: <27e5ca8d-0595-b2e4-fd87-5487aa206214@gmail.com> (Jesse Gibbons's message of "Sun, 23 Aug 2020 18:58:34 -0600")
Hi Jesse,
Jesse Gibbons <jgibbons2357@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’.
prev parent reply other threads:[~2020-08-24 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 0:58 bug#43011: unattended-upgrade fails and doesn't log why Jesse Gibbons
2020-08-24 21:26 ` Ludovic Courtès [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8mzzqe5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=43011@debbugs.gnu.org \
--cc=jgibbons2357@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).