From: "Thompson, David" <dthompson2@worcester.edu>
To: 56709@debbugs.gnu.org
Subject: bug#56709: Channel opening failure with guix deploy
Date: Wed, 18 Jan 2023 15:49:20 -0500 [thread overview]
Message-ID: <CAJ=RwfZa2zYNNAqo3GSg=pqkAVieap7oF1yfhidWVgTaq1cTbQ@mail.gmail.com> (raw)
In-Reply-To: <87fsituexa.fsf@posteo.org>
Hello,
This problem is strangely transient. I've seen it happen to others
when it wasn't happening to me with the same remote machine. Now I am
having this problem again on 2 different servers that I manage. I dug
around a bit and found that calls to 'open-remote-pipe*' from
guile-ssh have some chance of failure even though the SSH session is
fine. This procedure is called many times during a deploy, so the odds
are high that one of them will fail. I got lucky once today and had a
deploy finish but that was after many failures. I was able to unblock
myself by hacking call sites to repeatedly call 'open-remote-pipe*' in
a loop, like this:
(let loop ()
(or (false-if-exception
(apply open-remote-pipe* session OPEN_BOTH repl-command))
(loop)))
I also added some 'pk' logging and found that 'open-remote-pipe*'
would typically succeed on the first or second try. I think there
could be a bit more investigation done to better understand *why* this
happens in the first place, but as a resiliency tactic I think it
would be appropriate to write a wrapper procedure that retries a few
times before giving up.
Thoughts?
- Dave
prev parent reply other threads:[~2023-01-18 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 19:26 bug#56709: Channel opening failure with guix deploy Aleksandr Vityazev
2022-12-22 1:31 ` bug#56709: (No Subject) Attila Lendvai
2022-12-23 0:41 ` Attila Lendvai
2023-01-15 19:39 ` Attila Lendvai
2023-01-18 20:49 ` Thompson, David [this message]
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='CAJ=RwfZa2zYNNAqo3GSg=pqkAVieap7oF1yfhidWVgTaq1cTbQ@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=56709@debbugs.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).