zoukankan      html  css  js  c++  java
  • BindException 无法指定被请求的地址

    Caused by: java.net.BindException: Problem binding to [hadoop3:8096] java.net.BindException: 无法指定被请求的地址; For more details see: http://wiki.apache.org/hadoop/BindException
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
    at org.apache.hadoop.net.NetUtils.wrapWithMessage(NetUtils.java:824)
    at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:735)
    at org.apache.hadoop.ipc.Server.bind(Server.java:562)
    at org.apache.hadoop.ipc.Server$Listener.<init>(Server.java:1035)
    at org.apache.hadoop.ipc.Server.<init>(Server.java:2807)
    at org.apache.hadoop.ipc.RPC$Server.<init>(RPC.java:960)
    at org.apache.hadoop.ipc.ProtobufRpcEngine$Server.<init>(ProtobufRpcEngine.java:421)
    at org.apache.hadoop.ipc.ProtobufRpcEngine.getServer(ProtobufRpcEngine.java:342)
    at org.apache.hadoop.ipc.RPC$Builder.build(RPC.java:802)
    at org.apache.hadoop.yarn.factories.impl.pb.RpcServerFactoryPBImpl.createServer(RpcServerFactoryPBImpl.java:172)
    at org.apache.hadoop.yarn.factories.impl.pb.RpcServerFactoryPBImpl.getServer(RpcServerFactoryPBImpl.java:131)
    ... 9 more
    Caused by: java.net.BindException: 无法指定被请求的地址
    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 org.apache.hadoop.ipc.Server.bind(Server.java:545)
    ... 17 more
    2017-12-27 17:37:25,784 INFO org.apache.hadoop.yarn.server.nodemanager.NodeManager: SHUTDOWN_MSG:
    /************************************************************
    SHUTDOWN_MSG: Shutting down NodeManager at hadoop2/192.168.2.212
    ************************************************************/
    [root@hadoop2 logs]# jps
    22049 DataNode
    23734 Jps
    [root@hadoop2 logs]#

    [root@hadoop3 ~]# netstat --numeric-ports -a -t
    Active Internet connections (servers and established)
    Proto Recv-Q Send-Q Local Address Foreign Address State
    tcp 0 0 0.0.0.0:8040 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:9864 0.0.0.0:* LISTEN
    tcp 0 0 localhost:56873 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:8042 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:9866 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:9867 0.0.0.0:* LISTEN
    tcp 0 0 localhost:42859 0.0.0.0:* LISTEN
    tcp 0 0 localhost:38923 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:9868 0.0.0.0:* LISTEN
    tcp 0 0 localhost:54572 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:9870 0.0.0.0:* LISTEN
    tcp 0 0 localhost:47666 0.0.0.0:* LISTEN
    tcp 0 0 localhost:44918 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
    tcp 0 0 localhost:38871 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:8088 0.0.0.0:* LISTEN
    tcp 0 0 localhost:36248 0.0.0.0:* LISTEN
    tcp 0 0 localhost:53561 0.0.0.0:* LISTEN
    tcp 0 0 localhost:48825 0.0.0.0:* LISTEN
    tcp 0 0 localhost:34714 0.0.0.0:* LISTEN
    tcp 0 0 localhost:42650 0.0.0.0:* LISTEN
    tcp 0 0 localhost:38811 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:8030 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:8031 0.0.0.0:* LISTEN
    tcp 0 0 hadoop3:8096 0.0.0.0:* LISTEN
    tcp 0 0 hadoop3:8032 0.0.0.0:* LISTEN
    tcp 0 0 hadoop3:9088 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:46176 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:8033 0.0.0.0:* LISTEN
    tcp 0 0 localhost:40321 0.0.0.0:* LISTEN
    tcp 0 0 localhost:55651 0.0.0.0:* LISTEN
    tcp 0 0 hadoop3:9088 hadoop1:54645 ESTABLISHED
    tcp 0 0 hadoop3:42200 116.255.203.53:80 ESTABLISHED
    tcp 0 0 hadoop3:9088 hadoop3:43541 ESTABLISHED
    tcp 0 0 hadoop3:41439 hadoop1:22 TIME_WAIT
    tcp 0 0 hadoop3:34535 222.76.210.142:80 ESTABLISHED
    tcp 0 0 hadoop3:56969 116.255.203.53:80 ESTABLISHED
    tcp 0 0 hadoop3:52480 hadoop3:8031 ESTABLISHED
    tcp 0 0 hadoop3:41443 hadoop1:22 TIME_WAIT
    tcp 0 0 hadoop3:44670 116.255.203.53:80 ESTABLISHED
    tcp 0 0 localhost:46176 localhost:35759 ESTABLISHED
    tcp 0 0 hadoop3:22 192.168.2.102:63569 ESTABLISHED
    tcp 0 0 hadoop3:51653 116.255.203.53:80 ESTABLISHED
    tcp 0 0 hadoop3:39906 hadoop3:22 TIME_WAIT
    tcp 0 436 hadoop3:22 192.168.2.102:63487 ESTABLISHED
    tcp 0 0 hadoop3:38193 116.255.203.53:80 ESTABLISHED
    tcp 0 0 hadoop3:43541 hadoop3:9088 ESTABLISHED
    tcp 0 2712 hadoop3:22 192.168.2.102:51678 ESTABLISHED
    tcp 0 0 localhost:35759 localhost:46176 ESTABLISHED
    tcp 0 0 hadoop3:22 192.168.2.102:64330 ESTABLISHED
    tcp 0 0 hadoop3:44867 hadoop2:22 TIME_WAIT
    tcp 0 1 hadoop3:52937 61.164.108.182:80 SYN_SENT
    tcp 0 0 hadoop3:57631 116.255.203.53:80 ESTABLISHED
    tcp 0 0 hadoop3:38345 116.255.203.53:80 ESTABLISHED
    tcp 0 0 hadoop3:39903 hadoop3:22 TIME_WAIT
    tcp 0 0 hadoop3:45617 43.247.184.242:80 ESTABLISHED
    tcp 0 1 hadoop3:50148 114.113.158.213:80 SYN_SENT
    tcp 0 0 hadoop3:44862 hadoop2:22 TIME_WAIT
    tcp 0 0 hadoop3:8031 hadoop3:52480 ESTABLISHED
    tcp 0 0 hadoop3:50321 116.255.203.53:80 ESTABLISHED
    tcp 0 0 hadoop3:39899 hadoop3:22 TIME_WAIT
    tcp 0 0 hadoop3:50700 59.110.203.226:3306 ESTABLISHED
    tcp 0 0 hadoop3:22 192.168.2.102:51675 ESTABLISHED
    tcp 0 0 hadoop3:36735 116.255.203.53:80 ESTABLISHED
    tcp 0 0 hadoop3:22 192.168.2.102:51674 ESTABLISHED
    tcp 0 0 hadoop3:22 192.168.2.102:62990 ESTABLISHED
    tcp 0 0 hadoop3:57034 116.255.203.53:80 ESTABLISHED
    tcp 0 0 hadoop3:33928 116.255.203.53:80 ESTABLISHED
    tcp 0 0 hadoop3:60794 43.247.184.242:80 ESTABLISHED
    tcp 0 0 hadoop3:9088 hadoop2:52590 ESTABLISHED
    tcp 0 0 hadoop3:39900 hadoop3:22 TIME_WAIT
    tcp 0 0 hadoop3:22 192.168.2.102:52590 ESTABLISHED
    tcp 0 0 hadoop3:22 192.168.2.102:52086 ESTABLISHED
    tcp 0 0 hadoop3:22 192.168.2.102:63117 ESTABLISHED
    tcp6 0 0 localhost:56873 [::]:* LISTEN
    tcp6 0 0 localhost:42859 [::]:* LISTEN
    tcp6 0 0 localhost:38923 [::]:* LISTEN
    tcp6 0 0 localhost:54572 [::]:* LISTEN
    tcp6 0 0 localhost:47666 [::]:* LISTEN
    tcp6 0 0 [::]:22 [::]:* LISTEN
    tcp6 0 0 localhost:38871 [::]:* LISTEN
    tcp6 0 0 localhost:36248 [::]:* LISTEN
    tcp6 0 0 localhost:53561 [::]:* LISTEN
    tcp6 0 0 localhost:48825 [::]:* LISTEN
    tcp6 0 0 localhost:34714 [::]:* LISTEN
    tcp6 0 0 localhost:42650 [::]:* LISTEN
    tcp6 0 0 localhost:38811 [::]:* LISTEN
    tcp6 0 0 localhost:40321 [::]:* LISTEN
    tcp6 0 0 localhost:55651 [::]:* LISTEN
    [root@hadoop3 ~]#

    问题

    【从节点无法请求主节点的nodemanager地址,但是主节点的nodemanager可以tcp 0 0 hadoop3:8096 0.0.0.0:* LISTEN  监听任意ip的任意端口 】

    【stop-all.sh关闭hadopp所有组件,则8096端口消失】

    上一次登录:三 12月 27 17:37:27 CST 2017pts/24 上
    [root@hadoop3 hadoop]# cat etc/hadoop/yarn-site.xml
    <?xml version="1.0"?>
    <!--
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.
    You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

    Unless required by applicable law or agreed to in writing, software
    distributed under the License is distributed on an "AS IS" BASIS,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
    limitations under the License. See accompanying LICENSE file.
    -->
    <configuration>

    <!-- Site specific YARN configuration properties -->
    <property>
    <name>yarn.resourcemanager.address</name>
    <value>hadoop3:8032</value>
    </property>
    <property>
    <name>yarn.nodemanager.address</name>
    <value>hadoop3:8096</value>
    </property>
    </configuration>
    [root@hadoop3 hadoop]#

  • 相关阅读:
    iBase4J部署总结
    就像我爱你,不仅仅是今天
    10年千亿美元,紫光集团目标跻身全球前五的存储器企业
    ddd
    微信的API都是通过https调用实现的,分为post方法调用和get方法调用。不需要上传数据的采用get方法(使用IntraWeb开发)
    管道通信实例(A程序作为服务器,不断从B程序接收数据,并发送到C程序中)
    HTTP协议中的短轮询、长轮询、长连接和短连接
    细说gulp
    Linux IO 调度器
    SPARK如何使用AKKA实现进程、节点通信
  • 原文地址:https://www.cnblogs.com/rsapaper/p/8126970.html
Copyright © 2011-2022 走看看