zookeeper遇见错误总结

来源：互联网发布：赖昌星红楼知乎编辑：程序博客网时间：2024/04/30 08:21

我发现初学者搭建zookeeper的出错率比hadoop还要高。端口冲突等问题。下面是我的排除经历。

首先，selinux必须禁掉，防火墙必须把规则清空后，禁掉。这东西如果你不懂还不禁肯定会出现七七八八你解决不了的问题。

[root@sict61 bin]# ./zkServer.sh startZooKeeper JMX enabled by defaultUsing config: /root/zookeeper-3.4.8/bin/../conf/zoo.cfgStarting zookeeper ... STARTED[root@sict61 bin]# ./zkServer.sh statusZooKeeper JMX enabled by defaultUsing config: /root/zookeeper-3.4.8/bin/../conf/zoo.cfgError contacting service. It is probably not running.

zookeeper可以这样启动，（当然也可以看日志，我认为看日志麻烦）
#./zkServer.sh start-foreground
然后就出现这样的错误

2016-07-17 19:24:59,809 [myid:1] - INFO [main:QuorumPeerMain@127] - Starting quorum peer2016-07-17 19:24:59,821 [myid:1] - INFO  [main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:21812016-07-17 19:24:59,822 [myid:1] - ERROR [main:QuorumPeerMain@89] - Unexpected exception, exiting abnormallyjava.net.BindException: Address already in use

端口占用？我看看
[root@sict61 bin]# netstat -anp|grep 2181
tcp 0 0 :::2181 :::* LISTEN 7990/java

什么情况！！选端口最烦人了！！我推荐一个方法，推荐端口号后面填零。这里必须提出，一定要探查
2181，2888，3888，网络上配置教程的推荐端口。不行就换。
说下zookeeper节点间启动是平等的。

OK

[root@sict61 bin]# ./zkServer.sh statusZooKeeper JMX enabled by defaultUsing config: /root/zookeeper-3.4.8/bin/../conf/zoo.cfgMode: leader[root@sict64 bin]# ./zkServer.sh statusZooKeeper JMX enabled by defaultUsing config: /root/zookeeper-3.4.8/bin/../conf/zoo.cfgMode: followeroot@sict71 bin]# ./zkServer.sh statusZooKeeper JMX enabled by defaultUsing config: /root/zookeeper-3.4.8/bin/../conf/zoo.cfgMode: follower

0 0