Siebel Application Server Services Not Starting Up After Gateway Cluster Deployment With 3 Nodes "SBL-GEN-05013: Invalid parameter" And "TLSListener port is null or Empty"
(Doc ID 2889228.1)
Last updated on FEBRUARY 21, 2024
Applies to:
Siebel CRM - Version 22.3 and laterInformation in this document applies to any platform.
Symptoms
On : 22.3 version, System Admin
Siebel server service does not come up after gateway cluster deployment with 3 node cluster.
Successfully able to deploy gateway clustering with 3 nodes according to the SMC and everything was working. After the servers were restarted and after the restart, the Siebel services does not come up.
Siebsrvr.log file:
NameServerLayerLog Debug 5 0000000262f01ef8:0 2022-08-08 08:45:13 10228: CSSNSClient::Lock(), lockTime:0.001500, m_nLocks:1, m_tid:10228
GenericLog GenericError 1 0000000262f01ef8:0 2022-08-08 08:45:13 (listener.cpp (286) err=5013 sys=0) SBL-GEN-05013: Invalid parameter ((null)).
GenericLog GenericError 1 0000000262f01ef8:0 2022-08-08 08:45:13 (lstnsvc.cpp (154) err=5013 sys=0) SBL-GEN-05013: Invalid parameter (?).
GenericLog GenericError 1 0000000262f01ef8:0 2022-08-08 08:45:13 (scfsis.cpp (276) err=1310725 sys=0) SBL-SVR-00005: Stale or invalid Task handle
ScfEventLog SubEvtFacFatal 0 0000000262f01ef8:0 2022-08-08 08:45:13 scfEventFac::s_pEvtFacLock is NULL and hence SCF event facility cannot be initialised
GenericLog GenericError 1 0000000262f01ef8:0 2022-08-08 08:45:13 (scfeventfac.cpp (3818) err=1319869 sys=0) SBL-SVR-09149: Could not initialize the event facility.
Node3 Cloudgateway.log
[ERROR] 2022-08-04 16:37:41.185 [Thread-5] CG_LOGGER - com.siebel.opcgw.cloudgateway.config.SrvDeploymentThread: Exception occurred in Server Deployment Threadnull
[ERROR] 2022-08-04 16:37:41.185 [Thread-5] CG_LOGGER - com.siebel.opcgw.cloudgateway.config.SrvDeploymentThread:
java.io.IOException: null
at com.siebel.opcgw.cloudgateway.config.SrvDeploymentThread.run(SrvDeploymentThread.java:106) [opcgw.jar:?]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_311]
[ERROR] 2022-08-05 08:49:06.602 [main] CG_LOGGER - com.siebel.opcgw.cloudgateway.CGServletContext: Error ocurred while starting tls service on Gateway: TLSListener port is null or Empty
Primary Node1 cloudgateway.log:
[ERROR] 2022-08-08 08:37:46.038 [https-openssl-nio-8443-exec-10] CG_LOGGER - com.siebel.opcgw.cloudgateway.GatewayAuthenticationFilter: Ensure registry service is up and running.
[ERROR] 2022-08-08 08:37:46.038 [https-openssl-nio-8443-exec-10] CG_LOGGER - com.siebel.opcgw.cloudgateway.GatewayAuthenticationFilter: null
[ERROR] 2022-08-08 08:37:57.851 [Thread-15] CG_LOGGER - com.siebel.opcgw.cloudgateway.CGReqService: Authentication failed for user SADMIN
The issue can be reproduced at will with the following steps:
1. Log in to SMC and create a gateway cluster profile
2. Deploy gateway clustering with 3 nodes and Submit. Deployment successful
3. Validated application services and all looks good.
4. Restart the whole enterprise for validation
5. Application services not starting and srvrmgr not working
Changes
Trying to deploy Gateway clustering with 3 nodes
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 |
| Changes |
| Cause |
| Solution |
| References |