savannah down; quitter.im/fsfstatus also down

[Paul Eggert]

Currently I can't visit https://savannah.gnu.org (209.51.188.79), and the FSF 
status web page  is also down. Savannah is not 
responding, and Firefox rejects the quitter.im URL, saying:


An error occurred during a connection to quitter.im. SSL received a record that 
exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG


The page you are trying to view cannot be shown because the authenticity of 
the received data could not be verified.

Please contact the website owners to inform them of this problem.

Re: savannah down; quitter.im/fsfstatus also down

[Bob Proulx]

Hi Paul,

Paul Eggert wrote:
> Currently I can't visit https://savannah.gnu.org (209.51.188.79), and the
> FSF status web page  is also down. Savannah is
> not responding, and Firefox rejects the quitter.im URL, saying:

Please reference the updated URL:

  https://hostux.social/@fsfstatus

  We are experiencing a hardware failure in one of our servers, and we
  are working to repair it. The repairs will cause some downtime on
  debbugs.gnu.org h-node.org shop.fsf.org and savannah.gnu.org

Ian is at the datacenter working the problem since early this morning.
It seems there was a disk failure, and then a second disk failure
while trying to add a new disk in to address the first failure.  I
presume from some other hints that I have seen.

It would be nice to somehow intercept traffic for the down systems and
put up some type of notice.  Except I can't think of a way to do that.

All I can suggest is to stay tuned.

Bob

[sr #110128] Savannah bug submission markup does not properly handle URL with "http://" in non-protocol part

[Ineiev]

Update of sr #110128 (project administration):

  Status:None => Done   
 Assigned to:None => ineiev 
 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

Thank you, fixed.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/