Upgraded to TC 8: Getting handshake_failure from Build Agents

Hello,I just upgraded from TC 7.1 to TC 8.  Everything went great and I can access TC via the web browser with out any issues, but no build agents are able to connect.  wrapper.log on the Build Agent gives the follow error:INFO   | jvm 1    | 2013/06/25 11:02:36 | Registering on server[redacted], AgentDetails{Name='[redacted]', AgentId=null, BuildId=null, AgentOwnAddress='null', AlternativeAddresses=[redacted], Port=9091, Version='27402', PluginsVersion='27402-md5-a735f411177e302ee054b4dac8d66f43', AvailableRunners=[Ant, dotnet-tools-dupfinder, dotnet-tools-inspectcode, Duplicator, FxCop, gradle-runner, Inspection, Ipr, jb.nuget.installer, jb.nuget.pack, jb.nuget.publish, jetbrains.dotNetGenericRunner, jetbrains.mspec, jetbrains_powershell, JPS, Maven2, MSBuild, MSTest, NAnt, NUnit, rake-runner, simpleRunner, sln2003, VS.Solution], AvailableVcs=[perforce, mercurial, jetbrains.git, tfs, svn, cvs], AuthorizationToken='[redacted]'} INFO   | jvm 1    | 2013/06/25 11:02:36 | Call [redacted] buildServer.registerAgent3: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure Has any one run into this issue.  Anyone know how to troubleshoot this kind of issue?Thanks,Patrick
4 comments
Comment actions Permalink

If your agents connect to TeamCity server by https, then most likely you need to import certificates in JVM used by the agent.

0
Comment actions Permalink
Pavel,Thanks for the response.  At the end of the day I ended up just manually updating the agent with the MSI installer and that seemed to do the trick.I wonder if something changed in how the TC 8 build agent presents the SSL cert to the agents that causes older (7.1) agents to not complete the handshake.Thanks,Patrick
0
Comment actions Permalink
Fixed this issue by manually updating agent.
0

Please sign in to leave a comment.