From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#36754: SSH connections to hydra-slave{1, 2, 3} fail during builds Date: Wed, 24 Jul 2019 07:09:38 -0400 Message-ID: <87ef2fpu2a.fsf@netris.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> <87lfwo1lz0.fsf@gnu.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]:50634) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hqFCh-0002d8-HL for bug-guix@gnu.org; Wed, 24 Jul 2019 07:13:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hqFCg-0002DY-Ct for bug-guix@gnu.org; Wed, 24 Jul 2019 07:13:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:55430) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hqFCg-0002D3-8v for bug-guix@gnu.org; Wed, 24 Jul 2019 07:13:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hqFCg-0008E5-3l for bug-guix@gnu.org; Wed, 24 Jul 2019 07:13:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87lfwo1lz0.fsf@gnu.org> 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: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 36754@debbugs.gnu.org Hi Ludovic, Ludovic Court=C3=A8s wrote: > 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 = network. It=E2=80=99s hard to > tell exactly what, though. > > Ideas? Okay, I'll look into it. I'm very busy with something else for the next couple of days, but I'll try to get to it in the next week. > If it=E2=80=99s causing build failures, I=E2=80=99m afraid we=E2=80=99ll = have to comment out > those machines from berlin=E2=80=99s machines.scm until we=E2=80=99ve fig= ured it out. Agreed. Thanks, Mark