Unable To Start Siebel Server Service After Power Outage: Zookeeper EOF excepton java.io.EOFException: Failed to read
(Doc ID 2922113.1)
Last updated on JUNE 26, 2024
Applies to:
Siebel CRM - Version 17.0 [IP2017] and laterInformation in this document applies to any platform.
Symptoms
The Siebel Server would not start after a power outage.
The following errors were observed when the Siebel Server did not start.
SiebSrvr.log Errors
-----------------------
GenericLog GenericError 1 0000000263c43b30:0 2023-01-15 20:03:34 Register Service failed : NSGetZKConnectFromCG failed
GtwySvcFrmwrkLog Error 1 0000000263c43b30:0 2023-01-15 20:03:34 Invalid inputs provided to intiate the Registry Connection
GtwySvcFrmwrkLog Error 1 0000000263c43b30:0 2023-01-15 20:03:34 Connection to Registry failed
GtwySvcFrmwrkLog Error 1 0000000263c43b30:0 2023-01-15 20:03:34 ServiceDiscovery Exception : Registry Not Available
GtwySvcFrmwrkLog Error 1 0000000263c43b30:0 2023-01-15 20:03:34 Service Discovery Intialisation Failed : Registry Generic Exception
SisnTcpIp SisnSockError 1 0000000263c43b30:0 2023-01-15 20:04:04 1: [SISNAPI TLS] failed to read PARAM_GENERIC_ENABLE_OPENSSL parameter
NameServerLayerLog Error 1 0000000263c43b30:0 2023-01-15 20:04:04 1: [cgclientservice] TLS handshake to gateway failed gateway:registry_port
GenericLog GenericError 1 0000000263c43b30:0 2023-01-15 20:04:04 Register Service failed : NSGetZKConnectFromCG failed
GtwySvcFrmwrkLog Error 1 0000000263c43b30:0 2023-01-15 20:04:04 Invalid inputs provided to intiate the Registry Connection
GtwySvcFrmwrkLog Error 1 0000000263c43b30:0 2023-01-15 20:04:04 Connection to Registry failed
GtwySvcFrmwrkLog Error 1 0000000263c43b30:0 2023-01-15 20:04:04 ServiceDiscovery Exception : Registry Not Available
GtwySvcFrmwrkLog Error 1 0000000263c43b30:0 2023-01-15 20:04:04 Service Discovery Intialisation Failed : Registry Generic Exception"
Additional logging for Zookeeper server logs were enabled for troubleshooting.
The following DEBUG messages were observed.
zookeeper_roll_server.log
---------------------------------
2023-01-15 20:03:57,686 [myid:] - DEBUG [main:FileTxnLog$FileTxnIterator@641] - EOF excepton java.io.EOFException: Failed to read /siebel/gtwysrvr/zookeeper/version-2/log.c117
2023-01-15 20:03:57,690 [myid:] - DEBUG [main:FileTxnLog$FileTxnIterator@641] - EOF excepton java.io.EOFException: Failed to read /siebel/gtwysrvr/zookeeper/version-2/log.c1fd
STEPS
-----------------------
1. Install Siebel.
2. Startup Siebel.
3. Observe a Power Outage occurred in the Siebel environment while Siebel was running.
4. Restart Siebel after the Power Outage.
5. Observe the Siebel Server does not start up.
Changes
Customer experienced a Power Outage affecting the Siebel application.
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 |