Zookeeper start error
When you start zookeeper, JPS finds that there is no quorum peermain
Then go to zookeeper to check the log, and find the startup error
It indicates that port 8080 is not generated when starting
#Check if the port is occupied
netstat -natp | grep 8080
#Kill him when he finds out he’s occupied
kill -9 4944
Then restart zookeeper
bin/zkServer.sh start
jps
Read More:
- The first installation of zookeeper on Linux failed to start
- Solve the problem of unable to start under zookeeper Linux
- Zookeeper Failed to Start Error: start failed [How to Solve]
- Error in starting zookeeper in Windows: zookeeper audit is disabled
- Starting zookeeper to report an error already running as process
- Installing zookeeper under Linux system
- Docker install zookeeper 3.6.2
- Zookeeper starts the client and reports an error: java.net.connectexception: connection rejected
- Starting zookeeper… Already running as process 1949
- Zookeeper will not attempt to authenticate using SASL (unknown error)
- zookeeper_ An error is reported when the exporter starts
- Java connection zookeeper high availability hive error
- zookeeper Failed to Startup: Error: JAVA_HOME is not set and java could not be found in PATH
- Error when Java uses API to operate zookeeper
- Zookeeper connection timeout problem, and refused to connect to solve the problem
- Tdengine failed to start, start request repeated too quickly for taosd.service
- Net start mongodb failed to start: system error 5 has occurred. Access is denied
- Error: (serious: a child container failed during start) (server component failed to start so Tomcat is unable)
- Solve net start mysql, start MySQL service, prompt system error 5. Access denied.
- Docker start error: failed to start docker application container engine.