unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bengt Richter <bokr@bokr.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org, Lars-Dominik Braun <lars@6xq.net>,
	Maxime Devos <maximedevos@telenet.be>,
	Roel Janssen <roel@gnu.org>
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: <2F64B5BA-D271-42FE-A9F9-1D4B3789635B@tobias.gr>

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


      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 python-pytest in references graph 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:
  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=20220725173242.GA5336@LionPure \
    --to=bokr@bokr.com \
    --cc=guix-devel@gnu.org \
    --cc=lars@6xq.net \
    --cc=maximedevos@telenet.be \
    --cc=me@tobias.gr \
    --cc=roel@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).