Couldn't get lock for /opt/rsa/am/server/logs/rsaserv.log error when trying to list services on RSA Authentication Manager 8.x

Originally Published: 2018-09-27

Last Modified: 2022-06-20

Article Number

000041119

Applies To

RSA Product Set: SecurID
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.x

Issue

When trying to list services using ./rsaserv status on the RSA Authentication Manager server through the command line interface, the following error message appears:

Traceback (most recent call last):
  File "/opt/rsa/am/components/ims/unix/rsaservManager.py", line 22, in <module>
    execfile(RSA_SCRIPT_HOME + "/rsaServMgrLogging.py")
  File "/opt/rsa/am/components/ims/unix/rsaServMgrLogging.py", line 55, in <module>
    fileHandler = FileHandler(RSASERV_DIR + '/logs/rsaserv.log', 0, 10) # No file limit, 10 files to save
        at java.util.logging.FileHandler.openFiles(FileHandler.java:389)
        at java.util.logging.FileHandler.<init>(FileHandler.java:323)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
        at org.python.core.PyReflectedConstructor.constructProxy(PyReflectedConstructor.java:163)

java.io.IOException: java.io.IOException: Couldn't get lock for /opt/rsa/am/server/logs/rsaserv.log

Cause

File permissions in the /opt/rsa/am/server directory or with r saserv.sh and rsautil.sh have been changed.

Resolution

Rebooting the affected server should reset the permission and release any locks on the system.

Don't see what you're looking for?

Related Articles

Trending Articles