From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#36754: SSH connections to hydra-slave{1, 2, 3} fail during builds Date: Tue, 23 Jul 2019 23:26:27 +0200 Message-ID: <87lfwo1lz0.fsf@gnu.org> References: <87o91n3ps0.fsf@netris.org> <87o91n3ps0.fsf@netris.org> <87zhl656xk.fsf@netris.org> <87pnm04s21.fsf@devup.no> <87ef2gr6z3.fsf@netris.org> <878ssor680.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:59069) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hq2JL-0007XP-MA for bug-guix@gnu.org; Tue, 23 Jul 2019 17:27:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hq2JK-0003tT-MR for bug-guix@gnu.org; Tue, 23 Jul 2019 17:27:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:55121) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hq2JK-0003tD-IL for bug-guix@gnu.org; Tue, 23 Jul 2019 17:27:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hq2JK-000857-CO for bug-guix@gnu.org; Tue, 23 Jul 2019 17:27:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <878ssor680.fsf@netris.org> (Mark H. Weaver's message of "Tue, 23 Jul 2019 13:49:24 -0400") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Mark H Weaver Cc: 36754@debbugs.gnu.org Hi Mark, Mark H Weaver skribis: > I wrote earlier: >> I now believe that these failures are related to the newly added armhf >> build slaves, and that they have nothing to do with the recent changes >> to our linux-libre packages. > > I should mention that the armhf build slaves are on a private network, > and I use my public-facing internet server to forward TCP connections to > them, using the following entries in /etc/inetd.conf: > > # TCP-level forwards for SSH connections to build machines for the GNU > # Guix build farm: > 7275 stream tcp nowait nobody /bin/nc /bin/nc -w 10 172.19.189.= 11 7275 > 7276 stream tcp nowait nobody /bin/nc /bin/nc -w 10 172.19.189.= 12 7276 > 7274 stream tcp nowait nobody /bin/nc /bin/nc -w 10 172.19.189.= 13 7274 > > It's possible that this arrangement is somehow part of the problem. > However, note that nothing has changed here in several years, and it > worked fine on hydra.gnu.org. The build slaves were running a *very* > old version of Guix though. It seems likely that the new Guile-SSH code > doesn't cope well with this setup. I noticed that connections to the machines were unstable (using OpenSSH=E2=80=99s client). That is, the connection would eventually =E2=80= =9Chang=E2=80=9D, apparently several times a day. Currently we have an SSH tunnel set up on berlin to connect to each of these machines via overdrive1.guixsd.org. This setup proved to be robust in the past (we used it to connect to another build machine), so I suspect something=E2=80=99s wrong on =E2=80=9Cyour=E2=80=9D end of the ne= twork. It=E2=80=99s hard to tell exactly what, though. Ideas? If it=E2=80=99s causing build failures, I=E2=80=99m afraid we=E2=80=99ll ha= ve to comment out those machines from berlin=E2=80=99s machines.scm until we=E2=80=99ve figur= ed it out. Thanks, Ludo=E2=80=99.