1 Reply Latest reply on Mar 26, 2015 4:23 PM by Bill Robinson

    Agent upgrade skipped/server already in use

      We are upgrading Test agents to the latest patch level of 8.5 SP1 and I had one fail with the following message:

       

       

      Warning               03/26/2015 16:33:39       Agent upgrade is being skipped on server '<servername>'. The server is already in use by job/s: 'analysis-2000149-Copy of Windows Patch Group 1T A2014-08-06 11-08-36-009-0400 analysis-2000149-Windows Patch Group 1T2014-08-06 11-08-36-009-0400 analysis-2000149-Windows Patch Group 1T2014-08-06 11-08-36-009-0400 analysis-2000149-Windows Patch Group 1T2014-08-06 11-08-36-009-0400 analysis-2000149-Windows Patch Group 1T2014-08-06 11-08-36-009-0400 analysis-2000149-Windows Patch Group 1T2014-08-06 11-08-36-009-0400 analysis-2000149-Windows Patch Group 1T2014-08-06 11-08-36-009-0400 analysis-2000149-Windows Patch Group 1T2014-08-06 11-08-36-009-0400 analysis-2000149-Windows Patch Group 1T2014-08-06 11-08-36-009-0400 analysis-2000149-Windows Patch Group 1T2014-08-06 11-08-36-009-0400 analysis-2000149-Windows Patch Group 1T2014-08-06 11-08-36-009-0400 analysis-2000149-Windows Patch Group 1T2014-08-06 11-08-36-009-0400 analysis-2000149-Windows Patch Group 1T2014-08-06 11-08-36-009-0400 analysis-2000149-Windows Patch Group 1T2014-08-06 11-08-36-009-0400 analysis-2000149-Windows Patch Group 1T2014-08-06 11-08-36-009-0400 analysis-2000149-Windows Patch Group 1T2014-08-06 11-08-36-009-0400 analysis-2000149-Windows Patch Group 1T2014-08-06 11-08-36-009-0400 analysis-2000149-Windows Patch Group 1T2014-08-06 11-08-36-009-0400 analysis-2000149-Windows Patch Group 1T2014-08-06 11-08-36-009-0400 analysis-2000149-Windows Patch Group 1T2014-08-06 11-08-36-009-0400 analysis-2000149-Windows Patch Group 1T2014-08-06 11-08-36-009-0400 '

       

      The repetition of the job name looks like some sort of logging artifact.  I went to the server and cleaned out the RSCD/tmp folder which contained a blpatchcheck2.lck file.  Tried to upgrade the agent again, same result. Restarted the RSCD agent & tried to upgrade again, same result.

       

      I am assuming I could simply run the agent upgrade locally, but would like to know what's going on that this server is locked by a job that was run 7+ months ago (1T2014-08-06, in our naming convention).