启动zookeeper报错Error contacting service. It is probably not running解决

最新推荐文章于 2022-08-26 01:48:34 发布
最新推荐文章于 2022-08-26 01:48:34 发布
阅读量341 收藏
点赞数
分类专栏： java 文章标签： zookeeper java linux
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_44053632/article/details/108405699
版权

搭建zookeeper集群，发现启动失败

[root@localhost bin]# zkServer.sh status
JMX enabled by default
Using config: /opt/apps/zookeeper-3.4.6/bin/../conf/zoo.cfg
Error contacting service. It is probably not running.
[root@localhost bin]# zkServer.sh start
JMX enabled by default
Using config: /opt/apps/zookeeper-3.4.6/bin/../conf/zoo.cfg
Starting zookeeper ... already running as process 7180.

查看日志：显示如下信息

2020-09-04 15:30:47,113 [myid:1] - ERROR [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:Learner@230] - Unexpected exception
java.net.NoRouteToHostException: 没有到主机的路由 (Host unreachable)
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at org.apache.zookeeper.server.quorum.Learner.connectToLeader(Learner.java:225)
	at org.apache.zookeeper.server.quorum.Follower.followLeader(Follower.java:71)
	at org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:786)
2020-09-04 15:30:47,113 [myid:1] - WARN  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:Follower@89] - Exception when following the leader
java.net.NoRouteToHostException: 没有到主机的路由 (Host unreachable)
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at org.apache.zookeeper.server.quorum.Learner.connectToLeader(Learner.java:225)
	at org.apache.zookeeper.server.quorum.Follower.followLeader(Follower.java:71)
	at org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:786)
2020-09-04 15:30:47,114 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:Follower@166] - shutdown called
java.lang.Exception: shutdown Follower
	at org.apache.zookeeper.server.quorum.Follower.shutdown(Follower.java:166)
	at org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:790)
2020-09-04 15:30:47,114 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FollowerZooKeeperServer@139] - Shutting down
2020-09-04 15:30:47,114 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:ZooKeeperServer@441] - shutting down
2020-09-04 15:30:47,115 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumPeer@714] - LOOKING
2020-09-04 15:30:47,117 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@815] - New election. My id =  1, proposed zxid=0x0
2020-09-04 15:30:47,117 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 1 (n.leader), 0x0 (n.zxid), 0x68 (n.round), LOOKING (n.state), 1 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:30:47,122 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 2 (n.leader), 0x0 (n.zxid), 0x67 (n.round), LEADING (n.state), 2 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:30:47,122 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 3 (n.leader), 0x0 (n.zxid), 0x67 (n.round), LEADING (n.state), 3 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:30:47,323 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@849] - Notification time out: 400
2020-09-04 15:30:47,323 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 1 (n.leader), 0x0 (n.zxid), 0x68 (n.round), LOOKING (n.state), 1 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:30:47,326 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 3 (n.leader), 0x0 (n.zxid), 0x67 (n.round), LEADING (n.state), 3 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:30:47,326 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 2 (n.leader), 0x0 (n.zxid), 0x67 (n.round), LEADING (n.state), 2 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:30:47,727 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@849] - Notification time out: 800
2020-09-04 15:30:47,727 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 1 (n.leader), 0x0 (n.zxid), 0x68 (n.round), LOOKING (n.state), 1 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:30:47,728 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 3 (n.leader), 0x0 (n.zxid), 0x67 (n.round), LEADING (n.state), 3 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:30:47,728 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 2 (n.leader), 0x0 (n.zxid), 0x67 (n.round), LEADING (n.state), 2 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:30:48,528 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@849] - Notification time out: 1600
2020-09-04 15:30:48,529 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 1 (n.leader), 0x0 (n.zxid), 0x68 (n.round), LOOKING (n.state), 1 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:30:48,533 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 3 (n.leader), 0x0 (n.zxid), 0x67 (n.round), LEADING (n.state), 3 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:30:48,533 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 2 (n.leader), 0x0 (n.zxid), 0x67 (n.round), LEADING (n.state), 2 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:30:50,134 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@849] - Notification time out: 3200
2020-09-04 15:30:50,135 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 1 (n.leader), 0x0 (n.zxid), 0x68 (n.round), LOOKING (n.state), 1 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:30:50,138 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 3 (n.leader), 0x0 (n.zxid), 0x67 (n.round), LEADING (n.state), 3 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:30:50,140 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 2 (n.leader), 0x0 (n.zxid), 0x67 (n.round), LEADING (n.state), 2 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:30:53,341 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@849] - Notification time out: 6400
2020-09-04 15:30:53,341 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 1 (n.leader), 0x0 (n.zxid), 0x68 (n.round), LOOKING (n.state), 1 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:30:53,342 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 2 (n.leader), 0x0 (n.zxid), 0x67 (n.round), LEADING (n.state), 2 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:30:53,342 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 3 (n.leader), 0x0 (n.zxid), 0x67 (n.round), LEADING (n.state), 3 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:30:57,278 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 2 (n.leader), 0x0 (n.zxid), 0x68 (n.round), LOOKING (n.state), 2 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:30:57,278 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 2 (n.leader), 0x0 (n.zxid), 0x68 (n.round), LOOKING (n.state), 1 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:30:57,279 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 3 (n.leader), 0x0 (n.zxid), 0x67 (n.round), LEADING (n.state), 3 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:31:03,112 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 3 (n.leader), 0x0 (n.zxid), 0x68 (n.round), LOOKING (n.state), 3 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:31:03,114 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 3 (n.leader), 0x0 (n.zxid), 0x68 (n.round), LOOKING (n.state), 1 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:31:03,115 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@597] - Notification: 1 (message format version), 2 (n.leader), 0x0 (n.zxid), 0x68 (n.round), LEADING (n.state), 2 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2020-09-04 15:31:03,315 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumPeer@784] - FOLLOWING
2020-09-04 15:31:03,315 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:ZooKeeperServer@162] - Created server with tickTime 2000 minSessionTimeout 4000 maxSessionTimeout 40000 datadir /var/cyj/zookeeper/datalog/version-2 snapdir /opt/apps/zookeeper-3.4.6/data/version-2
2020-09-04 15:31:03,315 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:Follower@63] - FOLLOWING - LEADER ELECTION TOOK - 16200
2020-09-04 15:31:03,316 [myid:1] - WARN  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:Learner@233] - Unexpected exception, tries=0, connecting to node3/192.168.247.33:2881

