OKM - Cannot connect to the OKM Manager GUI; getting "Retrieve security parameters failed. Error: timeout"

Asset ID:	1-72-1627775.1
Update Date:	2014-03-17
Keywords:

Solution Type Problem Resolution Sure

Solution 1627775.1 : OKM - Cannot connect to the OKM Manager GUI; getting "Retrieve security parameters failed. Error: timeout"

Applies to:

Oracle Key Manager - Version 2.4 to 3.0 [Release 2.0 to 3.0]
Information in this document applies to any platform.

Symptoms

"Retrieve security parameters failed. Error: timeout" error when logging on to the GUI of KMA2
Both Security Officer and Operator users cannot connect. He tried Launch Redirection as Security Officer and he was able to bring up the OKM Console
He can ping the management port.

This is OKM 2.4.1

"Server Busy" messages from Audit log of KMA1:
----------------------------------------------------------

7FDDBC66C96D8E6E00000000007E3048 7FDDBC66C96D8E6E kma1 Cluster Operations Medium Term Retention Request Anti-Entropy Push From Peer Server Busy Warning 000094000012 2014-02-14 06:12:05.788714+00 kma2 172.18.18.12 Peer KMA ID = BFCA9B09661FDB47, Peer KMA Name = kma2, Peer KMA Network Address = 172.18.18.12 Server will retry the operation. If the problem persists, then reboot the KMA.

"Server Busy" message from Audit log of KMA 2 with Reason = SetPeerLastKnownTimestampVector:
-----------------------------------------------------------------------------------------------------------------------------------

BFCA9B09661FDB4700000000007EEA7E BFCA9B09661FDB47 kma2 Cluster Operations Medium Term Retention Push Updates to Peer Server Busy Warning 000093000012 2014-02-14 02:19:55.928387+00 kma1 172.18.18.11 Peer KMA ID = 7FDDBC66C96D8E6E, Anti-Entropy Push = TRUE, Reason = SetPeerLastKnownTimestampVector Server will retry the operation. If the problem persists, then reboot the KMA.
BFCA9B09661FDB4700000000007EEA7D BFCA9B09661FDB47 kma2 Replication Operations Short Term Retention Request Anti-Entropy Push From Cluster Peer Success Success 000101000000 2014-02-14 02:19:55.854386+00 kma1 172.18.18.31 KMA ID = 7FDDBC66C96D8E6E, Expected Peer KMA ID = BFCA9B09661FDB47 No recommended action

Changes

No known changes

Cause

Postgres could not serialize access due to concurrent update.
Possible race condition.

See Bug 17652160 : SERVER BUSY / POSTGRESQL COULD NOT SERIALIZE ACCESS DUE TO CONCURRENT UPDATE

Solution

OKM GUI login fails with "Retrieve security parameters failed. Error: timeout" error.

Workaround:

Log in to the GUI using both Security Officer and Operator user profiles.
If logon using a different user profile succeeds,
    the issue could be because the User ID being used to log on is blocked because the number of login retries has been exceeded.
    ( Refer to Cannot connect to any of the KMAs via the OKM gui - message is "Connect failed;Error access denied" (Doc ID 1570158.1)

If logon fails for all users, launch the OKM console from the ELOM or ILOM.
    If the Security Officer or Operator user can bring up the OKM console, try rebooting the KMA from the OKM Console.
    When the system restarts, try logging in again to connect to the OKM GUI.

If rebooting fails to resolve the issue, open a service request in MyOracle Support. Attach an OKM system dump to the service request.
The system dump can be generated from another KMA in the cluster.

Note: This problem has been reported to engineering and is being fixed.

Attachments

This solution has no attachment