Re: python-pytest in references graph

[Bengt Richter <bokr@bokr.com>]

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:  cr-tub2-be10.x-win.dfn.de                           102.352ms asymm 10 
12:  kr-mdcbln1.x-win.dfn.de                             110.156ms asymm 10 
13:  141.80.238.11                                        93.580ms asymm 17 
14:  no reply
--8<---------------cut here---------------end--------------->8---

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

--8<---------------cut here---------------start------------->8---
less whois.141.80.238.11.txt
[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 http://www.ripe.net/db/support/db-terms-conditions.pdf

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

% Information related to '141.80.0.0 - 141.80.255.255'
--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 issues.guix.gnu.org (issues.guix.gnu.org)|141.80.181.40|: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 issues.guix.gnu.org
(which presumably resolves ok internally) to say, e.g.

--8<---------------cut here---------------start------------->8---
    We know issues.guix.gnu.org (141.80.181.40)
    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?

--
Regards,
Bengt Richter