KMA 2.3.1: Reporting Key Not Found And SOAP Errors

Asset ID:	1-72-1550594.1
Update Date:	2017-05-17
Keywords:

Solution Type Problem Resolution Sure

Solution 1550594.1 : KMA 2.3.1: Reporting Key Not Found And SOAP Errors

Applies to:

Oracle Key Manager - Version 2.0.0 to 2.5.2 [Release 2.0]
Information in this document applies to any platform.
Older KMA cluster with two nodes. Added another node recently.
First two nodes management networks are 100Mbytes/half duplex, service networks are 1000Mbytes/full duplex.
Third node, management network is at 1000Mbytes/full duplex, service network at 100Mbytes/full duplex

Symptoms

SOAP errors and "Key not found" errors coming from KMA3. KMA1 and KMA2 are getting SOAP errors.

Lots of "close_waits" in the netstat.txt file from KMA3 and there are 13,667 keys less on KMA3

than in the cluster. Replication is not completing properly on KMA3.

Changes

Third node added recently that was running with management network at 1000Mbyte/full duplex. Service network running at 100Mbytes/full duplex

Cause

Network configuration issues.

Solution

1. Make sure the management ports on all nodes are running at the same speed and duplex mode

to ensure proper communication between cluster nodes on the network.

2. Make sure the service ports are all running at the same speed, as well.

3. Check port status via the /var/adm/messages on the KMA's and have customers verify that

their switch ports are set to auto/auto and are of the same speed.

References

<NOTE:1447111.2> - Information Center: Oracle Key Manager (KMS/OKM) Overview Advisor

Attachments

This solution has no attachment