How to re-add a removed build agent?

Hi,

I am trying to install a second build agent for Team City 6.5.  The default build agent that gets installed with TC shows up and is usable.  However, when I install a build agent on another machine, using the windows installer provided from TC, I do not see the agent.  I was, at one point, able to see the additional build agent in the disconnected tab.  There were some issues with having port 9090 open on the specific ip address, so I thought I would "remove" the agent from TC and see if that helped reset things.  Now the agent does not appear.  I've tried reinstalling the additional build agent, but it still does not appear.  I do not see how to undo the Remove build agent from TC.

Is there a way to get a "removed" agent to be visible again?

5 comments
Comment actions Permalink

Please inspect teamcity-server.log for errors. Server opens network connections to the agents, and maybe Windows firewal on agent machine blocks them.

0
Comment actions Permalink

What should I be looking for?  My server log is over 20,000 lines...

I do see a lot of errors similar to:
[2011-06-14 15:13:37,763]   WARN -   jetbrains.buildServer.SERVER - Exception occurred while communicating by XML RPC: ClientAbortException:  java.net.SocketException: Connection reset by peer: socket write error /remote: 127.0.0.1:64339

It's worth noting that the additional agent's ip address was set to 127.0.0.1.  I did change the agent properties file to set the public IP address for the agent.

Also, part of the problem is getting TeamCity to re-recognize my additonal build agent.  It is not showing up in the Agents tab at all.  I have verified that the additional build agent can access the TC server via port 80.

0
Comment actions Permalink

Jim

to troubleshoot that I will need to look at full teamcity-server.log and teamcity-agent.log (from remote machine).

Thanks

0
Comment actions Permalink

Hi Jim

Sorry for late response.

If that's still actual, please

  1. change Administration > Server Configuration > Server URL from localhost to actual DNS name
  2. enable debug logging, restart that remote agent, and send these logs and additional teamcity-xmlrpc.log

Thanks
0
Comment actions Permalink

Thanks Michael,

I should have replied back here.  Yegor helped me offline with this issue.  Ultimately, I believe the cause was from my IT admin making a typo with the ip range that was able to access port 9090 to get to my build agent machine.  Additionally, I have TeamCity running on port 81 on my webserver.  I have a reverse proxy setup through IIS (using Application Request Routing) so that I can access it via teamcity.mydomain.com.  I ended up opening up port 81 on the webserver, and having the build agent access TeamCity directly through that port, rather than through the reverse proxy.

0

Please sign in to leave a comment.