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

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#48903: closed (guix substitute: error: TLS error 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 guix substitute: error: TLS error 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: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: bug-guix <bug-guix <at> gnu.org>
Subject: guix substitute: error: TLS error in procedure
 'read_from_session_record_port': Error decoding the received TLS packet.
Date: Mon, 07 Jun 2021 11:10:06 -0400

[Message part 3 (text/plain, inline)]

Hello,

Using Guix from the master branch at commit
b2122b07dc24007263b92247cc479713c2101390, with a system reconfigured on
the 2nd of June (Guix commit bb325c5611553a6db21ee7499ac07d5757d24fc3):

--8<---------------cut here---------------start------------->8---
Generation 216  Jun 02 2021 10:14:19    (current)
  file name: /var/guix/profiles/system-216-link
  canonical file name: /gnu/store/apjg70083nc5xj816y0ff3r8ir9gh5py-system
  label: GNU with Linux-Libre 5.11.20
  bootloader: grub
  root device: /dev/mapper/cryptroot
  kernel: /gnu/store/ghijd80qabdyf0p6jcich9ggnpwrbwxw-linux-libre-5.11.20/bzImage
  channels:
    sfl-packages:
      repository URL: https://gitlab.com/Apteryks/sfl-guix-channel
      branch: master
      commit: 37d017573350b64f8a8c992530153f42806b6a6f
    guix:
      repository URL: https://git.savannah.gnu.org/git/guix.git
      branch: master
      commit: bb325c5611553a6db21ee7499ac07d5757d24fc3
  configuration file:
  /gnu/store/qvhl7ya2xn4gr9mn29hg93p1dcbdlyfy-configuration.scm
--8<---------------cut here---------------end--------------->8---
  
with the guix-daemon running being:

--8<---------------cut here---------------start------------->8---
/gnu/store/9zh3bg8d4y08jnkqyrk6xczahiahhcy4-guix-1.3.0-1.771b866/bin/guix-daemon
29920 guixbuild --max-silent-time 0 --timeout 0 --log-compression none
--discover=no --substitute-urls http://127.0.0.1:8080
https://ci.guix.gnu.org --max-jobs=4
--8<---------------cut here---------------end--------------->8---

Attempting to update my profile keeps failing with:

--8<---------------cut here---------------start------------->8---
$ ./pre-inst-env guix package -m ~/stow/guix/manifest.scm -L ~/src/sfl-guix-channel/ --substitute-urls=https://ci.guix.gnu.org --no-offload
;;; note: source file /home/maxim/src/guix-master/gnu/packages/networking.scm
;;;       newer than compiled /home/maxim/src/guix-master/gnu/packages/networking.go
;;; note: source file /home/maxim/src/guix-master/gnu/packages/networking.scm
;;;       newer than compiled /run/current-system/profile/lib/guile/3.0/site-ccache/gnu/packages/networking.go
The following packages will be installed:
   acpi                      1.7
   adb                       7.1.2_r36
   adwaita-icon-theme        3.34.3
   alsa-utils                1.2.4
   [...]
   xrandr                    1.5.1
   xrdb                      1.2.0
   xsetroot                  1.1.2
   yelp                      3.32.2

122.8 MB will be downloaded
 libreoffice-6.4.7.2  117.1MiB                                  344KiB/s 03:04 [#########         ]  52.7%guix substitute: error: TLS error in procedure 'read_from_session_record_port': Error decoding the received TLS packet.
substitution of /gnu/store/44h13hn5zssfppz67vydxcf95qsc8qfw-libreoffice-6.4.7.2 failed
guix package: error: some substitutes for the outputs of derivation `/gnu/store/9f8sffldy39mprihx6xgrs7hys9j75jm-libreoffice-6.4.7.2.drv' failed (usually happens due to networking issues); try `--fallback' to build derivation from source
--8<---------------cut here---------------end--------------->8---

I'm attaching my (large!) profile manifest.  It depends on the
https://gitlab.com/Apteryks/sfl-guix-channel channel, which just adds 3
Python packages.  You could comment out the "sflvault-client" package
from the manifest to lift that requirement.

Thanks,

Maxim

[manifest.scm (text/plain, attachment)]

[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

Previous Next

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