From: Marius Bakke <marius@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>, "Andrew Tropin" <andrew@trop.in>
Cc: 58290@debbugs.gnu.org
Subject: bug#58290: guile ssh error on guix deploy
Date: Mon, 17 Oct 2022 19:27:20 +0200 [thread overview]
Message-ID: <87h702uzrb.fsf@gnu.org> (raw)
In-Reply-To: <8735bmsee9.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1824 bytes --]
Ludovic Courtès <ludo@gnu.org> skriver:
> Hi,
>
> Andrew Tropin <andrew@trop.in> skribis:
>
>>>> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
>>>> Throw to key `guile-ssh-error' with args `("channel-open-session" "Channel opening failure: channel 67 error (2) open failed" #<input-output: channel (closed) 7f7d1af9e140> #f)'.
>>>
>>> Are there any hints from sshd in the /var/log/messages of that machine
>>> as to why the connection was closed?
>>
>> bob@pinky /var/log$ zcat messages.1.gz | grep "Oct 4" | grep ssh
>
> It’s hard (if not impossible) to see which lines correspond to the error
> above. :-)
>
> Could try to reproduce the bug, and have ‘tail -f /var/log/messages’
> running on the server side so you can capture just the right lines?
> /var/log/debug might be interesting too.
I have the same problem. Log messages around failure look something
like this (extracted from above message):
Oct 4 11:51:49 localhost shepherd[1]: Service sshd-2 has been started.
Oct 4 11:51:50 localhost sshd[250]: Accepted publickey for bob from 185.70.53.164 port 1915 ssh2: RSA SHA256:/X3jyhyMizAOKOjCfXK5cLN3Pa0vmi7dbQG+fxK3d3Y
Oct 4 11:52:28 localhost sshd[252]: error: no more sessions
Oct 4 11:52:28 localhost shepherd[1]: 1 connection still in use after sshd-2 termination.
Oct 4 11:52:28 localhost shepherd[1]: Service sshd-2 has been disabled.
Then deploy crashes with 'Channel opening failure'.
Due to the number of SSH connections made by deploy and frequent
occurence of this problem, I was not able to successfully deploy through
many attempts.
I found that removing the memoizing open-machine-ssh-session* in
(gnu machine ssh) works around it and can happily deploy again.
(that is, just use 'open-machine-ssh-session' instead)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-10-17 17:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 11:09 bug#58290: guile ssh error on guix deploy Andrew Tropin
2022-10-08 12:39 ` Ludovic Courtès
2022-10-14 6:45 ` Andrew Tropin
2022-10-17 14:39 ` Ludovic Courtès
2022-10-17 17:27 ` Marius Bakke [this message]
2022-10-18 15:31 ` Ludovic Courtès
2022-11-03 23:47 ` Marius Bakke
2022-11-10 10:06 ` Andrew Tropin
2023-01-12 12:11 ` Ludovic Courtès
2023-01-12 12:44 ` Ludovic Courtès
2023-01-22 20:00 ` Artyom V. Poptsov
2023-01-23 20:14 ` Artyom V. Poptsov
2023-01-23 21:50 ` Ludovic Courtès
2023-01-24 15:53 ` Andrew Tropin
2023-01-30 22:53 ` Ludovic Courtès
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=87h702uzrb.fsf@gnu.org \
--to=marius@gnu.org \
--cc=58290@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=ludo@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.