000030995 - Remote agent installation steps for RSA IMG

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000030995
Applies ToRSA Product Set: Identity Management and Governance (IMG)
RSA Product/Service Type: Appliance and Software install
RSA Version/Condition: All Versions
Platform: Linux
O/S: RedHat, SuSE
IssueRemote agent installation failure with below error in wrapper.log file.
======================================================================
STATUS | wrapper  | 2015/06/30 16:42:54 | WARNING: Could not write lock file /var/lock/subsys/avagent: Permission denied
STATUS | wrapper  | 2015/06/30 16:42:54 | --> Wrapper Started as Daemon
STATUS | wrapper  | 2015/06/30 16:42:54 | Launching a JVM...
ERROR  | wrapper  | 2015/06/30 16:42:54 | Unable to start JVM: No such file or directory (2)
ERROR  | wrapper  | 2015/06/30 16:42:54 | JVM exited while loading the application.
STATUS | wrapper  | 2015/06/30 16:42:59 | Launching a JVM...
ERROR  | wrapper  | 2015/06/30 16:42:59 | Unable to start JVM: No such file or directory (2)
ERROR  | wrapper  | 2015/06/30 16:42:59 | JVM exited while loading the application.
STATUS | wrapper  | 2015/06/30 16:43:03 | Launching a JVM...
ERROR  | wrapper  | 2015/06/30 16:43:03 | Unable to start JVM: No such file or directory (2)
ERROR  | wrapper  | 2015/06/30 16:43:03 | JVM exited while loading the application.
STATUS | wrapper  | 2015/06/30 16:43:07 | Launching a JVM...
ERROR  | wrapper  | 2015/06/30 16:43:07 | Unable to start JVM: No such file or directory (2)
ERROR  | wrapper  | 2015/06/30 16:43:07 | JVM exited while loading the application.
STATUS | wrapper  | 2015/06/30 16:43:11 | Launching a JVM...
ERROR  | wrapper  | 2015/06/30 16:43:11 | Unable to start JVM: No such file or directory (2)
ERROR  | wrapper  | 2015/06/30 16:43:11 | JVM exited while loading the application.
FATAL  | wrapper  | 2015/06/30 16:43:11 | There were 5 failed launches in a row, each lasting less than 300 seconds.  Giving up.
FATAL  | wrapper  | 2015/06/30 16:43:11 |   There may be a configuration problem: please check the logs.
STATUS | wrapper  | 2015/06/30 16:43:12 | <-- Wrapper Stopped
============================================================
Resolution0. Follow the guide for prerequisites such as jdk 1.6 installation and creation and download of the agent
1. Create an unprivileged account for the agent to run in (avagent in this example).
2. For the agent account, export JAVA_HOME and put $JAVA_HOME/bin on the path.

su -l avagent
export JAVA_HOME=/etc/alternatives/java_sdk_1.6.0
export PATH=$PATH:/etc/alternatives/java_sdk_1.6.0

To set in bash for next login for avagent account add the lines above to the .bash_profile:
=======================================================================
# User specific environment and startup programs
 
PATH=$PATH:$HOME/bin
 
export JAVA_HOME=/etc/alternatives/java_sdk_1.6.0
export PATH=$PATH:/etc/alternatives/java_sdk_1.6.0
========================================================================
3. Copy the AveksaAgent subdirectory to the agent account. Change permissions of all files to the
agent account. Make everything in bin executable
• cd path-to-AveksaAgent
• chmod 755 bin/*
4. To start the agent in background as avagent:

cd /home/avagent/AveksaAgent/bin
sh agent.sh start &
===================================================

[1] 23795
[avagent@small-08 bin]$ JAVA_HOME: /usr/bin/jdk1.6.0_45
checkJavaExes...
java found
All java executables found, continuing . . .
Using AGENT_HOME:    /home/avagent/AveksaAgent
Using JAVA_HOME:     /usr/bin/jdk1.6.0_45
Using CLASSPATH:     /home/avagent/AveksaAgent/bin/bootstrap.jar:/home/avagent/AveksaAgent/common/lib/log4j-1.2.14.jar:/home/avagent/AveksaAgent/conf:/home/avagent/AveksaAgent/agent/lib
Run
cmd args:  start
=========================================================================

The process is in the background running, the UI will show the agent running, the aveksaAgent.log shows all relevant information and status:
=================================================================

ps -ef | grep agent
==========================================================================
avagent  23795 17024  0 02:52 pts/1    00:00:00 sh agent.sh start
avagent  23800 23795  2 02:52 pts/1    00:00:02 /usr/bin/jdk1.6.0_45/bin/java -Djava.endorsed.dirs=/home/avagent/AveksaAgent/common/endorsed -classpath /home/avagent/AveksaAgent/bin/bootstrap.jar:/home/avagent/AveksaAgent/common/lib/log4j-1.2.14.jar:/home/avagent/AveksaAgent/conf:/home/avagent/AveksaAgent/agent/lib -Dagent.home=/home/avagent/AveksaAgent com.aveksa.client.datacollector.startup.Bootstrap start start

Attachments

    Outcomes