000021362 - RSA ClearTrust servers running on UNIX may not stay up when started from SSH

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

Article Content

Article Number000021362
Applies ToRSA ClearTrust 5.5 Authorization Server (AServer)
Sun Solaris 2.8
IssueRSA ClearTrust servers running on UNIX may not stay up when started from SSH
RSA ClearTrust servers stop after user logs out of SSH session
ResolutionDepending on the shell settings, if ClearTrust servers are started from an SSH session and the user logs out after starting the server, the server process may terminate right away. To protect this from happening, the 'nohup' UNIX utility should be used. nohup allows an application to continue to run even after the user logs out. nohup can be added to the line that starts the JVM in which a particular ClearTrust server runs.

The Following is an example of using nohup with aserver.sh:

1. Read the man entry for nohup for full understanding of the nohup utility

2. Backup aserver.sh

3. Open aserver.sh for editing

4. prefix the line that launches the AServer with nohup as below:

   Before:
   $JAVA_HOME/bin/java -DAuth $JVM_OSARGS -Xmx128m $DEBUG \
        -Djava.ext.dirs=$JAVA_HOME/lib/ext:$CT_ROOT/lib \
        -DCT_ROOT=$CT_ROOT -DLISTEN_PORT=$LISTEN_PORT \
        sirrus.authserver.AuthorizationServer \
        >> ${LOGFILE:-/dev/null} 2>&1 &

   After:
   nohup $JAVA_HOME/bin/java -DAuth $JVM_OSARGS -Xmx128m $DEBUG \
        -Djava.ext.dirs=$JAVA_HOME/lib/ext:$CT_ROOT/lib \
        -DCT_ROOT=$CT_ROOT -DLISTEN_PORT=$LISTEN_PORT \
        sirrus.authserver.AuthorizationServer \
        >> ${LOGFILE:-/dev/null} 2>&1 &

5. Repeat this for all ClearTrust server shell scripts and restart the servers
Legacy Article IDa22608

Attachments

    Outcomes