Over the weekend I noticed that a build had been hung for 63 hours. I tried stopping the build, but to no avail. I restarted all 3 of the build agents, but the same communication issues seem to keep happening. This (originally) was with 8.0.3. To try to fix the issue, I went ahead and updated the server to 8.0.4. After doing so, I started each one of the build agents, watched them unregister because of the new update, and then update themselves. The same thing is happening. When I kick off a build, you see the "Running..." status for a long time. If I look at the build agent, it doesn't appear that anything is going on or that it even received notice that it was supposed to do a build.
My question is this: where do I start to see why the TeamCity Server is unable to communicate with its build agents? Nothing is jumping out at me in the logs except for this (in the console of the build agent):
[2013-09-30 13:30:25,929] WARN - org.apache.xmlrpc.XmlRpc - java.net.SocketTimeoutException: Read timed out
From the build server, I can ping each of the individual agents and vice versa, so they are able to see each other. Any help would be greatly appreciated.
This was in the teamcity-agent.log as well:
[2013-09-30 13:35:29,085] WARN - buildServer.AGENT.registration - Call http://vm-tcserver:8080/RPC2 buildServer.registerAgent3: java.net.SocketTimeoutException: Read timed out