From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ricardo Wurmus <rekado@elephly.net>
Subject: bug#36754: SSH connections to hydra-slave{1, 2, 3} fail during builds
Date: Wed, 07 Aug 2019 16:30:54 +0200
Message-ID: <87d0hhxd29.fsf@elephly.net>
References: <87o91n3ps0.fsf@netris.org> <87zhl656xk.fsf@netris.org>
 <87pnm04s21.fsf@devup.no> <87ef2gr6z3.fsf@netris.org>
 <878ssor680.fsf@netris.org> <87lfwo1lz0.fsf@gnu.org>
 <87ef2fpu2a.fsf@netris.org> <87lfwnxyzg.fsf@gnu.org>
 <87k1bx2d1f.fsf@devup.no> <87pnlokfix.fsf@netris.org>
 <87sgqksiic.fsf@elephly.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:41117)
 by lists.gnu.org with esmtp (Exim 4.86_2)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hvMyy-0002jU-83
 for bug-guix@gnu.org; Wed, 07 Aug 2019 10:32:06 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hvMyx-0004n7-4n
 for bug-guix@gnu.org; Wed, 07 Aug 2019 10:32:04 -0400
Received: from debbugs.gnu.org ([209.51.188.43]:58598)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
 (Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
 id 1hvMyw-0004mv-MA
 for bug-guix@gnu.org; Wed, 07 Aug 2019 10:32:02 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hvMyw-0003We-Dn
 for bug-guix@gnu.org; Wed, 07 Aug 2019 10:32:02 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.36754.B36754.156518827013482@debbugs.gnu.org>
In-reply-to: <87sgqksiic.fsf@elephly.net>
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
 <mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-guix>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
 <mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 36754@debbugs.gnu.org


Ricardo Wurmus <rekado@elephly.net> writes:

> Mark H Weaver <mhw@netris.org> writes:
>
>>> Mark: are the armhf nodes still operational?
>>
>> I assume so.  They all respond to pings anyway, and I haven't touched
>> them since before they were disconnected from Berlin.  (I would need to
>> boot up my other, more secure computer to try SSHing into them).
>>
>>> I would like to re-enable them again, since we desperately need the
>>> computing power with four huge branches going concurrently at the
>>> moment.
>>
>> I have no objection, but since Ludovic made the decision to disconnect
>> them, it would be good to hear from him first.
>
> Now that we should be able to SSH to them directly from Berlin we can
> try connecting and perhaps upgrading the guix-daemon on these machines.

I have removed the SSH tunnel configuration from /etc/guix/machines.scm
and re-enabled the machines.

Let=E2=80=99s see if this makes any difference.  If not we should try to up=
grade
Guix on these build machines.

--
Ricardo