000022769 - Error: 'An unknown or uninitialized lock manager attempted to establish a connection' appears in ACE/Server logs

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 Number000022769
Applies ToRSA ACE/Server 5.2.1
Sun Solaris 2.8
IssueError: "An unknown or uninitialized lock manager attempted to establish a connection" appears in ACE/Server logs
Error: "Modification to the token record have simultaneously occurred on separate servers" appears in ACE/Server logs
Error: "Replica unable to correct clock" appears in ACE/Server logs
Both RSA ACE/Server Primary and Replica accept the authentication request and send back the authentication result to the client
CauseTime on the replica was 30 seconds off the time on the primary
ResolutionTo correct this issue, remove NTP time synchronization from the Replica, or make sure all RSA Servers are getting their time from known-good NTP servers based on a single known-good source. . Follow the solution regarding Error: "Warning: Cannot set replica clock" in RSA ACE/Server to make the Primary synchronize the time on the Replica.
Legacy Article IDa30277

Attachments

    Outcomes