Help: Missed VCS plugins on agent: Subversion ?

I have installed better than 10 agents and I have never seen this happen.
I have many builds that are incompatible with a new build machine that has been setup with Subversion like the others.

With most of my builds I get "Missed VCS Plugins on Agent"   -  Subversion


Any thoughts or ideas?

Subversion is installed and in the path for the agent.

Thanks

10 comments
Comment actions Permalink

Never mind,   We figured out that the SvnAgent zip file was not extracted and installed at all during the agent install.  Not sure why this happened but I was able to extract the SVN files and restart the buildagent and everything is working now.

0
Comment actions Permalink

This happened to me too.

0
Comment actions Permalink

This just happened to me too.

I had installed the agent before installing Subversion so the problem was to be expected.  I then installed Subversion, rebooted, to no avail.  Looking at the log files, I saw that the plug-in was not loaded. I then manually unpacked the plugin (svnAgent) and restarted the agent.  The log files told me that the plugin was now found and loaded (no error message either), but it would still not work.

Uninstalling the agent and reinstalling it solved the problem.

I was not using the latest TC version though.  I was working with 4.5.6

0
Comment actions Permalink

Guys,

First of all, TeamCIty agent does not need subversion client to be installed ont he agent machine (TeamCity uses java SvnKit library to communicate with Svn server).

What you describe looks like inability to upgrade agent plugins which is an indication of environment misconfiguraiton.

To help us analyze the problem, can you pelase attach agent logs covering the moment of agent first start and being in incompatible state?
Also, can you please check whether the user under whcih agent runs has write access to allthe directories under TeamCity agent home?

0
Comment actions Permalink

Hello,

  The only possible reason for the problem I see is that at some moment the build agent update process was interrupted, and it didn't unpack all the plugins, including svnAgent.zip .
  In this case, I think there are some other unpacked plugins as well, like testNGPlugin.zip or tfs-agent.zip.

  To fix the problem and ensure all plugins are unpacked, please remove buildAgent/plugins/* and restart the build agent. It will take some time for plugins to be downloaded and unpacked, so please don't do anything with build agent for a couple of minutes.

  In our turn, we should detect such situations and fix them.
  Please watch/vote for http://youtrack.jetbrains.net/issue/TW-11301

  Regards,
  KIR

0
Comment actions Permalink

Sorry guys, but when I reinstalled TeamCity, I uninstalled the previous one first, and then deleted the TeamCity directory, to have a clean install, so I don't have the logs.

If I have the situation again, I'll be sure to send you the logs.

0
Comment actions Permalink

Ok, I installed it to another agent and had the same situation:

The installation process ran smoothly, no interuption.  The user had complete access to everything on the disk.

Attached are the logs.

Please keep in mind that this is not the latest TC version. This was done with 4.5.6



Attachment(s):
logs.zip
0
Comment actions Permalink

Pascal,

There is something strange in the log:
the agent upgrade log ends with a line:

[2010-03-17 11:19:06,444]   INFO - buildServer.agent.LauncherUtil - Unpacking C:\TeamCity\buildAgent\plugins\dotnetPlugin.zip: 6325823 bytes

and does not have any other information in it, while there should be.

Do I understand correctly that the agent is registered on the server (is visible on Connected agents), but is not compatible with the build configuration?

Is it possible that something prevented the upgrade from finishing properly? Some antivirus software? Disk space issues? Is there anything relevant in the Windows Event Log?

If the agent is still in this half-updated state, can youy please attach the full (recursive) files listing of the agent home directory?

0
Comment actions Permalink

Hi Yarko,

Is it possible that something prevented the upgrade from finishing properly? Some antivirus software? Disk space issues? Is there anything relevant in the Windows Event Log?

There doesn't seem to be anything relevant in the Event Viewer.  I saved them into txt to parse them just to be sure.  It still could be a restriction in the firewall, but then why would a reinstall solved it my last time?  I didn't resorted yet to this on that machine, thinking you might want to try a few things first.  If you want me to try accessing something from this machine, I can.  I am writing this on the problematic machine by the way.

Do I understand correctly that the agent is registered on the server (is visible on Connected agents), but is not compatible with the build configuration?

The Agent is indeed registered and connected on the TeamCity server (albeit disabled right now).  It's when I click on it, in the Compatible configurations tab, 80 out of 182 configurations are Incompatible:
Missed VCS plugins on agent:

  • Subversion


If the agent is still in this half-updated state, can youy please attach the full (recursive) files listing of the agent home directory?

Attached.



Attachment(s):
TeamCityListing.txt.zip
0
Comment actions Permalink

Pascal,

Thank you for the listing. It seems the agent upgrade process was killed abruptly.
So far I have only two guesses:
- the machine was rebooted while the agnet was upgrading event log should have entries on that around 2010-03-17 11:20
- the agent upgrade process was aborted manually  (process kill) or by some automatic software and agent service was started manually after that.

To fix the agent you can stop the agent, delete <agent home>/plugins and start it again: it should download the plugins and upgrade automatically.

0

Please sign in to leave a comment.