upgrade from 4.5 to 4.5.3 - agent won't connect

Folks,

I just upgraded from 4.5 to 4.5.3.  I use the included windows service for my build agent, it runs under the account "Builder".
I'm finding that my agent is disconnected with the message " There were no builds on this agent or you do not have enough permissions to clean sources of build configurations built on this agent"

The builder account has full permission to
C:\TeamCity\buildAgent\work
as well as to
C:\Users\Administrator\.BuildServer

there is no c:\users\Builder\.BuildServer directory

please help!

6 comments
Comment actions Permalink

Suraj,

Please provide agent and server logs to allow us to investigate the issue.

Where do you see the message? Are the server and agent installed on the same machine? What are the agent settings (content of BuildAgent\conf\buildAgent.properties file)?

Agent process does not need .BuildServer directory. Only server process does.

0
Comment actions Permalink

Hi Yegor,
Its very strange...I eventually got this to work but I have no idea what I did (in fact i'm not sure I did anything).  It just started working after a number of restarts/reinstalls.  I must have uninstalled/reinstalled and restarted like 5 times.  The only thing that I think was different the last time is that I let the Agent install/run under the system account, got the same error message, switched the account to Builder in services.msc, and restarted the service (instead of initially isntalling/running in Builder).  but I can't be 100% certain that the last install was the only time I tried that sequence of events.

To answer your questions: I see the message from the Agent Tab.  I saw 1 Disconnected Agents.  When I drill down into the agent, I saw the message I posted.  Server and agent are installed on the same machine.   Contents of conf\buildAgent.properties is NOW (although it could have been different when it was not working...is there a way to tell?).  Can I provide any other information?  While everything is working fine now, I'd like to help you catch a bug if there is one.  I wouldn't like to have the same experience repeated.  Please let me know what I can do to help.


#Generated properties (see buildAgent.dist.properties for description)
#Thu Jun 18 18:09:47 EDT 2009
name=THEPARTY
ownPort=9090
serverUrl=http\://localhost\:4004
workDir=C\:\\TeamCity\\buildAgent\\work
tempDir=C\:\\TeamCity\\buildAgent\\temp
#User defined properties
#Thu Jun 18 18:09:47 EDT 2009
authorizationToken=2876dfb034b3a682f86614fea3a04627
env.TEAMCITY_JRE=C\:\\TeamCity\\jre



0
Comment actions Permalink

oh...I forgot to mention, when 4.5.3 uninstalled 4.5, I was running the webservice under port 4004.  When 4.5.3 installed, it installed to port 80.  I accidentally selected ok instead of changing the port to 4004.  In subsequent reinstalls, I switched to 4004.  could that have been the problem?

0
Comment actions Permalink

Suraj,

There is little to investigate without the agent logs. If you have the logs for the moment of agent not connecting, please attach them. If you do not have them already, please save all the agent logs if you encounter alike issues again.

The message "There were no builds on this agent or you do not have enough permissions to clean sources of build configurations built on this agent" does not seem like related to the agent disconnected state.

The only issue I'd point out is that the sequence of first agent connection is like that: connect, upgrade, connect. The upgrade stage can take time (minutes, sometimes) and the agent is in disconnected stage during the upgrade. So, next time please try to wait for some time before stopping/investigating why the agent is not connected.

0
Comment actions Permalink

Hi Yegor,

For future reference, where can I find the agent logs?

In terms of the wait time...I waited for an hour during all parts of the process.  I only posted after seeing the agent in a disconnected state for quite some time.

-Suraj

0
Comment actions Permalink

Suraj,

Agent logs can be found in <agent home>/logs directory. teamcity-agent.log

The files are described in our doc:http://www.jetbrains.net/confluence/display/TCD4/Logs+of+Internal+Events

To report issues about TeamCity you can also find the following page useful: http://www.jetbrains.net/confluence/display/TCD4/Reporting+Issues

Another common issue with disconnected agent is a machine with several network interfaces. You might need to specify machine IP address in agent's conf/buildAgnet.properties file in ownAddress property.

0

Please sign in to leave a comment.