Are EC2 build agents possible with Free Team City?

Hi - I'm doing some trials of TC with a view to replace my existing Bamboo/Elastic EC2/Jira setup.

My TC server website is up and running on EC2 on public DNS - everything seems fine there.

I installed a TC agent on a micro AMI - put the public DNS in serverURL. Also checked I could login to the TC Server website and had no issue there. I made an AMI from this and added to cloud configuration page.

The problem ( could be my understanding ) but once I start the cloud instance - the website says "No agents connected after instance start... Start the instance manually to check the instance again" . I can login to my agent and see the service is running and I have connectivity to my server - is there anything else I can troubleshoot in way of agent-cloud connectivity?

Also - I noticed theres is default local agent with TC - is the free version bound to the local agent or can TC server be used with a cloud agent with the 1 agent limit?

I attempted to push an Agent to this same AMI but are getting these errors too

[06:55:56]: Couldn't access ec2-xx-xxx-xx-x.compute-1.amazonaws.com:
[06:55:56]: Connecting to ec2-xx-xxx-xx-x.compute-1.amazonaws.com...
[06:55:56]: Remote agent installation failed: Command 'C:\TeamCity\temp\___1727799057969175728\cli-wrapper.exe C:\ProgramData\JetBrains\TeamCity\system\pluginData\psexec\psexec.exe /accepteula \\ec2-xx-xxx-xx-xx.compute-1.amazonaws.com -e -h -u Administrator -p ********** cmd.exe /C ver' was executed with error message(s): Execution error. Return code=6

Cheers!

1 comment
Comment actions Permalink

Just some more info - I checked teamcity-agent.log

[2014-02-09 07:31:35,994]   INFO - buildServer.AGENT.registration - Registering on server http://team.xxxx.com.au, AgentDetails{Name='WIN-XXXXXXXXXXX', AgentId=null, BuildId=null, AgentOwnAddress='null', AlternativeAddresses=[10.xxx.xxx.xxx, 54.xxx.xxx.xxx], Port=9090, Version='27767', PluginsVersion='NA', AvailableRunners=[], AvailableVcs=[], AuthorizationToken=''}
[2014-02-09 07:32:08,567]   WARN - buildServer.AGENT.registration - Call http://team.xxxx.com.au/RPC2 buildServer.registerAgent3: org.apache.xmlrpc.XmlRpcClientException: Server returned incorrect status code: 502 Bad Gateway
[2014-02-09 07:32:08,567]   WARN - buildServer.AGENT.registration - Connection to TeamCity server is probably lost. Will be trying to restore it. Take a look at logs/teamcity-agent.log for details (unless you're using custom logging).

I've opened up 9090 - and restarted the service and no change as yet.

0

Please sign in to leave a comment.