From: ludo@gnu.org (Ludovic Courtès)
To: guix-devel@gnu.org
Subject: Re: hydra.gnu.org down
Date: Sat, 16 Jul 2016 15:08:40 +0200 [thread overview]
Message-ID: <87fur9afxj.fsf@gnu.org> (raw)
In-Reply-To: <87k2gpi3yu.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 14 Jul 2016 00:10:49 +0200")
Hello,
ludo@gnu.org (Ludovic Courtès) skribis:
> ludo@gnu.org (Ludovic Courtès) skribis:
>
>> Since yesterday evening (CET), hydra.gnu.org is down. The FSF sysadmins
>> are working on it and will keep us updated.
>
> The bad news is that there was a hard disk failure so the FSF staff will
> need to restore a backup of the machine, which will take some time. :-/
The FSF folks restored a backup of the machine but the store is empty
(it was purposefully not backed up.) We’ve started to populate it, and
we should be able restart Hydra, hopefully later today. I’ve restarted
nginx already, and its cache is not empty, so that might help a little
already.
We’ll have to rebuild a large subset of master and core-updates (a
“large subset” because the build machines still have some of the
binaries, which will just need to be transferred back to hydra.gnu.org
via the offload mechanism.)
The SourceForge issue may make things more difficult because downloads
are normally not offloaded so hydra.gnu.org will just stop if it fails
to download the source of some package.
Ludo’.
next prev parent reply other threads:[~2016-07-16 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 13:44 hydra.gnu.org down Ludovic Courtès
2016-07-13 22:10 ` Ludovic Courtès
2016-07-14 4:58 ` Chris Marusich
2016-07-14 15:27 ` Leo Famulari
2016-07-15 1:45 ` Chris Marusich
2016-07-16 13:08 ` Ludovic Courtès [this message]
2016-07-17 13:18 ` Ludovic Courtès
2016-07-18 12:13 ` Ludovic Courtès
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=87fur9afxj.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@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).