unofficial mirror of 
 help / color / mirror / code / Atom feed
From: Bengt Richter <>
To: Tobias Geerinckx-Rice <>
Cc:, Lars-Dominik Braun <>,
	Maxime Devos <>,
	Roel Janssen <>
Subject: Re: python-pytest in references graph
Date: Mon, 25 Jul 2022 19:32:42 +0200	[thread overview]
Message-ID: <20220725173242.GA5336@LionPure> (raw)
In-Reply-To: <>

Hi Tobias,

On +2022-07-25 14:41:15 +0000, Tobias Geerinckx-Rice wrote:
> Hi Bengt,
> Berlin is currently in a degraded state (probably a Shepherd bug).  The main Web site works, although it's probably not being updated, and last I checked substitutes did to, but issues. is down and I don't think Cuirass is building new substitutes.
> We can't remotely reset the machine, so we wait until somebody can.
> Kind regards,
> T G-R
> Sent on the go.  Excuse or enjoy my brevity.

From tracepath, it seems to stop at some "RIPE" server[1]:
--8<---------------cut here---------------start------------->8---
[18:02 ~/bs]$ wl-paste 
11:                           102.352ms asymm 10 
12:                             110.156ms asymm 10 
13:                                        93.580ms asymm 17 
14:  no reply
--8<---------------cut here---------------end--------------->8---

[1] whois >> whois.
and copying some lines from the less view:

--8<---------------cut here---------------start------------->8---
less whois.
[18:05 ~/bs]$ wl-paste 
% This is the RIPE Database query service.
% The objects are in RPSL format.
% The RIPE Database is subject to Terms and Conditions.
% See

% Note: this output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to ' -'
--8<---------------cut here---------------end--------------->8---

I guess their server would be the one that couldn't get anything from
where my wget failed:
--8<---------------cut here---------------start------------->8---
Connecting to (||:443... connected.
HTTP request sent, awaiting response... 502 Bad Gateway
2022-07-25 15:05:57 ERROR 502: Bad Gateway.
--8<---------------cut here---------------end--------------->8---

How hard would it be to set up some kind of fail-over at
(which presumably resolves ok internally) to say, e.g.

--8<---------------cut here---------------start------------->8---
    We know (
    has been down since YYYY-MM-DD hh:mm:ss, sorry.
    Admin notified YYYY-MM-DD hh:mm:ss who replied:
    Fix ETA: ...
--8<---------------cut here---------------end--------------->8---
I.e., IWBN to get something informative from gnu rather than some net
error code :)

Is there an easy way to determine on the serving server how it is
responding to requests from the internet and switch/restore if down/up?

Or would you have to resort to some kind of periodic selfie-probe via
SSH/VPN to a cooperating mirror server?
(amateur idea :)

BTW, a good solution for informatiive status in place of error codes
might be applicable to other server stoppages and problems too, n'est-ce pas?

Bengt Richter

      reply	other threads:[~2022-07-25 17:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-24 20:25 Roel Janssen
2022-07-24 21:01 ` Maxime Devos
2022-07-25  5:59   ` Roel Janssen
2022-07-25  6:23   ` Lars-Dominik Braun
2022-07-25 13:12     ` bokr
2022-07-25 14:41       ` Tobias Geerinckx-Rice
2022-07-25 17:32         ` Bengt Richter [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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220725173242.GA5336@LionPure \ \ \ \ \ \ \

* 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

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).