zookeeper启动失败，显示：Error contacting service. It is probably not running.

最新推荐文章于 2023-05-30 19:49:07 发布

TRIERR

最新推荐文章于 2023-05-30 19:49:07 发布

阅读量989

点赞数

文章标签： zookeeper

本文链接：https://blog.csdn.net/weixin_44725007/article/details/126535411

版权

本文档介绍了当遇到Zookeeper启动失败并显示'Error contacting service. It is probably not running.'错误时的解决方法。关键在于检查日志，并发现端口冲突问题。通过修改zoo.cfg配置文件中的端口号，将默认的8080改为其他可用端口，问题得以解决。提醒读者，类似错误应具体分析日志以找到相应解决方案。

摘要由CSDN通过智能技术生成

zookeeper启动失败

[root@localhost bin]# ./zkServer.sh start
ZooKeeper JMX enabled by default
Using config: /opt/zookeeper/bin/../conf/zoo.cfg
Starting zookeeper ... STARTED
[root@localhost bin]# ./zkServer.sh status
ZooKeeper JMX enabled by default
Using config: /opt/zookeeper/bin/../conf/zoo.cfg
Client port found: 2181. Client address: localhost.
Error contacting service. It is probably not running.

解决方法：./zkServer.sh start-foreground

 
[root@localhost bin]# ./zkServer.sh start-foreground
ZooKeeper JMX enabled by default
Using config: /opt/zookeeper/bin/../conf/zoo.cfg
2022-08-25 07:57:06,809 [myid:] - INFO  [main:QuorumPeerConfig@173] - Reading configuration from: /opt/zookeeper/bin/../conf/zoo.cfg
2022-08-25 07:57:06,826 [myid:] - INFO  [main:QuorumPeerConfig@459] - clientPortAddress is 0.0.0.0:2181
2022-08-25 07:57:06,826 [myid:] - INFO  [main:QuorumPeerConfig@463] - secureClientPort is not set
2022-08-25 07:57:06,826 [myid:] - INFO  [main:QuorumPeerConfig@479] - observerMasterPort is not set
2022-08-25 07:57:06,826 [myid:] - INFO  [main:QuorumPeerConfig@496] - metricsProvider.className is org.apache.zookeeper.metrics.impl.DefaultMetricsProvider
2022-08-25 07:57:06,830 [myid:1] - INFO  [main:DatadirCleanupManager@78] - autopurge.snapRetainCount set to 3
2022-08-25 07:57:06,830 [myid:1] - INFO  [main:DatadirCleanupManager@79] - autopurge.purgeInterval set to 0
2022-