NolioAgent Fails to Start After Agent Upgrade
search cancel

NolioAgent Fails to Start After Agent Upgrade

book

Article ID: 248652

calendar_today

Updated On:

Products

CA Release Automation - Release Operations Center (Nolio)

Issue/Introduction

After upgrading nolio from 6.6 to 6.7 a deployment failed on some actions stating:

Action cannot be loaded - not supported on legacy OS agents (running JRE 1.6). Try to use equivalent action that ends with '(for legacy OS)' or pass manually.

As a result, we found that the agent it was trying to run on was 5.5.2 so we tried to upgrade the agent from the Nolio UI. This resulted in the agent stopping and failing to restart. 

Environment

Release : 5.5.2 Upgrade to 6.7

Component : Nolio Agent

 

Cause

During an agent upgrade, a few things happen. This includes: 

  • the nolio agent's binaries are upgraded from the current version it is running (in this case 5.5.2) to the new binaries/jars used by the new version of the agent.
  • the java binaries are updated from the current version it is running (in this case java 1.7) to the new binaries/jars used by the new version of the agent (in this case java 1.8.0_232)

The problem is that the 6.7 agent binaries are not compatible with java 1.7. 

You can use these steps to see if the solution in this KB applies:

  • Reviewing the logs/wrapper.log on the agent machine shows:
    • java.lang.UnsupportedClassVersionError: com/nolio/platform/deployer/WinRestarter : Unsupported major.minor version 52.0
  • Open a command prompt and changed to NolioAgent_InstallDir/jre/bin to run: java -version
    • Confirm it is using jre 1.7
  • Check the NolioAgentInstallDir/lib folder and confirm it has nolio-shared-6.7.0.jar
  • Confirm you have these two folders:
    • NolioAgentInstallDir/lib; and
    • NolioAgentInstallDir/lib_update

 

If all of the above are true then the Resolution described below applies.

 

Resolution

If the NolioAgent is started, this KB article does not apply. If you have confirmed, via the Cause section above, that this KB applies to your situation then use the steps below to resolve this problem: 

  • Rename the lib folder (which has the nolio-shared-6.7.0.jar file in it) to lib_new
  • Rename the lib_update folder (which has the nolio 5.5.2 jars/binaries in it) to lib
  • Start the agent.
  • Review the logs/wrapper.log file to confirm it completed the jre upgrade.
  • Open a command prompt and change to NolioAgentInstallDir/jre/bin to run: java -version
    • Confirm it is using jre 1.8.0_232
  • Stoped the agent.
  • Rename the lib to lib_old
  • Rename the lib_new to lib (so the agent will use the nolio 6.7 binaries)
  • Start agent