000030033 - Running ./rsaserv command displays errors on the log4j file for RSA Authentication Manager 8.x

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support on Dec 12, 2019
Version 4Show Document
  • View in full screen mode

Article Content

Article Number000030033
Applies ToRSA Product Set: SecurID
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.x
IssueRunning the ./rsaserv status command from /opt/rsa/am/server throws a log4j error as follows:

log4j:ERROR Could not read configuration file [test/resources/log4j.properties].
java.io.FileNotFoundException: test/resources/log4j.properties (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:120)
at java.io.FileInputStream.<init>(FileInputStream.java:79)
CauseThe Could not read configuration file error happens when the log4j.properties file is missing from /opt/rsa/am/utils/etc/rsaserv.  There is currently no known cause for this file not to be in the directory.  This behavior has been seen when a customer patched the Authentication Manager system directory from the hard drive.
ResolutionTo resolve the error, copy the log4j.properties file from a replica server's /opt/rsa/am/utils/etc/rsaserv directory to the proper path on the primary.  If there is no replica in the deployment, contact RSA Customer Support for the file.