FS#48597 - Git repos not working properly

Attached to Project: AUR web interface
Opened by Daniel Milde (dundee) - Tuesday, 15 March 2016, 17:40 GMT
Last edited by Lukas Fleischer (lfleischer) - Saturday, 02 April 2016, 06:56 GMT
Task Type Bug Report
Category Backend
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 4.2.0
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

I am getting error message when reading from AUR git repos since last few days:

Timeout, server aur.archlinux.org not responding.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Tried IPv6 and 4 addresses, same behaviour.
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Saturday, 02 April 2016, 06:56 GMT
Reason for closing:  Fixed
Comment by Dave Reisner (falconindy) - Tuesday, 15 March 2016, 17:57 GMT
Seems like a local problem, given that you say it's been a "few days" and there's been no shortage of updates to the AUR from other users.

What's the full command you're running? Are you behind a firewall? Can you ping the address?
Comment by Daniel Milde (dundee) - Tuesday, 15 March 2016, 18:32 GMT
It doesn't look like local problem. I experience this on multiple machines in different locations.

Mark Weiman also wrote on AUR-General:
I'm getting large delays too. I only noticed today, but I haven't really checked since last Thursday.

I have tried connecting from server placed in datacentre in Prague:

# time git fetch

real 0m20.741s
user 0m0.022s
sys 0m0.004s

It doesn't failed, but 20 secs for fetch of small repo with 5 commits is a lot.
Comment by Lukas Fleischer (lfleischer) - Tuesday, 15 March 2016, 19:01 GMT
For a couple of days, the configuration options used to omit "have" lines did not work due to a recent Git upgrade on luna. It should be fixed now, though. Can you still reproduce this behavior?
Comment by Daniel Milde (dundee) - Tuesday, 15 March 2016, 19:04 GMT
Yes, I'm still getting long delays or timeouts. Tried with git 2.7.3 and 1.7.10.4.
Comment by Gustavo Alvarez (sl1pkn07) - Tuesday, 15 March 2016, 19:08 GMT
for me, connect for git push is too slow
Comment by Daniel Milde (dundee) - Tuesday, 15 March 2016, 19:10 GMT
Long delays also on server in Munich (GlobalAccess datacentre) - 25.592s and in Hluboka nad Vltavou (Wedos datacentre) - 18.853s.
Comment by Lukas Fleischer (lfleischer) - Tuesday, 15 March 2016, 19:40 GMT
Could you please give some more details? Which repository does this happen with? Are you cloning via SSH or via HTTPs? Does it also happen with a fresh clone?
Comment by Mark Weiman (markzz) - Tuesday, 15 March 2016, 19:47 GMT
*Psst* Eli Schwartz said that line you said I said.

Regardless, it's not very quick to clone or push, but I'm not experiencing any time-outs. I've noticed that pushes have been slow for a while now, but clones have now joined in on the fun (within the last week). My main issue was in  FS#48593 , which appears to be fixed.
Comment by Eli Schwartz (eschwartz) - Tuesday, 15 March 2016, 21:35 GMT
The missing HEAD ref is now fixed, (thanks!), but fresh clones are still slow. And for that matter, so is fetch/ls-remote/etc
And come to think of it, I too have noticed pushing is rather slow for a while. (It isn't as noticeable, when you are splitting a subtree first, every time.)
The fetch/clone is new, I think.

All over SSH -- because I have an SSH alias for "aur", so it saves so much typing that way, whyever not...
Comment by Daniel Milde (dundee) - Wednesday, 16 March 2016, 08:47 GMT
Lukas: It happens on all repos I have tested, but it only happens via SSH, HTTPs works fine (fast).
It happens on fetch, push and clone.
Comment by Daniel Milde (dundee) - Tuesday, 22 March 2016, 09:16 GMT
Any update about this? Timeouts still appear, only 1 of 5 attempts works for me.

$ git clone ssh+git://aur@aur.archlinux.org/python2-pypdf.git
Cloning into 'python2-pypdf'...
Timeout, server aur.archlinux.org not responding.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Comment by Daniel Milde (dundee) - Tuesday, 29 March 2016, 09:50 GMT
Now it looks working properly again.

Loading...