Tongliang Liao wrote:
> I also saw people asking online regarding the status page with
> responses like "there's no status page for this site". Would be
> great if theisURL can be documented somewhere more visible,
Yes. I know that most of the IRC channels have it in the /topic
banner for public dissemination. Savannah mentions it at various
times in the web UI news area when there are events. It's otherwise
buried down this one page only.
https://savannah.gnu.org/maintenance/NotSavannahAdmins/
I'll try to make it documented more visibily. I think I will
advertise it on the front page of the servers such as here.
https://git.savannah.gnu.org/
Note that the Savannah Hackers admin team can do many things with the
Savannah system but that we don't have access to update notifications
to that FSF sysadmin managed hostux.social account.
> or perhaps 302 something like https://status.savannah.gnu.org
> <https://status.savannah.gnu.org/> here.
The problem is that if there is a larger problem at the Boston
datacenter where everything is hosted then it's a larger problem and
nothing from that datacenter works at all. That's been a problem a
few times in the past. When a problem like that happens that, for
example, breaks all networking to the entire set of machines, then
nothing there can work to communicate the failure.
That's why they (the FSF sysadmin staff) are using the hostux.social
media account as it is hosted elsewhere on a completely independent
network. The likelihood that both sites would be offline at the same
time is very small that way.
For just the one Savannah web UI system if there is going to be an
extended downtime then I will usually put up a maintenance page there.
But that's only possible when one is dealing with just that one thing
of the web server there which does not happen very often.
Bob
