From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: mirror.hydra.gnu.org is back on-line
Date: Fri, 30 Nov 2018 22:48:37 +0100
Message-ID: <87d0qmtex6.fsf@gnu.org>
References: <87d0qozzp0.fsf@gnu.org> <87efb40zpp.fsf@gnu.org>
	<87zhtsq7mx.fsf@ambrevar.xyz>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51648)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1gSqeP-0006cN-Ul
	for guix-devel@gnu.org; Fri, 30 Nov 2018 16:48:42 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1gSqeN-0004Ly-O2
	for guix-devel@gnu.org; Fri, 30 Nov 2018 16:48:41 -0500
In-Reply-To: <87zhtsq7mx.fsf@ambrevar.xyz> (Pierre Neidhardt's message of
	"Thu, 29 Nov 2018 15:29:42 +0100")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org

Hi,

Pierre Neidhardt <mail@ambrevar.xyz> skribis:

> So what happened?

There was a short maintenance operation in the data center at TUM, the
university that hosts this machine.  They turned it off (without
contacting guix-sysadmin@gnu.org) and turned it back on soon after,
except that the machine didn=E2=80=99t come back for some obscure reason.

We reported the issue in the evening and one of the sysadmins at TUM
diagnosed and fixed the problem on the next morning.

Ludo=E2=80=99.