VCS root checkout fails - List remote refs failed - java.net.SocketTimeoutException: Read timed out
We had a working teamcity deployment with VCS roots configured to checkout git repos.
This morning, all VCS root checkouts started failing with no changes on the teamcity server or agents. The network connectivity looks fine. If we try to manually clone the same repository on the same server using the same keys, it works.
After enabling debug logging for vcs using the debug-vcs preset this is what is seen in the teamcity-vcs log
[2018-02-22 21:55:11,919] DEBUG [ical executor 3] - jetbrains.buildServer.VCS - VCS connection problem in build <redacted build-name>: Failed for the root ‘”<redacted repo-name>” {instance id=411, parent internal id=80, parent id=<redacted project_name>, description: “<redacted>”}: List remote refs failed: com.jcraft.jsch.JSchException: Session.connect: java.net.SocketTimeoutException: Read timed out
jetbrains.buildServer.vcs.VcsRootVcsException: List remote refs failed: com.jcraft.jsch.JSchException: Session.connect: java.net.SocketTimeoutException: Read timed out
----- more
[2018-02-22 21:55:11,920] DEBUG [ical executor 3] - Triggers.vcs.git.GitServerUtil - Ensure repository at '/teamcity/pf9/.BuildServer/system/caches/git/git-E0BC6796.git' has a valid config file
I tried clearing the git cache from admin options, but that did not help.
I would appreciate any pointers on how to fix this.
Please sign in to leave a comment.
Hi Deepit,
I faced the same issue this morning on our VCS roots, it appears Github has changed some TLS/SSL settings and as a quick changing to use HTTPS with username and password rather than SSL with a public key seems to work, I'm still looking into what the the issue with SSH is and will let you know if I find it :)
Hope this helps!!
-- Joe
We've bypassed the problem temporarily by changing checkouts to run on the server rather than the agent. YMMV.
If you're using IntelliJ you'll also need to switch to native SSH checkout rather than the builtin one.
Hi all,
if your issue comes from the github change, please check and try to follow our instructions here: https://youtrack.jetbrains.com/issue/TW-52052#comment=27-2607007