From: "Ludovic Courtès" <ludo@gnu.org>
To: Marius Bakke <marius@gnu.org>
Cc: 58290@debbugs.gnu.org, Andrew Tropin <andrew@trop.in>
Subject: bug#58290: guile ssh error on guix deploy
Date: Tue, 18 Oct 2022 17:31:42 +0200 [thread overview]
Message-ID: <87y1tdkv1d.fsf@gnu.org> (raw)
In-Reply-To: <87h702uzrb.fsf@gnu.org> (Marius Bakke's message of "Mon, 17 Oct 2022 19:27:20 +0200")
Hi,
Marius Bakke <marius@gnu.org> skribis:
> 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'.
“no more sessions” comes from this:
--8<---------------cut here---------------start------------->8---
int
session_open(Authctxt *authctxt, int chanid)
{
Session *s = session_new();
debug("session_open: channel %d", chanid);
if (s == NULL) {
error("no more sessions");
return 0;
}
[...]
}
--8<---------------cut here---------------end--------------->8---
Would be interesting to run sshd in verbose/debug mode and see why we
hit that; it could be because the maximum number of sessions has been
reached or something.
> 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.
Ouch. Normally, thanks to memoization, ‘guix deploy’ opens only one
session per machine. (I think it works well with the 25 local build
machines behind berlin; it’s also fine for a small set of machines I
take care of at work.)
> 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)
Interesting. That gives us a hint. Could you add a ‘pk’ in
‘open-machine-ssh-session*’ to see how many connections it opens?
Thanks for your feedback!
Ludo’.
next prev parent reply other threads:[~2022-10-18 15:33 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
2022-10-18 15:31 ` Ludovic Courtès [this message]
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
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=87y1tdkv1d.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=58290@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=marius@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).