Teamcity log is growing

My log file grows and contains only one line repeted.
================
Can't register agent 'Windows_Agent' using xml-rpc protocol: Unable to ping agent 'Windows_Agent'. Details: Agent cannot be accessed by any of the addresses: [10.199.28.11], (port 9090).
================
We had agent with such name. But now there is no agent with such name in list of connected and in list of disconnected agents.


Is it possible that some other agent (we have clone virtual server that contains that agent) try to connect from other IP but in its properties point old IP and teamcity can't connect using wrong credentionals?

3 comments
Comment actions Permalink

Hi Alexey,

This warning indicates that agent can't be accessed from the server. The IP used by TeamCity server to connect to the build agent is detected by build agent automatically, if it is not specified using ownAddress=<own IP address> property in the agent.properties file. Did you set this property?
What TeamCity version do you use? Since TeamCity 9.1 unidirectional agent-to-server communication was implemented and is recommended one. In this case if agent can't be accessed from the server, then it will switch to polling protocol. Please consider the upgrade and switching to the new protocol.

0
Comment actions Permalink

Alina , we are using v9.1.7 , What can be the reasons for unidirectional protocol failing ?

 

We are getting agent can't be pinged using unidirectional .

0
Comment actions Permalink

Hi Team. Agent can't be pinged is typically that the server cannot initiate a connection to the agents on their reported ips. Make sure traffic from server to agent is allowed.

0

Please sign in to leave a comment.