From: Richard Sent <richard@freakingpenguin.com>
To: Thom R Harmon <trharmon@proton.me>
Cc: help-guix@gnu.org
Subject: Re: guix pull/guix upgrade often fails over VPN with TLS error message
Date: Wed, 04 Sep 2024 14:41:34 -0400 [thread overview]
Message-ID: <8734mfi7mp.fsf@freakingpenguin.com> (raw)
In-Reply-To: <e60baeb0-166e-40f3-b9bb-5b9c504532df@proton.me> (Thom R. Harmon's message of "Thu, 22 Aug 2024 23:46:03 +0000")
Thom R Harmon <trharmon@proton.me> writes:
> Just closing the loop on this...
>
> So, nobody had any advice as to how to troubleshoot this and I stopped
> looking for root cause and started looking for a fix of any sort. Turns
> out that was to make sure nothing was using /gnu/store and then `rm -rf
> /gnu/* /var/guix` and re-install guix. All of the nodes which were
> exhibiting this behavior stopped doing so after a re-install.
>
> My only theory is that there is something I am doing when managing the
> guix binary install that will occasionally result in the systems getting
> into this state. Perhaps something to do with the TLS libs.
I missed this email earlier, but FYI your issue sounds similar to
https://issues.guix.gnu.org/71238. A root cause hasn't been identified
there either.
--
Take it easy,
Richard Sent
Making my computer weirder one commit at a time.
prev parent reply other threads:[~2024-09-04 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 13:54 guix pull/guix upgrade often fails over VPN with TLS error message Thom R Harmon
2024-08-15 21:20 ` Thom R Harmon
2024-08-17 2:01 ` Thom R Harmon
2024-08-17 2:05 ` Thom R Harmon
2024-08-17 18:14 ` Thom R Harmon via
2024-08-22 23:46 ` Thom R Harmon
2024-09-04 18:41 ` Richard Sent [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=8734mfi7mp.fsf@freakingpenguin.com \
--to=richard@freakingpenguin.com \
--cc=help-guix@gnu.org \
--cc=trharmon@proton.me \
/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.
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).