mainSavannah Administration - Support: sr #110155, Can not "git fetch...

 
 

sr #110155: Can not "git fetch upstream" public repos

Submitter:  Burak <buraksarac>
Submitted:  Fri 06 Dec 2019 09:45:51 AM UTC
   
 
Category:  Download area - anonymous access Priority:  5 - Normal
Severity:  3 - Normal Status:  Done
Privacy:  Public Assigned to:  rwp
Operating System:  GNU/Linux Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Sat 07 Dec 2019 08:57:17 PM UTC, comment #4: 


> Hello Bob,
>  Its definitely fine! Works like a charm now, I would say even faster than before:)
> Thank you for quick response
> Burak


Thank you for the feedback!  The kind words are always appreciated. :-)

https should be okay to use.  It is only when we are suffering from a network abuse attack that it suffers by being overloaded.  But it is https with a Certificate Authority to verify the validity of the connection.

I'll go ahead and close this ticket. The problem with the git shared library problem (it was libpcre of the wrong version) has been resolved by reverting to the previous version.  And the root cause has been found to be the method I was using worked for the old version but did not work for the new version.  I will think of something different to do instead.

Thanks for the Report!

Bob Proulx <rwp>
Site Administrator
Fri 06 Dec 2019 07:15:38 PM UTC, comment #3: 

Gack!  Thank you for the report!

Hopefully working now.  Please retry.

This was due to me upgrading git on the server last night and failing to notice a shared library failure.  This was causing git clones using https to fail.

Failure to notice is because with the DDoS the regression suite, which also stresses the system, pretty much always fails due to being loaded along with the ongoing network abuse.  So it was just me monkey testing after installing the git upgrade.  I ran several commands and everything appeared to work.  But I didn't clone.  So not really related to the DDoS and yet still related because it was triggering me to do this type of maintenance.

I have reverted to the previous git version in order to restore things to a working state.  I tested git clone and was able to clone a project.  Reverting is the quickest way to get things going again.  I'll debug the shared library problem and redo the upgrade.  And test that one better.

Very sorry for the breakage.

Bob Proulx <rwp>
Site Administrator
Fri 06 Dec 2019 02:21:18 PM UTC, comment #2: 

Burak,

It's not you.  As Simon hints, the FSF's been the target of a large-footprint DDoS attack for the past week.

Sometimes one can get lucky and anonymous git over HTTPS will succeed, but the only reliable work-around is to pull over SSH as mentioned at the link.

Kind regards,

T G-R

Tobias Geerinckx-Rice <nckx>
Fri 06 Dec 2019 02:04:00 PM UTC, comment #1: 

Dear,

I have the same issue about Guix repos.
First error 502 then 443 connection refused.

Is it related to the DDoS attack?


All the best,
simon

Simon Tournier <zimoun>
Fri 06 Dec 2019 09:45:51 AM UTC, original submission:  

Hello,
 To build a LFS distro I have fetched all sources yesterday, today I was writing an update script and I notice I can not fetch sources anymore. Is it possible I am firewall banned because of excessive anonymous usage? Is there any way to restore it?

Thank you

i.e.
git clone https://git.savannah.gnu.org/git/grep.git
Cloning into 'grep'...
fatal: unable to access 'https://git.savannah.gnu.org/git/grep.git/': Failed to connect to git.savannah.gnu.org port 443: Connection refused

Burak <buraksarac>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rwp (Posted a comment)
  • -email is unavailable- added by nckx (Posted a comment)
  • -email is unavailable- added by zimoun (Posted a comment)
  • -email is unavailable- added by buraksarac (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2019-12-07 rwp StatusIn Progress Done
        Open/ClosedOpen Closed
    2019-12-06 rwp StatusNone In Progress
        Assigned toNone rwp

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code