unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Wojtek Kosior <koszko@koszko.org>
Cc: help-guix@gnu.org
Subject: Re: ci.guix.gnu.org unreachable
Date: Fri, 18 Nov 2022 21:28:41 +0100	[thread overview]
Message-ID: <87iljcats9.fsf@nckx> (raw)
In-Reply-To: <20221118194951.1e44fc4b@koszkonutek-tmp.pl.eu.org>

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

Hi Wojtek,

Wojtek Kosior via 写道:
> Today various Guix commands started showing me
>
>     substitute: guix substitute: warning: ci.guix.gnu.org: 
>     connection failed: No route to host
>
> Indeed ci.guix.gnu.org's IP, 141.80.181.40, is not 
> accessible. Also
> when trying to connect through Tor.
>
> Anybody knows what might be wrong?

Berlin, the server hosting guix.gnu.org, issues.guix.gnu.org, and 
ci.guix.gnu.org, was down for planned maintenance (not by us).

Some nice steps were taken today to keep guix.gnu.org up despite 
the downtime, for the first time ever.

Next time we can add a status update to the home page. 
Eventually, maybe even add some kind of server status report 
facility to the ‘guix command’:

  substitute: guix substitute: ci.guix.gnu.org reports: Down for 
  scheduled maintenance.

Or maybe not.

Anyway, this maintenance window has successfully been closed, and 
ci.guix is serving tasty toots once again.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

      parent reply	other threads:[~2022-11-18 20:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 18:49 ci.guix.gnu.org unreachable Wojtek Kosior via
2022-11-18 18:52 ` (
2022-11-18 19:04   ` Wojtek Kosior via
2022-11-18 20:28 ` Tobias Geerinckx-Rice [this message]

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=87iljcats9.fsf@nckx \
    --to=me@tobias.gr \
    --cc=help-guix@gnu.org \
    --cc=koszko@koszko.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.
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).