TeamCity Agent on machine with multiple network adapters

We are trying to install an agent on a machine that has multiple network adapters.

One of these adapters (slot) has an IP and is pingable etc, but the second adaptor (onboard) is set up with IP but is not pingable (it is used as part of a backup strategy).

Unfortunately, TeamCity appears to pick the hidden adapter when trying to communicate with the TeamCity Server.

We get the following error:

INFO - buildServer.AGENT.registration - Registering agent "Build Agent 2" (aaa.bb.cc.ddd:9090) on http://OurTeamCityServer:8111 with runners:
WARN - buildServer.AGENT.registration - Call http://OurTeamCityServer:8111/RPC2 buildServer.register: org.apache.xmlrpc.XmlRpcException: java.lang.Exception: jetbrains.buildServer.CannotPingAgentException: Unable to ping agent aaa.bb.cc.ddd Build Agent 2. Please check firewall on agent machine


where aaa.bb.cc.ddd is the hidden IP on the build agent.

Is there anyway we can set the which adapter (IP) the agent should use?
I've found nothing obvious thus far in the config files.



Thanks.

2 comments

You should provide correct IP address to ownAddress property in buildAgent.properties file:
ownAddress=]]>

--
Pavel Sher

0

That did the trick :)


Many thanks for the quick response.

0

Please sign in to leave a comment.