Local Build Agent intermittent connectivity issues
For some reason we are having problems with our builds hanging regularly on the finish build step. We are running Teamcity on Windows and all the Build Agents are installed locally on the same server. Once an agent hangs it seems to loop through registering with the server, failing to send finish build, and then failing to register. This repeats for 20-40 minutes until it appears to abandon the build and becomes available again?
There are errors in the teamcity-agent.log, but I am not sure where to look. A couple things I have tried are changing the server url to localhost and specifying agent ownAddress as the server IP.
The two exceptions I keep seeing:
[2020-03-11 11:44:50,799] INFO - r.agent.impl.AgentLogProxyImpl - Failed to perform remote command 'buildFinishedOnAgent' for build with id 2931, error: jetbrains.buildServer.xmlrpc.RemoteCallException: Call 'http://localhost/RPC2', method 'buildServer.buildFinished' failed: java.net.SocketTimeoutException: Read timed out: jetbrains.buildServer.xmlrpc.RemoteCallException: Call 'http://localhost/RPC2', method 'buildServer.buildFinished' failed: java.net.SocketTimeoutException: Read timed out (enable debug to see stacktrace)
[2020-03-11 11:44:55,808] INFO - r.agent.impl.AgentLogProxyImpl - Failed to perform remote command 'pingAndReregister' for build with id 2931, error: java.lang.Exception: Unable to register on server, pingable: java.lang.Exception: Unable to register on server, pingable (enable debug to see stacktrace)
Please sign in to leave a comment.
Does the issue affect any specific local agents or all of them?
I suggest to enable the debug logging for the agent(s) in question first (please see the details here: https://www.jetbrains.com/help/teamcity/viewing-build-agent-logs.html#ViewingBuildAgentLogs-GenericDebugLogging). When agent would fail in this fashion, could you please upload teamcity-agent.log, teamcity-server.log and teamcity-activities.log (two latter found at <teamcity-installation-home>/logs) by clicking on "Submit a Request" and attaching the files, so that I could check the server state during the issue?
It was doing it on and off for awhile, but hasn't happened recently. If it starts happening again, I will try to capture and upload logs.