[savannah-help-public] git.sv.gnu.org flaky; pumprock.net connection refused

[Paul Eggert]

git.sv.gnu.org was flaky a few minutes ago. Sometimes it would work, and
sometimes not; see transcript below.

When I visit https://pumprock.net/fsfstatus for the out-of-band status report
for Savannah status, I get "Connection refused". Has that the fsfstatus URL
changed? It's still listed at
https://savannah.gnu.org/maintenance/NotSavannahAdmins/ and other places.

--- start of transcript ---

1041-Penguin $ git pull
ssh_exchange_identification: Connection closed by remote host
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
...
1044-Penguin $ git pull -v
From git.sv.gnu.org:/srv/git/gnulib
= [up to date] master -> origin/master
= [up to date] EMACS_21_1_RC -> origin/EMACS_21_1_RC
= [up to date] FILEUTILS -> origin/FILEUTILS
= [up to date] SHELLUTILS -> origin/SHELLUTILS
= [up to date] TEXTUTILS -> origin/TEXTUTILS
= [up to date] akim-fix-upload -> origin/akim-fix-upload
= [up to date] akim/relpath -> origin/akim/relpath
= [up to date] coreutils-8.9 -> origin/coreutils-8.9
= [up to date] diff-merge -> origin/diff-merge
= [up to date] emacs-unicode -> origin/emacs-unicode
= [up to date] emacs-unicode-2 -> origin/emacs-unicode-2
= [up to date] haible-private -> origin/haible-private
= [up to date] karl -> origin/karl
= [up to date] lexbind -> origin/lexbind
= [up to date] origin -> origin/origin
= [up to date] pygnulib -> origin/pygnulib
= [up to date] python -> origin/python
= [up to date] topic/libposix -> origin/topic/libposix
= [up to date] ueno/unicode-9.0.0 -> origin/ueno/unicode-9.0.0
Already up to date.
1045-Penguin $ git pull
ssh_exchange_identification: Connection closed by remote host
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
1046-Penguin $ git pull
Already up to date.

[Bob Proulx]

Hi Paul,

Post by Paul Eggert
git.sv.gnu.org was flaky a few minutes ago. Sometimes it would work, and
sometimes not; see transcript below.

I can only say that the git host system seems to be operating
normally. I haven't seen any trouble from it today. So perhaps it
was the backbone network between. Don't know.

If the problem persists please make another report. I was able to
clone gnulib a moment ago from Boston to Colorado. Hopefully it was
just a temporary problem.

Post by Paul Eggert
When I visit https://pumprock.net/fsfstatus for the out-of-band status
report for Savannah status, I get "Connection refused". Has that the
fsfstatus URL changed? It's still listed at
https://savannah.gnu.org/maintenance/NotSavannahAdmins/ and other places.

For some time pumprock.net has been offline for reasons I don't know
but are outside of anyone's control. Therefore the 3rd party status
had moved to https://quitter.se/fsfstatus December 2016. I just
updated the wiki page with that information. However the web copy
hasn't updated yet. If it doesn't update Monday I will investigate
why. Thank you for bringing it to our attention. I hadn't realized
it was in the documentation there.

However https://quitter.se/fsfstatus isn't responding to me at this
time. I don't know anything about the status of it but will ask the
FSF admins on Monday. If it isn't one thing it is another. :-(

Bob

[Ineiev]

Post by Bob Proulx
I just
updated the wiki page with that information. However the web copy
hasn't updated yet. If it doesn't update Monday I will investigate
why.

Last time I had to run the script on frontend manually; IIRC it didn't
let connect via ssh from vcs.

[Bob Proulx]

Post by Ineiev

I just updated the wiki page with that information. However the
web copy hasn't updated yet. If it doesn't update Monday I will
investigate why.

Last time I had to run the script on frontend manually; IIRC it didn't
let connect via ssh from vcs.

I figured it out. The hook script was using an https URL to frontend0
which I obsoleted some time ago. Changing that to the production
https URL of https://savannah.gnu.org avoids the certificate problem.

Additionally there were two hook scripts that both tried to update the
wiki. That was a little confusing since the other one was unable to
function for multiple reasons. I explicitly disabled that one and
left a comment. It might still be useful at another time.

The wiki updates should be working automatically again now. I
committed an update just now and it worked.

Bob

[Bob Proulx]

Post by Bob Proulx
However https://quitter.se/fsfstatus isn't responding to me at this
time. I don't know anything about the status of it but will ask the
FSF admins on Monday. If it isn't one thing it is another. :-(

Ian said he had noticed that quitter.se had been persistently offline
and said he opened a ticket in their system to move to (yet another)
3rd party system for status notification.

There is some irony in that the out-of-band 3rd party outage
notification location has needed to move twice now due to they being
persistently offline.

Bob