zookeeper启动失败的排错 no route to host 防火墙未关闭导致的
2017-08-30 14:21
966 查看
1.执行zkServer.sh start 后显示:
JMX enabled by default
Using config:/home/Hadoop/app/zookeeper-3.4.5/bin/../conf/zoo.cfg
Starting zookeeper ... STARTED
2.jps后发现没有QuorumPeerMain进程
3.查看zookeeper-3.4.5/data下的zookeeper-3.4.5.out,如果提示 binding to port 0.0.0.0/0.0.0.0:2181
ERROR [main:QuorumPeerMain@89] - Unexpected exception, exiting abnormally Java.NET.BindException:
Address already in use
说明2181端口被占用,通过netstat -nltp | grep 2181检查是否已被占用,如果有则把对应的进程kill掉(kill 进程的pid),然后再启动zookeeper
4..jps后发现有QuorumPeerMain进程,然后执行zkServer.sh status,如果显示:
JMX enabled by default
Using config: /home/hadoop/app/zookeeper-3.4.5/bin/../conf/zoo.cfg
Error contacting service. It is probably not running.
说明未启动成功,通过查看zookeeper-3.4.5.out,如果提示
Cannot open channel to 1 at election address hadoop05/10.37.129.105:3888
java.net.NoRouteToHostException: No route to host,说明无法连接远程电脑10.37.129.105:3888,很有可能开启了防火墙
通过sudo service iptables status检查,如果确实开启,则通过sudo service iptables stop将其关闭,最后再查看状态zkServer.sh status
此时,基本都能够正常启动了,提示:
JMX enabled by default
Using config: /home/hadoop/app/zookeeper-3.4.5/bin/../conf/zoo.cfg
Mode: leader(或follower)
JMX enabled by default
Using config:/home/Hadoop/app/zookeeper-3.4.5/bin/../conf/zoo.cfg
Starting zookeeper ... STARTED
2.jps后发现没有QuorumPeerMain进程
3.查看zookeeper-3.4.5/data下的zookeeper-3.4.5.out,如果提示 binding to port 0.0.0.0/0.0.0.0:2181
ERROR [main:QuorumPeerMain@89] - Unexpected exception, exiting abnormally Java.NET.BindException:
Address already in use
说明2181端口被占用,通过netstat -nltp | grep 2181检查是否已被占用,如果有则把对应的进程kill掉(kill 进程的pid),然后再启动zookeeper
4..jps后发现有QuorumPeerMain进程,然后执行zkServer.sh status,如果显示:
JMX enabled by default
Using config: /home/hadoop/app/zookeeper-3.4.5/bin/../conf/zoo.cfg
Error contacting service. It is probably not running.
说明未启动成功,通过查看zookeeper-3.4.5.out,如果提示
Cannot open channel to 1 at election address hadoop05/10.37.129.105:3888
java.net.NoRouteToHostException: No route to host,说明无法连接远程电脑10.37.129.105:3888,很有可能开启了防火墙
通过sudo service iptables status检查,如果确实开启,则通过sudo service iptables stop将其关闭,最后再查看状态zkServer.sh status
此时,基本都能够正常启动了,提示:
JMX enabled by default
Using config: /home/hadoop/app/zookeeper-3.4.5/bin/../conf/zoo.cfg
Mode: leader(或follower)
相关文章推荐
- zookeeper使用和原理探究 (注意linux下防火墙导致启动失败的坑,使用service iptables stop 关闭防火墙 使用service iptables status确认)
- CDH集群异常关闭导致zookeeper启动失败
- zookeeper启动失败的排错
- Weblogic魔法堂:AdminServer.lok被锁导致启动、关闭域失败
- AdminServer.lok被锁导致启动、关闭域失败
- Amazon EC2上配置集群出现zookeeper启动失败的排错
- zookeeper启动失败的排错
- Oracle表空间文件损坏导致的数据库异常关闭并启动失败问题的解决方法
- Weblogic魔法堂:AdminServer.lok被锁导致启动、关闭域失败
- 未关闭防火墙导致tomcat启动后访问无响应
- Weblogic:AdminServer.lok被锁导致启动、关闭域失败
- 【Hadoop】ZooKeeper集群搭建中的Connection refused而导致的启动失败
- zookeeper启动失败的排错
- 无效的DNS配置,导致防火墙服务启动失败
- AdminServer.lok被锁导致启动、关闭域失败
- zookeeper启动失败导致项目不能运行
- bootstrap.memory_lock: true导致Elasticsearch启动失败问题
- ZooKeeper3.3.6 启动失败
- Oracle 创建连接数过大 导致启动失败
- 修改RAC中的私网地址导致CRS启动失败