Zookeeper启动失败：java.net.BindException: Address already in use

最新推荐文章于 2024-08-17 20:41:32 发布
最新推荐文章于 2024-08-17 20:41:32 发布
阅读量3k 收藏 8
点赞数 4
分类专栏： Zookeeper 文章标签： zookeeper
版权声明：本文为博主原创文章，遵循 CC 4.0 BY 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/Victory_Lei/article/details/101213248
版权

在启动Zookeeper时候失败：java.net.BindException: Address already in use

查看日志信息如下所示：

[ipaas@admin01 bin]$  ./zkServer.sh start-foreground
ZooKeeper JMX enabled by default
Using config: /home/ipaas/zookeeper/zookeeper-3.4.11/bin/../conf/zoo.cfg
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/ipaas/zookeeper/zookeeper-3.4.11/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/ipaas/zookeeper/zookeeper-3.4.11/lib/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
2019-09-23 04:52:12,325 [myid:] - INFO  [main:QuorumPeerConfig@136] - Reading configuration from: /home/ipaas/zookeeper/zookeeper-3.4.11/bin/../conf/zoo.cfg
2019-09-23 04:52:12,341 [myid:] - INFO  [main:QuorumPeer$QuorumServer@184] - Resolved hostname: 192.168.47.103 to address: /192.168.47.103
2019-09-23 04:52:12,341 [myid:] - INFO  [main:QuorumPeer$QuorumServer@184] - Resolved hostname: 192.168.47.102 to address: /192.168.47.102
2019-09-23 04:52:12,342 [myid:] - INFO  [main:QuorumPeer$QuorumServer@184] - Resolved hostname: 192.168.47.101 to address: /192.168.47.101
2019-09-23 04:52:12,342 [myid:] - INFO  [main:QuorumPeerConfig@398] - Defaulting to majority quorums
2019-09-23 04:52:12,345 [myid:1] - INFO  [main:DatadirCleanupManager@78] - autopurge.snapRetainCount set to 3
2019-09-23 04:52:12,346 [myid:1] - INFO  [main:DatadirCleanupManager@79] - autopurge.purgeInterval set to 0
2019-09-23 04:52:12,346 [myid:1] - INFO  [main:DatadirCleanupManager@101] - Purge task is not scheduled.
2019-09-23 04:52:12,373 [myid:1] - INFO  [main:QuorumPeerMain@130] - Starting quorum peer
2019-09-23 04:52:12,379 [myid:1] - INFO  [main:ServerCnxnFactory@117] - Using org.apache.zookeeper.server.NIOServerCnxnFactory as server connection factory
2019-09-23 04:52:12,492 [myid:1] - INFO  [main:Login@297] - Server successfully logged in.
2019-09-23 04:52:12,494 [myid:1] - INFO  [main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:2181
2019-09-23 04:52:12,495 [myid:1] - ERROR [main:QuorumPeerMain@92] - Unexpected exception, exiting abnormally
java.net.BindException: Address already in use
	at sun.nio.ch.Net.bind0(Native Method)
	at sun.nio.ch.Net.bind(Net.java:433)
	at sun.nio.ch.Net.bind(Net.java:425)
	at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
	at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
	at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67)
	at org.apache.zookeeper.server.NIOServerCnxnFactory.configure(NIOServerCnxnFactory.java:90)
	at org.apache.zookeeper.server.quorum.QuorumPeerMain.runFromConfig(QuorumPeerMain.java:133)
	at org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:114)
	at org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:81)

如日志所示，该错误是由于Zookeeper对应的端口号被占用导致的。

查看端口占用情况：

[ipaas@admin01 bin]$ sudo netstat -nltp | grep 2181
tcp6       0      0 :::2181                 :::*                    LISTEN      37431/java

如上所示，占用Zookeeper对应端口号的应用是java，只需要kill掉该应用就能成功启动Zookeeper了。

[ipaas@admin01 bin]$ kill -9 37431

重新启动zookeeper，结果如下所示：

