all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thom R Harmon <trharmon@proton.me>
To: help-guix@gnu.org
Subject: guix pull/guix upgrade often fails over VPN with TLS error message
Date: Wed, 14 Aug 2024 13:54:50 +0000	[thread overview]
Message-ID: <03c76f93-3118-4967-9baa-443e8ca0a9ab@proton.me> (raw)

tldr; guix substitute: error: TLS error in procedure 
'write_to_session_record_port': Error in the push function.

The full error message:

 > substitute: updating substitutes from 
'https://bordeaux.guix.gnu.org'...   0.0%guix substitute: error: TLS 
error in procedure 'write_to_session_record_port': Error in the push 
function.
guix upgrade: error: 
`/gnu/store/8wp75vw27zm2c8cfkpxqg73glslqvmgn-guix-command substitute' 
died unexpectedly

There's at least one thread about this message in the archives but it's 
from before I subscribed and I don't know how/if I can tag into that 
thread so I'll just start a new one.

I've been seeing the above error message on `guix pull` and `guix 
upgrade` off-and-on for about 2 years. It's not 100% correlated but 
seems to be more prevalent when I'm doing the guix operation over a VPN. 
It seems to come in bunches meaning I won't see the error for a few 
weeks and then it will persist for a couple of weeks to the point where 
I basically cannot do a pull/upgrade.

Anyone have any thoughts as to what might happening? Or, even better, 
ideas as to how I might troubleshoot? Previous attempts to capture it 
with wireshark/tshark have not been indicative of the root cause.

thx




             reply	other threads:[~2024-08-15 10:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14 13:54 Thom R Harmon [this message]
2024-08-15 21:20 ` guix pull/guix upgrade often fails over VPN with TLS error message 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

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=03c76f93-3118-4967-9baa-443e8ca0a9ab@proton.me \
    --to=trharmon@proton.me \
    --cc=help-guix@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.