Secure Global Desktop Array Configured With Secure Intra-Array Communication Enabled Shows Inconsistent Status Results from the Command Line and Administration Console And Secondaries Will Not Join
Last updated on AUGUST 26, 2016
Applies to:Oracle Secure Global Desktop - Version 4.61 and later
Information in this document applies to any platform.
When a Secure Global Desktop (SGD) array is created with Secure Intra-Array Communication enabled, it is found that that the tarantella status command may report that some secondaries are "not accepting connections" from all servers. Meanwhile, when viewed from the Administration Console (AC), these same nodes may show correctly as "Up". During this period, users can login to all the servers.
If a secondary is detached from the array, the reverse is seen on that server i.e "tarantella status" says the server is up but the AC says it's down.
In addition, if an attempt is made to join a secondary to the array, it will fail with a message stating that the primary server is unreachable.
# <SGD-DIR>/bin/tarantella array join --primary <primary> --secondary <secondary> --verbose
WHERE <primary> is the Fully Qualified Domain Name of the Primary
<secondary> is the Fully Qualified Domain Name of the secondary
In the ouput, the following error is seen:
2011/10/13 18:05:08.382 (pid 0) admin/misc/moreinfo #1318529108382
Failed to contact host sgd-host.vdihost.net because of javax.naming.CommunicationException: failed to connect [Root exception is javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty]
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms