My Oracle Support Banner

Changing The Primary Node Of A Siebel Gateway Cluster In Siebel Management Console Fails With "Failed to set <hostname> as primary node." (Doc ID 3037391.1)

Last updated on JULY 31, 2024

Applies to:

Siebel CRM - Version 17.0 [IP2017] and later
Information in this document applies to any platform.

Symptoms


When attempting to change the Primary Gateway node ,the following error occurs:

"Failed to set <hostname> as primary node.
Refer logs of <hostname> node for details."

cloudgateway.log in the affected nodes captured the following:

[DEBUG] 2024-06-20 13:55:54.541 [https-jsse-nio-8001-exec-2] CG_LOGGER - com.siebel.opcgw.cloudgateway.config.GatewayClusterResource: Begin: POST on setprimaryservicenode.
[DEBUG] 2024-06-20 13:55:54.561 [https-jsse-nio-8001-exec-2] CG_LOGGER - com.siebel.opcgw.cloudgateway.config.GatewayClusterResource: Attempting properties file update at <hostname1>:<HTTPS_PORT>
[WARN ] 2024-06-20 13:55:54.759 [https-jsse-nio-8001-exec-2] CG_LOGGER - com.siebel.opcgw.cloudgateway.config.GatewayClusterResource: Warning: Unable to update properties file at <hostname1>:<HTTPS_PORT>
[DEBUG] 2024-06-20 13:55:54.759 [https-jsse-nio-8001-exec-2] CG_LOGGER - com.siebel.opcgw.cloudgateway.config.GatewayClusterResource: Attempting properties file update at <hostname2>:<HTTPS_PORT>
[ERROR] 2024-06-20 13:55:54.797 [https-jsse-nio-8001-exec-2] CG_LOGGER - com.siebel.opcgw.cloudgateway.config.GatewayClusterResource: Error occurred during update properties file at <hostname2>:<HTTPS_PORT>
[ERROR] 2024-06-20 13:55:54.797 [https-jsse-nio-8001-exec-2] CG_LOGGER - com.siebel.opcgw.cloudgateway.config.GatewayClusterResource: Change primary service node operation failed. Retry after correcting errors.
[DEBUG] 2024-06-20 13:55:54.797 [https-jsse-nio-8001-exec-2] CG_LOGGER - com.siebel.opcgw.cloudgateway.config.GatewayClusterResource: End: POST on setprimaryservicenode.

 
Steps to reproduce the issue

The issue can be reproduced at will with the following steps:
1. Install and deploy the latest Siebel release.
2. Configure and deploy a Siebel Gateway Cluster.
3. Access the Siebel Management Console (SMC).
4. Navigate to "Deployments" -> "Cluster" and select the node that is required as primary.
5. Click on the "Set As Primary" button in SMC and notice the error.




Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.