VCS Root checkout fails with the ls-remote timeout exception

Symptoms

VCS Root checkout fails with the error like:

jetbrains.buildServer.vcs.VcsRootVcsException: Timeout exception: jetbrains.buildServer.vcs.VcsException: git -c credential.helper= -c credential.helper=/Teamcity/TeamCity/temp/credHelper1135898789378362137.sh ls-remote origin command failed. exit code: -1 exception: jetbrains.buildServer.ProcessTimeoutException: Timeout exception: the process did not produce output longer than 60 seconds; Process: git -c credential.helper= -c credential.helper=/Teamcity/TeamCity/temp/credHelper1135898789378362137.sh ls-remote origin at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.createRootException(VcsChangesStatesCollector.java:117) at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.getCurrentState(VcsChangesStatesCollector.java:70) at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.lambda$getCollectStatesTasks$1(VcsChangesStatesCollector.java:3) at jetbrains.buildServer.vcs.impl.ImmediateFutureExecService$2.call(ImmediateFutureExecService.java:2) at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:63) at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:73) at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.collectStatesForAllRoots(VcsChangesStatesCollector.java:15) at jetbrains.buildServer.vcs.impl.VcsChangesStatesCollector.getCurrentStateSnapshot(VcsChangesStatesCollector.java:27) at jetbrains.buildServer.vcs.impl.VcsChangesFetcher.getStateAndCreateChangesCollectingTasks(VcsChangesFetcher.java:13) at jetbrains.buildServer.vcs.impl.VcsChangesLoader.doLoadChanges(VcsChangesLoader.java:24) at jetbrains.buildServer.vcs.impl.VcsChangesLoader.tryLoadChanges(VcsChangesLoader.java:152) at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction$1.run(VcsModificationChecker.java:28) at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:77) at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction.run(VcsModificationChecker.java:12) at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) at java.base/java.lang.Thread.run(Thread.java:1583) Caused by: jetbrains.buildServer.buildTriggers.vcs.git.command.errors.GitExecTimeout: Timeout exception: jetbrains.buildServer.vcs.VcsException: git -c credential.helper= -c credential.helper=/Teamcity/TeamCity/temp/credHelper1135898789378362137.sh ls-remote origin command failed. exit code: -1

Cause

The git ls-remote command didn't produce any output for more than 60 seconds, which is the default timeout for this operation in TeamCity.

Resolution

This timeout can be increased with the teamcity.git.repositoryStateTimeoutSeconds server internal property. The default value is 60.

If increasing the timeout doesn't help:

1. Log in to the machine where the TeamCity server is running.
2. Run git ls-remote <repository URL> command for the affected repository manually, under the same user that is used to run the TeamCity server process.
3. If the command didn't succeed and produced an error message, the issue is not related to TeamCity. It should be further investigated to make sure this command works.
4. If it succeeds, check how long it takes for the command to produce output, and increase the timeout further if needed.