[ipaas@admin01 bin]$  ./zkServer.sh start-foreground
ZooKeeper JMX enabled by default
Using config: /home/ipaas/zookeeper/zookeeper-3.4.11/bin/../conf/zoo.cfg
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/ipaas/zookeeper/zookeeper-3.4.11/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/ipaas/zookeeper/zookeeper-3.4.11/lib/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
2019-09-23 04:56:33,944 [myid:] - INFO  [main:QuorumPeerConfig@136] - Reading configuration from: /home/ipaas/zookeeper/zookeeper-3.4.11/bin/../conf/zoo.cfg
2019-09-23 04:56:33,969 [myid:] - INFO  [main:QuorumPeer$QuorumServer@184] - Resolved hostname: 192.168.47.103 to address: /192.168.47.103
2019-09-23 04:56:33,969 [myid:] - INFO  [main:QuorumPeer$QuorumServer@184] - Resolved hostname: 192.168.47.102 to address: /192.168.47.102
2019-09-23 04:56:33,970 [myid:] - INFO  [main:QuorumPeer$QuorumServer@184] - Resolved hostname: 192.168.47.101 to address: /192.168.47.101
2019-09-23 04:56:33,970 [myid:] - INFO  [main:QuorumPeerConfig@398] - Defaulting to majority quorums
2019-09-23 04:56:33,978 [myid:1] - INFO  [main:DatadirCleanupManager@78] - autopurge.snapRetainCount set to 3
2019-09-23 04:56:33,979 [myid:1] - INFO  [main:DatadirCleanupManager@79] - autopurge.purgeInterval set to 0
2019-09-23 04:56:33,979 [myid:1] - INFO  [main:DatadirCleanupManager@101] - Purge task is not scheduled.
2019-09-23 04:56:34,007 [myid:1] - INFO  [main:QuorumPeerMain@130] - Starting quorum peer
2019-09-23 04:56:34,012 [myid:1] - INFO  [main:ServerCnxnFactory@117] - Using org.apache.zookeeper.server.NIOServerCnxnFactory as server connection factory
2019-09-23 04:56:34,134 [myid:1] - INFO  [main:Login@297] - Server successfully logged in.
2019-09-23 04:56:34,136 [myid:1] - INFO  [main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:2181
2019-09-23 04:56:34,141 [myid:1] - INFO  [main:QuorumPeer@1158] - tickTime set to 2000
2019-09-23 04:56:34,141 [myid:1] - INFO  [main:QuorumPeer@1204] - initLimit set to 10
2019-09-23 04:56:34,141 [myid:1] - INFO  [main:QuorumPeer@1178] - minSessionTimeout set to -1
2019-09-23 04:56:34,142 [myid:1] - INFO  [main:QuorumPeer@1189] - maxSessionTimeout set to -1
2019-09-23 04:56:34,161 [myid:1] - INFO  [main:QuorumPeer@1467] - QuorumPeer communication is not secured!
2019-09-23 04:56:34,161 [myid:1] - INFO  [main:QuorumPeer@1496] - quorum.cnxn.threads.size set to 20
2019-09-23 04:56:34,164 [myid:1] - INFO  [main:QuorumPeer@668] - currentEpoch not found! Creating with a reasonable default of 0. This should only happen when you are upgrading your installation
2019-09-23 04:56:34,175 [myid:1] - INFO  [main:QuorumPeer@683] - acceptedEpoch not found! Creating with a reasonable default of 0. This should only happen when you are upgrading your installation
2019-09-23 04:56:34,191 [myid:1] - INFO  [ListenerThread:QuorumCnxManager$Listener@736] - My election bind port: /192.168.47.101:3888
2019-09-23 04:56:34,201 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumPeer@909] - LOOKING
2019-09-23 04:56:34,202 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@820] - New election. My id =  1, proposed zxid=0x0
2019-09-23 04:56:34,208 [myid:1] - INFO  [WorkerReceiver[myid=1]:FastLeaderElection@602] - Notification: 1 (message format version), 1 (n.leader), 0x0 (n.zxid), 0x1 (n.round), LOOKING (n.state), 1 (n.sid), 0x0 (n.peerEpoch) LOOKING (my state)
2019-09-23 04:56:34,214 [myid:1] - INFO  [WorkerSender[myid=1]:QuorumCnxManager@347] - Have smaller server identifier, so dropping the connection: (2, 1)
2019-09-23 04:56:34,218 [myid:1] - INFO  [WorkerSender[myid=1]:QuorumCnxManager@347] - Have smaller server identifier, so dropping the connection: (3, 1)
2019-09-23 04:56:34,427 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@347] - Have smaller server identifier, so dropping the connection: (2, 1)
2019-09-23 04:56:34,433 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@347] - Have smaller server identifier, so dropping the connection: (3, 1)
2019-09-23 04:56:34,435 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@854] - Notification time out: 400
2019-09-23 04:56:34,848 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@347] - Have smaller server identifier, so dropping the connection: (2, 1)
2019-09-23 04:56:34,853 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@347] - Have smaller server identifier, so dropping the connection: (3, 1)
2019-09-23 04:56:34,854 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@854] - Notification time out: 800
2019-09-23 04:56:35,658 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@347] - Have smaller server identifier, so dropping the connection: (2, 1)
2019-09-23 04:56:35,664 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@347] - Have smaller server identifier, so dropping the connection: (3, 1)
2019-09-23 04:56:35,665 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@854] - Notification time out: 1600
2019-09-23 04:56:37,269 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@347] - Have smaller server identifier, so dropping the connection: (2, 1)
2019-09-23 04:56:37,273 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@347] - Have smaller server identifier, so dropping the connection: (3, 1)
2019-09-23 04:56:37,275 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@854] - Notification time out: 3200
2019-09-23 04:56:40,506 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@347] - Have smaller server identifier, so dropping the connection: (2, 1)
2019-09-23 04:56:40,510 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@347] - Have smaller server identifier, so dropping the connection: (3, 1)
2019-09-23 04:56:40,512 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@854] - Notification time out: 6400
2019-09-23 04:56:46,918 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@347] - Have smaller server identifier, so dropping the connection: (2, 1)
2019-09-23 04:56:46,922 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@347] - Have smaller server identifier, so dropping the connection: (3, 1)
2019-09-23 04:56:46,923 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@854] - Notification time out: 12800
2019-09-23 04:56:59,729 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@347] - Have smaller server identifier, so dropping the connection: (2, 1)
2019-09-23 04:56:59,733 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@347] - Have smaller server identifier, so dropping the connection: (3, 1)
2019-09-23 04:56:59,734 [myid:1] - INFO  [QuorumPeer[myid=1]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@854] - Notification time out: 25600
Rocky000000
关注
专栏目录
ZooKeeper源码分析之NIOServerCnxnFactory
long99920的博客
11-07 1927
文章目录2021SC@SDUSCNIOServerCnxnFactory工作流程（一）NIOServerCnxnFactory工作流程（二）NIOServerCnxnFactory.configureNIOServerCnxnFactory.start()启动服务该函数用来启动后台服务AcceptThreadSelectorThreadConnectionExpirerThread总结 2021SC@SDUSC 在讲述NIOServerCnxnFactory之前，先了解一下NIOServerCnxnFact
Zookeeper java.net.BindException: Address already in use
Deer的博客
08-07 789
在使用“zkServer.sh start”启动后，显示正常，但是输入zkServer.sh status则Error contacting service. It is probably not running.如下所示 hadoop@master:/usr/local/zookeeper/bin$ zkServer.sh start ZooKeeper JMX enabled by default Using config: /usr/local/zookeeper/bin/../conf/zoo.cf
Zookeeper启动失败，提示：java.net.BindException: Address already in use 加图解超级容易理解
weixin_45793065的博客
06-12 3121
启动zookeeper ,查看状态出错 查看日志 ./zkServer.sh start-foreground 原因： zoo.cfg中选项clientPort配置的端口号2181已经被占用。 执行命令查看： netstat -nltp | grep 2181 解决方法： 有两种方法： 一是：将占用2181端口的进程杀死：kill -9 3027； 或者是：修改clientPort选项的配置，比如配置为2282. 然后重启zookeeper服务即可。 第一种我的还是不成功 只能用第二种，修改zo
已解决：java.net.BindException: 地址已在使用
最新发布
A1551143530的博客
08-17 3101
java.net.BindException: 地址已在使用通常是由于尝试绑定到一个已被占用的端口而引起的。通过查找并关闭占用端口的进程、修改端口号、检查应用程序是否重复启动或设置选项等方式，可以有效解决这个问题。确保在开发和部署中对端口占用情况进行合理管理，是避免此类问题的关键。希望本文提供的解决方案对你有所帮助！
杀掉某个进程！怎么查看pid，报错：Address already in use
lsr40的博客
09-01 2万+
说在文前，菜鸟一个，如果有说的不对的，还请见谅，望能指出，让我这井底之蛙也能见见世面。 今天分享下一个比较常见的问题，端口被占用。 报错大致类型如下： 这里我是zookeeper开启的时候，报了Address已经被使用。其实这个问题还挺常见的，比如我们重复打开Tomcat就可以看到这个报错。 解决方法如下： 最简单的方法：jps看看，然后看看有没有对应的进程，有就直接kill ...
启动zookeeper时：java.net.BindException: 地址已在使用
海棠的博客
06-28 1583
zookeeper
Zookeeper启动失败，提示：java.net.BindException: Address already in use
07-21
你遇到的问题是因为端口被占用，导致Zookeeper无法启动。这个错误通常是由于另一个进程已经在使用相同的端口号。要解决这个问题，你可以尝试以下几种方法： 1. 查找并杀死占用该端口的进程。可以使用以下命令来查找...
Zookeeper启动zkServer.cmd闪退, zk服务启动跟报错：Unexpected exception, exiting abnormally java.net.BindException
Erostrate9
06-22 1635
Zookeeper启动zkServer.cmd闪退 编辑zkServer.cmd，在代码最后一行添加pause 运行cmd，查看保存内容 2021-06-22 10:24:21,727 [myid:] - ERROR [main:ZooKeeperServerMain@63] - Unexpected exception, exiting abnormally java.net.BindException: Address already in use: bind at sun.nio.ch
ERROR [main:QuorumPeerMain@113] - Unexpected exception, exiting abnormally java.net.BindException: Address already in use
07-28
- *2* *3* [Zookeeper启动失败：java.net.BindException: Address already in use](https://blog.csdn.net/py_123456/article/details/80314221)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630",...
dubbo启动报错： Address already in use
Ahull的博客
02-14 2866
报错内容如下： java.lang.IllegalStateException: Failed to start jetty server on 192.168.254.1:8080, cause: Address already in use: bind at com.alibaba.dubbo.monitor.simple.container.JettyContainer.start(JettyContainer.java:74) at com.alibaba.dubbo
2023-06-06 14:40:11,144 [myid:2] - ERROR [main:QuorumPeerMain@89] - Unexpected exception, exiting abnormally java.net.BindException: Address already in use at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Net.java:461)
06-07
这个错误通常是由于在同一台机器上启动了多个Zookeeper服务导致的。你可以通过以下步骤解决这个问题： 1. 首先，你可以使用以下命令检查当前正在运行的Zookeeper服务的进程： ``` ps aux | grep zookeeper ``` ...
Zookeeper启动不成功，日志报java.net.BindException: Address already in use
基咯咯
01-16 1万+
最近集群在做新的迁移改动，所以需要开启很多集群。当在开启zookeeper时，有一个节点zookeeper并不能正常启动，使用命令：./zkServer.sh status 查看了下状态，报错如下：JMX enabled by default Using config: /usr/local/zookeeper/bin/../conf/zoo.cfg Error contacting servic
【Kafka】ZooKeeper启动失败报错java.net.BindException: Address already in use: bind
HEX9CF的技术博客
09-04 1111
Kafka 2.8.1 ZooKeeper启动失败。
Zookeeper报错:java.net.BindException: Address already in use: bind
lisa2017_的博客
01-15 617
Zookeeper报错:java.net.BindException: Address already in use: bind 原因：2181端口被占用 查询是什么占用了2181端口，然后停掉就可以了 在任务管理器中找到，并删除就行
zookeeper学习笔记001-Address already in use: bind启动报错
添柴程序猿的专栏
07-25 7244
JAVA技术交流QQ群：170933152  第一次安装,填坑的时候 异常由于我本地8080端口占用: 查看端口占用可以用下面的命令: windows cmd中: netstat -ano|findstr "2181" 我一查这个端口没有被占用啊 C:\Users\Administrator>netstat -ano|findstr "2181" 郁闷,之后才知道,这货,原来用...
Zookeeper启动失败（java.net.BindException: 地址已在使用）
热门推荐
光于前裕于后的博客
06-13 3万+
[hadoop@DEV22 ~]$ opt/zookeeper-3.4.8/bin/zkServer.sh start ZooKeeper JMX enabled by default Using config: /home/hadoop/opt/zookeeper-3.4.8/bin/../conf/zoo.cfg Starting zookeeper ... STARTED [hadoop@D
zookeeper启动报: address already in use
酷爱编程的小猿同学
06-09 4028
zookeeper启动的时候报错，进入bin目录查看zookeeper.out的报错信息 zookeeper启动报错信息如下： 原因：2181端口被占用的问题。用netstat查看下2181占用的情况 解决方法： 1、查看端口号被谁占用了：sudo netstat -atunlp | grep 2181 如果没有报错: -bash: netstat: command not found 安装命令：yum install ne...
端口没被占用，但是zookeeper还是报错： Address already in use: bind的解决方案
pangdongh的博客
12-14 2005
记录一次奇葩的zookeeper报错 zookeeper报错： Address already in use: bind 原先以为是2182端口被占用 使用 下面命令查询后发现并没有进程占用此端口 netstat -aon|findstr ':2181' 查了N多东西后才发现是hyper-v占用了一堆端口 查询命令： netsh interface ipv4 show excludedportrange protocol=tcp 通过下面的命令修改保留的端口范围 netsh int ipv4 set
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值