cos-boot - ZooKeeperServer fails to start on clientPort due to java.lang.NullPointerException or java.io.IOException: Bad file descriptor
(Doc ID 2043605.1)
Last updated on AUGUST 15, 2022
Applies to:
Oracle WebCenter Sites - Version 7.6.2 to 7.6.2 [Release FatWire]Information in this document applies to any platform.
Symptoms
Normally when ZooKeeperServer is successfully started, in cos-boot.log, you will see messages like these:
Changes
User might have manually modified the dataDir used by zookeeper, and caused corruption with the files inside dataDir. Or, if there was a FS issue with where dataDir is located.
NOTE: clientPort and dataDir are defined in cos-boot/WEB-INF/classes/zoo.properties. By default dataDir is set to {COS_HOME}/data.
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 |