Unable to check git repo after updating to 1.9.0.413

fixed

(StuY) #1

I have 4 git repos in my setup, hosted on Bitbucket and accessed over SSH. I updated to 1.9.0.143 today. Since then, I have been unable to check or reset one of the repos. The other 3 repos are accessed in exactly the same way, with the same SSH key, and are working perfectly. There are two recurring errors in the event logs:

  • Repository XXX cannot be initialised: Running ‘C:\Program Files\Git\cmd\git.exe’ with arguments “clone --no-checkout --progress *********************************************** C:\Users\ContinuaCI\ShareRoot\Rc\2149f40f” failed and threw exception: “Access is denied”

  • Repository XXX cannot be initialised: Running ‘C:\Program Files\Git\cmd\git.exe’ with arguments “clone --no-checkout --progress *********************************************** C:\Users\ContinuaCI\ShareRoot\Rc\2149f40f” failed with return code -1 and error output: “The process timed out as there was no response for 20s 0ms. Process was running for 21s 364ms in total.”

This is a large repo - it is possible that a new 20s timeout has been introduced?

Can you help me to interpret the ‘access denied’ message? What is this referring to? SSH access to the repo using the installed keys is working fine via git bash when logged in to Windows as the Continua user.

Really appreciate any clues on this.

Cheers…


(Dave Sparks) #2

Hi,

The Access is denied message is coming directly from the git command line. The 20 second timeout occurs only if there has been no output from the git command line for 20 seconds. This is usually because the git command line is prompting for input.

Can you try running the same git command in command prompt? e.g.

"C:\Program Files\Git\cmd\git.exe" clone --no-checkout --progress <your ssh url> C:\Users\ContinuaCI\ShareRoot\Rc\2149f40f

while logged in as the Continua service user and let us know what the output is.

Can you also let us know the format of your ssh url e.g. * user@host.xz:port/path/to/repo.git or ssh://user@host.xz:port/path/to/repo.git or git://host.xz/path/to/repo.git, and the version of the git command line that you are running.


(StuY) #3

Hi,

If I run the command manually via command prompt, logged in as the Continua user, it clones the repo as expected. It takes a few minutes as the transfer is ~400MB after compression. After a bit of retrying, this seems to have got it working, for now anyway.

The URL format is: git@bitbucket.org:USER/REPO.git

The git version was 2.8.1.windows.1. I have now updated it to 2.11.0.windows.1.

Thanks!
Stu


(Dave Sparks) #4

Was there a long delay before there was any output from the clone command? If so, approximately how long? We may need to make the timeout configurable.


(StuY) #5

There was some information output to the console immediately.


(Dave Sparks) #6

What I should have asked is whether there was any interval longer than 20 seconds where there was no output to the console?

I’ve done some testing cloning various large git repositories using version 2.8.1.windows.1 of Git for Windows and haven’t been able to reproduce a scenario where progress output pauses for more than a couple of seconds and causes a timeout. I guess however that network connectivity issues could cause a longer delay, so we have added the ability to change the timeout for the next version of Continua CI.

Meanwhile let us know if you encounter any further errors.

Note the latest version of Git for Windows is currently 2.21.0.windows.1


(StuY) #7

I did a bit more testing and saw some delays approaching 20s at the ‘counting objects’ stage. Perhaps if the remote was busy this could take longer; I’m guessing that stage is not network bandwidth limited. The progress reporting on the compression and transfer would normally prevent it getting to 20s without any output I think, unless it was a really huge transfer or very slow.

Potentially a lifesaver to have a configurable timeout; thanks!

Version number was an early-morning typo, I have the latest version now.

Cheers…


(StuY) #8

I encountered this problem again and can confirm that there was a period of more than 20s without output to the console, in this case during the ‘unpacking objects’ phase, when running:

C:\Users\ContinuaCI\AppData\Local\Programs\Git\cmd\git.exe fetch --prune --all

Running this on the local repo again cleared the problem for now.


(Dave Sparks) #9

Hi Stuy,

We plan to release a new version on Wednesday. This will include a configurable no-output timeout for Git repositories.