在配置zookeeper遇到Error contacting service. It is probably not running

在配置完zookeeper集群后,三个节点,分别启动三个节点如下:

[[email protected] bin]# zkServer.sh start
JMX enabled by default
Using config: /usr/local/zk/bin/../conf/zoo.cfg
Starting zookeeper ... STARTED

在查看zookeeper状态时遇到

[[email protected] bin]# zkServer.sh status
JMX enabled by default
Using config: /usr/local/zk/bin/../conf/zoo.cfg
Error contacting service. It is probably not running.

而其他两个节点却是现实正常;最后检查配置zoo.cfg配置发现是该节点的主机名写错了;先停止三个节点zookeeper服务,逐一的修改节点上zoo.cfg配置文件,在逐一的启动 ,结果显示正常;

时间: 2024-08-02 07:01:05

在配置zookeeper遇到Error contacting service. It is probably not running的相关文章

zookeeper错误Error contacting service. It is probably not running.

./zkServer.sh start启动成功,并且使用jps能看zookeeper的进程. ./zkServer.sh status缺报错,Error contacting service. It is probably not running. 好多地方说和防火墙有关系 我的解决办法是先看一下2181是否被占用,如果没有被占用查看8080端口是否会占用 zookeeper有一个内嵌的管理控制台是通过jetty启动,会占用8080端口 通过查看zookeeper的官方文档,发现有3种解决途径:

启动zookeeper时,jps显示有进程,但是status查看状态时就Error contacting service. It is probably not running

转自:http://www.cnblogs.com/xiaohua92/p/5460515.html#undefined 安装zookeeper时候,可以查看进程启动,但是状态显示报错:Error contacting service. It is probably not running 安装zookeeper-3.3.2的时候,启动正常没报错,但zkServer.sh status查看状态的时候却出现错误,如下: JMX enabled by defaultUsing config: /ha

安装zookeeper时候,可以查看进程启动,但是状态显示报错:Error contacting service. It is probably not running

安装zookeeper-3.3.2的时候,启动正常没报错,但zkServer.sh status查看状态的时候却出现错误,如下: JMX enabled by defaultUsing config: /hadoop/zookeeper/bin/../conf/zoo.cfgError contacting service. It is probably not running. jps查看进程,却发现进程已启动 7313  QuorumPeerMain 在网上查阅资料一共有三种解决方法: 1,

zookeeper 集群 Cannot open channel to X at election address Error contacting service. It is probably not running.

zookeeper集群   启动 1.问题现象. 启动每一个都提示  STARTED 但是查看 status时全部节点都报错 [[email protected] bin]# sh zkServer.sh  start ZooKeeper JMX enabled by default Using config: /usr/local/zookeeper-3.4.8/bin/../conf/zoo.cfg Starting zookeeper ... STARTED [[email protect

zookeeper环境搭建中的几个坑[Error contacting service. It is probably not running]的分析及解决

Zookeeper简介 关于zk的介绍, zk的paxos算法, 网上已经有各位大神在写了, 本文主要写我在搭建过程中的几个极有可能遇到的坑. Zookeeper部署中的坑 坑之一 Error contacting service. It is probably not running 在配置完zookeeper集群后,三个节点,分别启动三个节点如下: [[email protected] bin]# zkServer.sh start JMX enabled by default Using

Zookeeper群起脚本启动失败及查看状态出现:Error contacting service. It is probably not running

1.问题: 群起脚本启动后查看jps没有出现:QuorumPeerMain Zookeeper正常启动但是群起脚本查状态出现:Error contacting service. It is probably not running错误 ZooKeeper JMX enabled by default Using config: /opt/module/zookeeper-3.4.10/bin/../conf/zoo.cfg Error contacting service. It is prob

zz-zookeeper 启动失败 BindException: Address already in use 或者Error contacting service. It is probably not running

https://www.bbsmax.com/A/ZOJPOw8xzv/ 平台:centos-6.3-i386 jdk-7u51 storm 0.9.1 python 2.6.6   hadoop 1.2.1 今天上午装storm的时候遇到这个问题,好郁闷.把网上介绍的方法都试了一遍,都没能很好的解决问题. 先介绍我自己的方法: 当我查看/bin目录下的zookeeper.out后,发现是2181端口被占用了,按照网上的方法,改成2182或者2183,都没有解决问题.此时我想到能不能把2181给

Zookeep启动异常:Error contacting service. It is probably not running.

Zookeep安装启动异常    异常提示: [[email protected] bin]# ./zkServer.sh status JMX enabled by default Using config: /usr/local/zk/bin/../conf/zoo.cfg Error contacting service. It is probably not running 解决方案: 网上问题答案有许多种,一一归纳: 1. zoo.cfg配置文件中指定目录却没有创建! 创建相应目录即可

zookeeper启动时报Cannot open channel to X at election address Error contacting service. It is probably not running.

配置storm集群的时候出现如下异常: 2016-06-26 14:10:17,484 [myid:1] - WARN [SyncThread:1:[email protected]] - fsync-ing the write ahead log in SyncThread:1 took 1340ms which will adversely effect operation latency. See the ZooKeeper troubleshooting guide 2016-06-26