git lfs clone failing on centos 7 over ssh

Martin Slater February 1, 2018

Hi there,

I am trying to clone a repository that is using git-lfs from centos 7 using ssh but this fails after ~5gb of data is transferred. The same clone from a windows box appears to work 99% of the time although I have had some internal reports of intermittent failures as well. The command line is just

 git lfs clone ssh://git@git.****.net:7999/waws/waws.git

The symptoms are the clone is happily progressing then it decides to change to basic authentication and brings up a prompt asking for a password. The tail of the logs around this are below with thousands of successful lines prior to this.

 

trace git-lfs: HTTP: GET https://git.****.net/rest/git-lfs/storage/WAWS/waws/a5f4bcf9427e5ed7a5c261bab84fffd5f6417780588c315f6ba4dd1f6e8c34f6
trace git-lfs: HTTP: 200
13:25:04.620367 git.c:371 trace: built-in: git 'credential' 'approve'
13:25:04.620633 git.c:371 trace: built-in: git 'credential' 'approve'
13:25:04.622580 git.c:371 trace: built-in: git 'credential' 'approve'
13:25:04.630627 git.c:371 trace: built-in: git 'credential' 'approve'
13:25:04.638202 git.c:371 trace: built-in: git 'credential' 'approve'
trace git-lfs: tq: sending batch of size 100
trace git-lfs: ssh cache: git.****.net git-lfs-authenticate wows/wows.git download
trace git-lfs: api: batch 100 files
trace git-lfs: HTTP: POST https://git.****.net/scm/wows/wows.git/info/lfs/objects/batch
trace git-lfs: HTTP: 401
trace git-lfs: setting repository access to basic
trace git-lfs: run_command: 'git' config lfs.https://git.****.net/waws/waws.git/info/lfs.access basic
trace git-lfs: api: http response indicates "basic" authentication. Resubmitting...
trace git-lfs: creds: git credential fill ("https", "git.****.net", "waws/waws.git/info/lfs")
13:25:06.254941 git.c:371 trace: built-in: git 'credential' 'fill'
13:25:06.255289 run-command.c:369 trace: run_command: 'git credential-cache --timeout=2600 get'
13:25:06.255923 run-command.c:228 trace: exec: '/bin/sh' '-c' 'git credential-cache --timeout=2600 get' 'git credential-cache --timeout=2600 get'
13:25:06.260598 git.c:595 trace: exec: 'git-credential-cache' '--timeout=2600' 'get'
13:25:06.260701 run-command.c:369 trace: run_command: 'git-credential-cache' '--timeout=2600' 'get'

 

Versions are :-

  Self hosted Bitbucket - v5.5.0

  Git client - 2.12.1

  Git LFS - 2.3.0 (2.34 has also been tested with the same issue).

 

this is a big blocker for one of our key internal processes, can anyone suggest what may cause and how to fix or work around this issue?

 

thanks

 

Martin

 

1 answer

0 votes
mell0 November 12, 2019

Hi,

 

Same problem here. I headbanged almost a day why it isn't working and finally it turned out that I had to change my bitbucket account password and it worked fine after that. I don't know how this was related since I could clone and push fine other repositories, but repositories with git lfs failed, so I guess somewhere along the chain there was a problem and git lfs couldn't authorize my password and after change it updated it and everything worked fine.

Good luck.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events