Teamcity agent in the disconnected state (the agent is unregistered (will be updated))

Question

Teamcity build agent in the disconnected state (the agent is unregistered (will be updated)) in the server interface. The build agent service was in a hang state, tried to restart, but still did not work, therefore, manually updated the TC build agent with the version server. Reboot the build agent service. Still disconnected. Please suggest.

Answer 1

I ran into this problem and found a solution, but I will make a few assumptions about your setup.

This fixed an issue that I encountered with TeamCity build agent on Windows and started as a user account (as opposed to a system account).

• Stopped TeamCity service and changed account to system account
• I started the TeamCity service and waited about 10 minutes to complete the update. The build agent appeared on the Connected Agents tab, indicating a successful upgrade.
• Stopped TeamCity service and switched back to user account
• Launched TeamCity Service

Another option is to grant user account permissions to start / stop services, but instead I went along this route. See this article for these steps.

Answer 2

Old question, but someone might find my comments helpful. If you cannot read the update logs, check the buildAgent/update/ folder, if the files and file sizes change in this particular folder, this means that the Agent is being updated, and you just have to wait. If this is not the case, but you still see Agent has unregistered (will upgrade) in the city of the team under "Agents" → "Disabled", the agent either freezes or there is some problem with it. Stop the agent from services, and then run agent.bat (Windows) and agent.sh (nix) by providing a stop argument, and then run it from the same script using the start argument. You can also see the status of the agent with the status argument. If this also does not work, you will have to read all the magazines.

Answer 3

This worked for me:

• On the Agents tab, I deleted the assembly agent by clicking Delete Agent.
• I restarted the service.
• I updated the Agents tab and the build agent appeared with unauthorized agents.
• I have authorized the agent and it is now connected.

Answer 4

These may be permissions for the account under which the agent runs. In BuildAgent \ Logs \ Upgrade.txt you can find this

Update Error: Failed to stop TeamCity Build Agent service. Verify that the TeamCity Build Service Agent has sufficient permissions to stop and start the service. java.io.IOException: Failed to stop TeamCity assembly agent service. Please verify that the TeamCity Build Service Agent has sufficient permissions to stop and start the service.

Despite the fact that the service works fine on the computer (windows in my case), it produces an error in this log, not the event viewer or it does not start, and disconnects from TeamCity when updating.

I gave higher privileges, and he began to work. +1 to the Lemtronix method if you do not want to limit the permissions of your service account.

Answer 5

For those who continued to restart the build agent service and saw that “Agent is unregistered (will be updated)”, check the log in the BuildAgent / logs section to view the update process and wait.

Answer 6

I had the same problem. I called the build, and the agent was automatically changed to the associated status.