如上显示2181端口被关闭，所以可能被占用了

  • 查看该端口
    在这里插入图片描述
  • 关闭端口
    在这里插入图片描述
  • 重新启动，成功！
    在这里插入图片描述
程程程程yyyy
关注
专栏目录
zookeeper启动后服务验证报错：Error contacting service. It is probably not running.
hair请的的博客
10-23 1053
目录 报错内容 报错原因 解决方案 报错内容 ZooKeeper JMX enabled by default Using config: /opt/zookeeper/bin/../conf/zoo.cfg Error contacting service. It is probably not running. 报错原因 防火墙未关 解决方案 依次输入以下命令关闭防火墙 systemctl stop firewalld systemctl disable firewalld
Zookeeper启动显示成功，zkServer.sh status报错：Error contacting service. It is probably not running.
weixin_54348877的博客
10-19 8381
目录 1. 检查防火墙是否关闭 2. 确认每台主机是否都启动Zookeeper 3. 检查zookeeper安装目录下zoo.cfg文件 4.检查myid文件内容是否一致 5. 检查环境配置是否出错 6.检查是否使环境变量生效 问题描述： 问题分析： 1. 检查防火墙是否关闭 CentOS6.8、虚拟机防火墙开启、关闭、重启、查询命令_连胜是我偶像的博客-CSDN博客 2. 确认每台主机是否都启动Zookeeper 涉及到Leader（Master）选举的问题，需要先启动m...
Error contacting service. It is probably not running 错误
freeman983
04-23 167
安装Zookeeper 3.4.6 启动节点 调用sh zkServer.sh status 遇到这个问题。百度，google了后发现有人是修改sh脚本里的一个nc的参数来解决，可在3.4.6的sh文件里并没有找到nc的调用。 最后 tailf zookeeper.out 才知道是因为配置文档里指定的log目录没有创建导致出错，手动增加目录后重启，问题解决。 ...
zookeeper启动提示Error contacting service. It is probably not running.
二次源的博客
03-30 227
排查思路： 查看配置文件zoo.cfg是否配错。 检查环境变量是否添加 检查时间是否正确 查看日志排查其他错误
解决zppkeeper报错：Error contacting service. It is probably not running.
qq_37135484的博客
03-06 904
错误详情： 解决： 进入到你配置的dataDIR目录下 找到zookeeper_server.pid: 删除zookeeper_server.pid后重新启动:
zookeeper，解决状态显示报错：Error contacting service. It is probably not running
求人不如求己
03-20 670
就是没有启动成功 在zookeeper的bin目录下，比如：/zookeeper-3.4.6/bin使用命令 ./zkServer.sh start 查看状态 ./zkServer.sh status 注意如果还是出现这个问题，建议直接找到 conf/zoo.conf文件中的dataDir所指向的目录，删除如下zookeeper_server.pid的文件，再次启动即可。...
zookeeper 执行./zkServer.sh status，报错：Error contacting service. It is probably not running.
BlackCast的博客
11-21 1952
在linux系统中，centos 6.7中 zookeeper 3.5.6 启动失败： 在zookeeper的bin目录中，执行./zkServer.sh start，能显示已经STARTED。 但是执行./zkServer.sh status，报错：Error contacting service. It is probably not running. 看不到，zookeeper的启动状态：standalone。 执行jps命令，也没显示，zookeeper的进程：QuorumPeerMain
zookeeper启动失败，显示：Error contacting service. It is probably not running.
正文~博客
08-26 1005
Error contacting service. It is probably not running.
zookeeper 启动错误Error contacting service. It is probably not running
也许是我送你哦
05-14 1201
./zkServer.sh start 启动kafka后 [root@localhost bin]# ./zkServer.sh start /data/jdk/jdk1.8.0_261/bin/java ZooKeeper JMX enabled by default Using config: /data/zk/zookeeper/bin/../conf/zoo.cfg Starting zookeeper ... STARTED 查看kafka的状态 [root@localhost bin]# .
解决 Zookeeper集群启动失败，提示 Error contacting service. It is probably not running.
一名准程序员
08-10 1996
刚学到zookeeper 记录一下出现的错误，死活开启不了服务，经查阅后发现是防火墙问题。（关闭防火墙命令在文章底部） 如果设置了SSH免密登录 则在zoo.cig中如下设置; 如果没有设置ssh免密登录，把“=”后面设置为IP:通信端口号:选举端口号即可(文章底部有一个连接，搭建集群的方式是IP的方式) [root@slave2 zookeeper-3.4.14]# vim co...
[ZooKeeper]启动失败zkServer.sh status:Error contacting service. It is probably not running
Balmunc的专栏
07-20 862
运行zkServer.sh status 查看zookeeper.out 在192.168.16.212这台机关掉防火墙
在配置zookeeper集群的时候提示Error contacting service. It is probably not running.
ILovePythonhao的博客
07-08 282
在配置zookeeper集群的时候，我使用的是三台机器，首先进入conf文件中使用 vim zoo.cfg 进去配置文件,修改数据文件的位置为 dataDir=/home/hao/Pictures/zookeeper-3.4.14/my_zoo_data 然后添加集群信息 server.1=node1:2888:3888 server.2=node2:2888:3888 server.3=node3:2888:3888 然后进入my_zoo_data文件当中使用 vim myid 然后在里面添加se
zookeeper部署报错 Error contacting service. It is probably not running.
whiteGu的博客
11-26 417
原因是因为，在zookeeper的data文件夹里面没有添加myid文件；分别添加下面配置即可 第一步：在conf文件夹里面的zoo.cfg里面添加 server.A=B:C:D(例如：server.1=你的IP地址:2888:3888); 第二步：在data文件夹里面添加myid文件 然后解决问题； server.A=B:C:D：其中 A 是一个数字，表示这个是第几号服务器；B 是这个服务 ...
ZK的Error contacting service. It is probably not running问题
csdn_halon的博客
10-11 829
记录测试的时候遇到了一个bug 发起请求后返回502 bad gateway（nginx/1.1.19）查看到nginx正常启动后查看后端的日志发现了报错 java.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:7
Error contacting service. It is probably not running.//zkServer.sh start报错解决
dj_hanhan的博客
06-02 403
zkServer.sh start可以正常启动，jps可以查看到QuorumPeerMain进程 [root@masternode1 conf]# jps 16500 Jps 16349 QuorumPeerMain 报错信息： [root@masternode1 conf]# /usr/zookeeper-3.4.6/bin/zkServer.sh status JMX enabled by default Using config: /usr/zookeeper-3.4.6/bin/../conf/z
【已解决】zookeeper显示Error contacting service. It is probably not running等问题
热门推荐
一只程序猿的修炼之旅
11-17 3万+
博主在安装hadoop时，为实现高可用(high-available )，使用zookeeper 3.4.6，出现了一些小插曲，报错(Error contacting service. It is probably not running)经历一番折腾，最终完美解决。 下面提示几个配置zookeeper容易入坑的点: 一、zoo.cfg配置文件(文件位置在zookeeper根目录下的conf里) ...
【Zookeeper 启动失败】zkServer.sh status Error contacting service. It is probably not running.
weixin_38118900的博客
03-17 751
启动后查看状态如下 查看日志 程序所在目录下的 logs/zookeeper.out 2020-03-17 16:07:04,542 [myid:1] - INFO [WorkerReceiver[myid=1]:FastLeaderElection@600] - Notification: 1 (message format version), 1 (n.leader), 0x...
linux系统下zookeeper的启动异常：Error contacting service. It is probably not running.
javaboy
12-05 1051
原来异常信息： 网上对于这个异常的解答众说纷纭，现在总结一下我的解决方案： 因为我用的zookeeper的版本是zookeeper-3.4.6，然后我原来的jdk用的是jdk-8u191-linux-x64.tar.gz，我卸载之后重新安装了一个jdk,这次的版本是jdk-7u79-linux-x64.tar.gz,问题解决。 现在重新启动zookeeper之后： Ok,问题解决！...
zookeeper 集群异常：Error contacting service. It is probably not running.
在路上。。。
12-12 773
zookeeper 集群异常 :Error contacting service. It is probably not running
启动Zookeeper报错:Error contacting service. It is probably not running.
最新发布
12-25
It is probably not running."通常有两种可能的原因： 1. 端口被占用：可以使用netstat命令查看端口号的占用情况，找到占用Zookeeper端口的进程并停止它。 2. IP地址不是本机网卡：需要让服务器监听所有网卡的IP...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值