The Remote AveksaAgent fails to start as a service on Windows in RSA Governance and Lifecycle
a month ago
Article Number
000068202
Applies To
  • RSA Governance & Lifecycle 8.0.0 P09
  • SecurID Governance & Lifecycle 7.5.2 P04, P05, P06
Issue

The Remote AveksaAgent fails to start as a service on Windows machines:

image-2023-05-28-17-33-26-536.png

The following exception is shown in the wrapper.log:

INFO   | jvm 1    | 2023/05/28 10:20:06 | WrapperSimpleApp: Unable to locate the class com.aveksa.client.datacollector.startup.Bootstrap: java.lang.NoClassDefFoundError: org/apache/log4j/Logger



 

Cause

Java classpath in the wrapper.conf file is pointing to a different log4j.jar file, hence remote agent was failing to start as a service.

Resolution

This issue is resolved in the following versions/patches:

  • RSA Governance & Lifecycle 8.0.0 P10
  • SecurID Governance & Lifecycle 7.5.2 P07
Workaround

WORKAROUND for RSA Governance & Lifecycle 8.0.0 P09:

Follow the below steps as a workaround on RSA Governance & Lifecycle 8.0.0 P09 to run the remote agent as a service on a Windows machine:

  • Stop RemoteAgent if running already.
  • Uninstall Remote Agent by running "UninstallAvAgent-NT.bat" as Administrator in AveksaAgent/bin folder.
  • Download Remote Agent zip from UI and re-deploy the agent on windows box (this includes removing the old AveksaAgent folder and unzipping the new agent zip into a new folder).
  • Locate the below lines in wrapper.conf file present under AveksaAgent/conf folder:
    • wrapper.java.classpath.3=../common/lib/log4j-1.2-api-2.17.2.jar
    • wrapper.java.classpath.4=../common/lib/log4j-api-2.17.2.jar
    • wrapper.java.classpath.5=../common/lib/log4j-core-2.17.2.jar
  • Update the above lines as follows in the same file & save the changes:
    • wrapper.java.classpath.3=../common/lib/log4j-1.2-api-2.21.0.jar
    • wrapper.java.classpath.4=../common/lib/log4j-api-2.21.0.jar
    • wrapper.java.classpath.5=../common/lib/log4j-core-2.21.0.jar
  • Go to Remote agent bin folder & install agent by running "InstallAvAgent-NT.bat" file as Administrator.
  • Go to Services window and start AveksaAgent service.

 

WORKAROUND for SecurID Governance & Lifecycle 7.5.2 P04-P06:

Follow the below steps as a workaround on SecurID Governance & Lifecycle 7.5.2 P04 through P06 to run the remote agent as a service on a Windows machine:

  • Stop RemoteAgent if running already.
  • Uninstall Remote Agent by running "UninstallAvAgent-NT.bat" as Administrator in AveksaAgent/bin folder.
  • Download Remote agent zip from UI and re-deploy the agent on windows box (this includes removing the old AveksaAgent folder and unzipping the new agent zip into a new folder).
  • Remove the below lines in wrapper.conf file present under AveksaAgent/conf folder:
    • wrapper.java.classpath.3=../common/lib/log4j-1.2.17-1.0-rsa-1.jar
    • wrapper.java.classpath.4=../conf
  • Add below lines in the same file & save the changes:
    • wrapper.java.classpath.3=../common/lib/log4j-1.2-api-2.17.2.jar
    • wrapper.java.classpath.4=../common/lib/log4j-api-2.17.2.jar
    • wrapper.java.classpath.5=../common/lib/log4j-core-2.17.2.jar
    • wrapper.java.classpath.6=../conf
  • Go to Remote agent bin folder & install agent by running "InstallAvAgent-NT.bat" file as Administrator.
  • Go to Services window and start AveksaAgent service.