开发者社区> 问答> 正文

hbase hbck return Caused by: java.net.BindException: Address already in use

[apache@datanode01 ~]$ hbase hbck
Exception in thread "main" java.lang.reflect.InvocationTargetException

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:386)
    at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:401)

Caused by: 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.net.httpserver.ServerImpl.bind(ServerImpl.java:133)
    at sun.net.httpserver.HttpServerImpl.bind(HttpServerImpl.java:54)
    at io.prometheus.jmx.shaded.io.prometheus.client.exporter.HTTPServer.<init>(HTTPServer.java:145)
    at io.prometheus.jmx.shaded.io.prometheus.jmx.JavaAgent.premain(JavaAgent.java:49)
    ... 6 more

FATAL ERROR in native method: processing of -javaagent failed
Aborted

[apache@datanode01 ~]$ netstat -nltp
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:9981 0.0.0.0:* LISTEN 10563/java
tcp 0 0 0.0.0.0:50020 0.0.0.0:* LISTEN 10563/java
tcp 0 0 127.0.0.1:54188 0.0.0.0:* LISTEN 10563/java
tcp 0 0 0.0.0.0:50706 0.0.0.0:* LISTEN 10563/java
tcp 0 0 0.0.0.0:41106 0.0.0.0:* LISTEN 10563/java
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:50010 0.0.0.0:* LISTEN 10563/java
tcp 0 0 0.0.0.0:50075 0.0.0.0:* LISTEN 10563/java
tcp 0 0 0.0.0.0:9211 0.0.0.0:* LISTEN 10563/java
tcp 0 0 :::16030 :::* LISTEN 15985/java
tcp 0 0 :::60830 :::* LISTEN 15985/java
tcp 0 0 :::50849 :::* LISTEN 11919/java
tcp 0 0 ::ffff:10.184.21.38:60546 :::* LISTEN 19024/java
tcp 0 0 :::9223 :::* LISTEN 11919/java
tcp 0 0 :::8040 :::* LISTEN 11919/java
tcp 0 0 :::4040 :::* LISTEN 19024/java
tcp 0 0 :::9962 :::* LISTEN 15985/java
tcp 0 0 :::8042 :::* LISTEN 11919/java
tcp 0 0 :::9100 :::* LISTEN -
tcp 0 0 :::46829 :::* LISTEN 11919/java
tcp 0 0 :::48429 :::* LISTEN 11919/java
tcp 0 0 ::ffff:10.184.21.38:33774 :::* LISTEN 19024/java
tcp 0 0 :::9232 :::* LISTEN 15985/java
tcp 0 0 :::16020 :::* LISTEN 15985/java
tcp 0 0 :::9973 :::* LISTEN 11919/java
tcp 0 0 :::22 :::* LISTEN -
tcp 0 0 ::1:25 :::* LISTEN -
tcp 0 0 :::13562 :::* LISTEN 11919/java
tcp 0 0 :::59164 :::* LISTEN 15985/java
[apache@datanode01 ~]$ jps
19024 SparkSubmit
15985 HRegionServer
10563 DataNode
23287 Jps
11919 NodeManager

请问下大家有碰到过这个问题吗?

展开
收起
hbase小能手 2018-11-07 16:31:53 5813 0
2 条回答
写回答
取消 提交回答
  • java 数据分析 数据可视化 大数据

    ip冲突啊 , 把之前的kill掉

    2019-07-17 23:12:45
    赞同 展开评论 打赏
  • 社区管理员

    明显就是你之前跑了一个,再跑一个 端口冲突了,或者你跟一个 端口冲突了

    2019-07-17 23:12:45
    赞同 展开评论 打赏
问答排行榜
最热
最新

相关电子书

更多
大数据时代的存储 ——HBase的实践与探索 立即下载
Hbase在滴滴出行的应用场景和最佳实践 立即下载
阿里云HBase主备双活 立即下载