Build agents disconnecting (TC 4.0)

We upgraded from TC 3 to 4 recently, and all is looking well. We are running the professional edition as of now. After upgrading I uninstalled the default build agent. Then I installed three build agents on the same machice. After each install I removed the service, edited the wrapper.conf file to have unique values, edited the build.properties to have unique ports (9090, 9091, 9092) and directories, and reinstalled the service. So now I have three services installed with three names.

When I run the first service, Agent 1 connects and is authorized. When I ran the second service Agent 2 connected after a minute or so then immediately disconnected. I then unauthorized Agent 2. After that I ran the third service and after a minute or so Agent 3 connected and immediately disconnected. I also noticed that Agent 2's service stopped running. So I re-ran Agent 2 and I unauthorized Agent 3. After about 5-10 minutes Agent 3 showed up as connected, and I authorized it.

Now I have all three services running, all three agents have at one time connected but only 2 are staying connected. I have tried restarting Agent 2's service again but it doesn't seem to help. Any ideas on what's going on?

5 comments
Comment actions Permalink

I just noticed that my Agent 2 bin directory is now empty. I'm going to uninstall it and reinstall.

0
Comment actions Permalink

This may be a result of starting build agent service while agent is upgrading. Could you please attach zipped logs folder of agent2.
Thanks!

0
Comment actions Permalink

That looks like it might be the case.

[2008-12-03 10:11:56,595]   INFO - ver.agent.upgrade.AgentUpgrade - Finish upgrade at Wed Dec 03 10:11:56 EST 2008
[2008-12-03 10:11:56,595]   INFO - r.agent.upgrade.UpgradeRunBase - Run command line (arguments seperated with '|': cmd.exe|/c|D:\ContinuousIntegration\Tools\TeamCityBuildAgent2\bin\service.start.bat| (at D:\ContinuousIntegration\Tools\TeamCityBuildAgent2\bin)
[2008-12-03 10:11:57,423]   WARN - .agent.run.ProcessOutputLogger - 'D:\ContinuousIntegration\Tools\TeamCityBuildAgent2\bin\service.start.bat' is not recognized as an internal or external command,
[2008-12-03 10:11:57,423]   WARN - .agent.run.ProcessOutputLogger - operable program or batch file.
[2008-12-03 10:11:57,517]   WARN - .agent.run.ProcessOutputLogger - 
[2008-12-03 10:11:57,517]  ERROR - r.agent.upgrade.UpgradeRunBase - java.io.IOException: Failed to start process. Return code was 1 not equal to zero.
java.io.IOException: Failed to start process. Return code was 1 not equal to zero.


I can't figure out how to attach a file to my comment.


Dan Lash

0
Comment actions Permalink

Please try sending it to email: eugene [dot] petrenko [dogg] jetbrains.com
Thanks!

0
Comment actions Permalink

That must have been the problem. I reinstalled Agent 2 and started the service. It didn't connect for 5 minutes but I didn't stop the service, but it has now and it is connected, authorized, and building!

Thanks a lot, Eugene!


Dan Lash

0

Please sign in to leave a comment.