Sick error after successful login on /KMS key-manager.log shows 'com.chrysalisits.crypto.LunaException: LunaSession: slot uninitialized'
Originally Published: 2011-10-02
Article Number
Applies To
SafeNet Luna SA HSM
M-of-N is configured on SafeNet Luna partition
Activation and AutoActivation policies were enabled when SafeNet HSM partition was created
Issue
SafeNet command './vtl verify' works fine and shows list of slot(s) and partition(s)
"partition -show" command run on lunash:> prompt on Luna HSM shows Activation status as "no"
UNCONFIRMED: SafeNet command "hsm show" run on Lunash prompt on Luna SA shows "MofN activation status" as "Deactivated"
Cause
Resolution
service tomcat restart
Access to /KMS should now be successful.
In keyManagerServer.properties, make sure that provider.slot is set to the correct slot for your environment. This is located in /opt/KMS/conf/properties. If you need to change it, restart Tomcat for the change to take effect.
Workaround
Related Articles
After successful Account data collection, Custom Account Integer Attribute value is not displaying under Accounts tab in R… 21Number of Views Successful SSH login attempts are not logged in /var/log/messages in Authentication Manager prior to 8.4 39Number of Views Unable to make a successful Web Service API createChangeRequest call from a Workflow in RSA Identity Governance & Lifecycle 168Number of Views Microsoft Azure Active Directory - Third-Party IdP Integration - RSA Ready Implementation Guide 193Number of Views AFX Server on Windows fails to stop/start after initial successful start in RSA Governance & Lifecycle 153Number of Views
Trending Articles
How to Download OTP Token Seed Files from myRSA RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Release Notes for RSA Authentication Manager 8.8
Don't see what you're looking for?