GNU bug report logs - #48903
guix substitute: error: TLS error in procedure 'read_from_session_record_port': Error decoding the received TLS packet.

Previous Next

Package: guix;

Reported by: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Date: Mon, 7 Jun 2021 15:18:02 UTC

Severity: important

Merged with 49071

Done: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#49071: closed (error: TLS-fout in procedure ‘read_from_session_record_port’:
 Error decoding the received TLS packet.)
Date: Sat, 07 Aug 2021 04:24:02 +0000
[Message part 1 (text/plain, inline)]
Your message dated Sat, 07 Aug 2021 00:23:07 -0400
with message-id <87czqpkhn8.fsf <at> gmail.com>
and subject line Re: bug#48903: guix substitute: error: TLS error in procedure 'read_from_session_record_port': Error decoding the received TLS packet.
has caused the debbugs.gnu.org bug report #48903,
regarding error: TLS-fout in procedure ‘read_from_session_record_port’: Error decoding the received TLS packet.
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
48903: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=48903
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Maxime Devos <maximedevos <at> telenet.be>
To: bug-guix <at> gnu.org
Subject: error: TLS-fout in procedure
 ‘read_from_session_record_port’:
 Error decoding the received TLS packet.
Date: Thu, 17 Jun 2021 14:59:29 +0200
[Message part 3 (text/plain, inline)]
tags: + substituter

(^ not sure if that works, 'substituter' isn't a standard tag)

During a "guix system -L. reconfigure [...].scm":

[...]
substitute: lijst van substitutes van ‘[...]’ aan het bijwerken...   0.0%
guix substitute: warning: [...]: host not found: Naam of dienst is niet bekend
 guix-1.3.0-3.50dfbbf  35.9MiB         60KiB/s 09:03 [################  ]  89.4%guix substitute: error: TLS-fout in procedure ‘read_from_session_record_port’: Error decoding the received TLS packet.
vervanging van /gnu/store/3j9kzhsygg56pmhlwpvjqicvjgsni49w-guix-1.3.0-3.50dfbbf mislukt
guix system: error: beschadigde invoer tijdens het terugplaatsen van het archief uit #<closed: file 7f875a3ac4d0>

Version of the daemon:

$ ls -l /run/current-system/profile/bin/guix-daemon 
lrwxrwxrwx 2 root root 80  1 jan  1970 /run/current-system/profile/bin/guix-daemon -> /gnu/store/pv9i296wfjl3zwkmsg4w24ksqcb9qhnb-guix-1.3.0-2.9f2b2c4/bin/guix-daemon

I'll try to work-around with --no-substitutes.
[signature.asc (application/pgp-signature, inline)]
[Message part 5 (message/rfc822, inline)]
From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 48903-done <at> debbugs.gnu.org, Maxime Devos <maximedevos <at> telenet.be>
Subject: Re: bug#48903: guix substitute: error: TLS error in procedure
 'read_from_session_record_port': Error decoding the received TLS packet.
Date: Sat, 07 Aug 2021 00:23:07 -0400
Hello,

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

> Hi,
>
> Maxim Cournoyer <maxim.cournoyer <at> gmail.com> skribis:
>
>> I've tried some to reproduce the issue with the modified scripts below,
>> but in vain.  I'm not sure if my delay is inserted at the right place.
>> I also suspect that my attempt to shuffle the substitute-urls is not
>> really useful, as that's probably what would have happened anyway
>> (although I haven't followed in the code deeply enough to confirm).
>
> Bah.  :-/  Do the two of you still experience the bug initially reported
> here in “real” conditions?
>
> Are we sure we’re using the same Guix + Guile when running the stress
> test and in real conditions?
>
> Thanks for testing!
>
> Ludo’.

I've been doing builds on core-updates, which would previously trigger
this problem rather often, *without* suffering from the problem.

I consider it resolved.  I'm not exactly sure how, which is not
satisfying, but I'm glad it's gone.

Thank you!

Closing.

Maxim


This bug report was last modified 3 years and 190 days ago.

Previous Next


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