java.net.ConnectException: Call From localhost/127.0.0.1 to 192.168.232.138:9000 failed on connectio

已于 2022-05-03 18:13:03 修改
阅读量4.4k 收藏 2
点赞数 2
分类专栏： 大数据技术基础 文章标签： Hadoop
于 2022-05-03 18:11:06 首次发布
本文为博主原创文章，未经博主允许不得转载。
本文链接：https://blog.csdn.net/c_lanxiaofang/article/details/124558967
版权 
java.net.ConnectException: Call From localhost/127.0.0.1 to 192.168.232.138:9000 failed on connection exception: java.net.ConnectException: Connection refused; 
22/05/03 00:34:57 INFO client.RMProxy: Connecting to ResourceManager at /192.168.232.138:8032
java.net.ConnectException: Call From localhost/127.0.0.1 to 192.168.232.138:9000 failed on connection exception: java.net.ConnectException: Connection refused; For more details see:  http://wiki.apache.org/hadoop/ConnectionRefused
	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:827)
	at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:757)
	at org.apache.hadoop.ipc.Client.getRpcResponse(Client.java:1553)
	at org.apache.hadoop.ipc.Client.call(Client.java:1495)
	at org.apache.hadoop.ipc.Client.call(Client.java:1394)
	at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:232)
	at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:118)
	at com.sun.proxy.$Proxy10.getFileInfo(Unknown Source)
	at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.getFileInfo(ClientNamenodeProtocolTranslatorPB.java:800)
	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 org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:422)
	at org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeMethod(RetryInvocationHandler.java:165)
	at org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invoke(RetryInvocationHandler.java:157)
	at org.apache.hadoop.io.retry.RetryInvocationHandler$Call.invokeOnce(RetryInvocationHandler.java:95)
	at org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:359)
	at com.sun.proxy.$Proxy11.getFileInfo(Unknown Source)
	at org.apache.hadoop.hdfs.DFSClient.getFileInfo(DFSClient.java:1673)
	at org.apache.hadoop.hdfs.DistributedFileSystem$29.doCall(DistributedFileSystem.java:1524)
	at org.apache.hadoop.hdfs.DistributedFileSystem$29.doCall(DistributedFileSystem.java:1521)
	at org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
	at org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1521)
	at org.apache.hadoop.fs.FileSystem.exists(FileSystem.java:1632)
	at org.apache.hadoop.mapreduce.lib.output.FileOutputFormat.checkOutputSpecs(FileOutputFormat.java:145)
	at org.apache.hadoop.mapreduce.JobSubmitter.checkSpecs(JobSubmitter.java:279)
	at org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:145)
	at org.apache.hadoop.mapreduce.Job$11.run(Job.java:1570)
	at org.apache.hadoop.mapreduce.Job$11.run(Job.java:1567)
	at java.security.AccessController.doPrivileged(Native Method)
	at javax.security.auth.Subject.doAs(Subject.java:422)
	at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1926)
	at org.apache.hadoop.mapreduce.Job.submit(Job.java:1567)
	at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1588)
	at org.apache.hadoop.examples.WordCount.main(WordCount.java:87)
	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 org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:71)
	at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)
	at org.apache.hadoop.examples.ExampleDriver.main(ExampleDriver.java:74)
	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 org.apache.hadoop.util.RunJar.run(RunJar.java:244)
	at org.apache.hadoop.util.RunJar.main(RunJar.java:158)
Caused by: java.net.ConnectException: Connection refused
	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:715)
	at org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206)
	at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:532)
	at org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:701)
	at org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:814)
	at org.apache.hadoop.ipc.Client$Connection.access$3700(Client.java:423)
	at org.apache.hadoop.ipc.Client.getConnection(Client.java:1610)
	at org.apache.hadoop.ipc.Client.call(Client.java:1441)
	... 45 more

Connection Refused

连接拒绝

You get a ConnectionRefused Exception when there is a machine at the address specified, but there is no program listening on the specific TCP port the client is using -and there is no firewall in the way silently dropping TCP connection requests. If you do not know what a TCP connection request is, please consult the specification.

当指定的地址处有一台机器，但是没有程序监听客户机正在使用的特定TCP端口—并且没有防火墙以静默的方式丢弃TCP连接请求时，您会得到ConnectionRefused Exception。 如果您不知道什么是TCP连接请求，请参阅规范。  

Unless there is a configuration error at either end, a common cause for this is the Hadoop service isn't running.

除非两端都有配置错误，否则常见的原因是Hadoop服务没有运行。  

This stack trace is very common when the cluster is being shut down -because at that point Hadoop services are being torn down across the cluster, which is visible to those services and applications which haven't been shut down themselves. Seeing this error message during cluster shutdown is not anything to worry about.

当集群关闭时，这种堆栈跟踪非常常见——因为此时Hadoop服务在整个集群中被关闭，这对那些自己没有关闭的服务和应用程序是可见的。 不用担心在集群关闭期间看到这个错误消息。  

If the application or cluster is not working, and this message appears in the log, then it is more serious.

如果应用程序或集群不工作，并且此消息出现在日志中，则问题更为严重。

The exception text declares both the hostname and the port to which the connection failed. The port can be used to identify the service. For example, port 9000 is the HDFS port. Consult the Ambari port reference, and/or those of the supplier of your Hadoop management tools.

异常文本声明了主机名和连接失败的端口。 端口可以用来识别服务。 例如，9000端口是HDFS的端口。 请查阅Ambari端口参考资料和/或Hadoop管理工具供应商的参考资料。  

Check the hostname the client using is correct. If it's in a Hadoop configuration option: examine it carefully, try doing an ping by hand.

检查客户端使用的主机名是否正确。 如果它在Hadoop配置选项中:仔细检查它，尝试手动执行ping操作。
    
Check the IP address the client is trying to talk to for the hostname is correct.

检查客户端试图与之通信的IP地址，确认主机名是否正确。

Make sure the destination address in the exception isn't 0.0.0.0 -this means that you haven't actually configured the client with the real address for that service, and instead it is picking up the server-side property telling it to listen on every port for connections.

确保异常中的目的地址不是0.0.0.0—这意味着您实际上没有为客户端配置该服务的真实地址，而是获取服务器端属性，告诉它侦听每个端口的连接。

If the error message says the remote service is on "127.0.0.1" or "localhost" that means the configuration file is telling the client that the service is on the local server. If your client is trying to talk to a remote system, then your configuration is broken.

如果错误消息说远程服务在“127.0.0.1”或“localhost”上，这意味着配置文件告诉客户端服务在本地服务器上。 如果您的客户端试图与远程系统通信，那么您的配置就被破坏了。

Check that there isn't an entry for your hostname mapped to 127.0.0.1 or 127.0.1.1 in /etc/hosts (Ubuntu is notorious for this).

检查/etc/hosts中是否有映射到127.0.0.1或127.0.1.1的主机名条目(Ubuntu在这方面臭名昭著)。

Check the port the client is trying to talk to using matches that the server is offering a service on. The netstat command is useful there.

使用服务器提供服务的端口检查客户端试图与之通信的端口。 netstat命令在这里很有用。

On the server, try a telnet localhost <port> to see if the port is open there.

在服务器上，尝试telnet localhost <端口>，以查看该端口在那里是否打开。

On the client, try a telnet <server> <port> to see if the port is accessible remotely.

在客户机上，尝试telnet <server> <port>，以查看该端口是否可以远程访问。

Try connecting to the server/port from a different machine, to see if it just the single client misbehaving.

尝试从另一台机器连接到服务器/端口，看看是否只是单个客户机行为不正常。

If your client and the server are in different subdomains, it may be that the configuration of the service is only publishing the basic hostname, rather than the Fully Qualified Domain Name. The client in the different subdomain can be unintentionally attempt to bind to a host in the local subdomain —and failing.

如果您的客户端和服务器在不同的子域名中，服务的配置可能只是发布基本主机名，而不是完全限定的域名。 不同子域中的客户端可能无意中试图绑定到本地子域中的主机—并且失败。

If you are using a Hadoop-based product from a third party, -please use the support channels provided by the vendor.

如果您正在使用第三方提供的基于hadoop的产品，请使用供应商提供的支持渠道。

Please do not file bug reports related to your problem, as they will be closed as Invalid

请不要提交与您的问题相关的bug报告，因为它们将被关闭为无效

See also Server Overflow

参见服务器溢出

None of these are Hadoop problems, they are hadoop, host, network and firewall configuration issues. As it is your cluster, only you can find out and track down the problem.

这些都不是Hadoop的问题，而是Hadoop、主机、网络和防火墙的配置问题。 因为这是您的集群，只有您才能发现并跟踪问题。

懒笑翻
关注
  • 2
    点赞
  • 踩
  • 2
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 0
    评论
专栏目录
Hadoop报错java.net.ConnectException: Call From xxx to localhost:8020 failed on connection exception
给我一点温度
08-16 7423
运行Spark时报错，java.net.ConnectException: Call From xxx to localhost:8020 failed on connection exception, caused by:java.net.ConnectException:拒绝连接 提示可以去Hadoop官网上找答案，网址如下：https://cwiki.apache.org/conflue...
Web.Client.Programming.with.Perl.Automating.Tasks.on.the.Web.pdf
08-18
The World Wide Web has been credited with bringing the Internet to the masses. The Internet was previously the stomping ground of academics and a small, elite group of computer professionals, mostly UNIX programmers and other oddball types, running obscure commands like ftp and finger, archie and telnet, and so on. With the arrival of graphical browsers for the Web, the Internet suddenly exploded. Anyone could find things on the Web. You didn't need to be "in the know" anymore--you just needed to be properly networked. Equipped with Netscape Navigator or Internet Explorer or any other browser, everyone can now explore the Internet freely. But graphical browsers can be limiting. The very interactivity that makes them the ideal interface for the Internet also makes them cumbersome when you want to automate a task. It's analogous to editing a document by hand when you'd like to write a script to do the work for you. Graphical browsers require you to navigate the Web manually. In an effort to diminish the amount of tedious pointing-and-clicking you do with your browser, this book shows you how to liberate yourself from the confines of your browser. Web Client Programming with Perl is a behind-the-scenes look at how your web browser interacts with web servers. Readers of this book will learn how the Web works and how to write software that is more flexible, dynamic, and powerful than the typical web browser. The goal here is not to rewrite the browser, but to give you the ability to retrieve, manipulate, and redistribute web-based information in an automated fashion. Who This Book Is For I like to think that this book is for everyone. But since that's a bit of an exaggeration, let's try to identify who might really enjoy this book. This book is for software developers who want to expand into a new market niche. It provides proof-of-concept examples and a compilation of web-related technical data. This book is for web administrators who maintain large amounts of data. Administrators can replace manual maintenance tasks with web robots to detect and correct problems with web sites. Robots perform tasks more accurately and quickly than human hands. But to be honest, the audience that's closest to my heart is that of computer enthusiasts, tinkerers, and motivated students, who can use this book to satisfy their curiosity about how the Web works and how to make it work for them. My editor often talks about when she first learned UNIX scripting and how it opened a world of automation for her. When you learn how to write scripts, you realize that there's very little that you can't do within that universe. With this book, you can extend that confidence to the Web. If this book is successful, then for almost any web-related task you'll find yourself thinking, "Hey, I could write a script to do that!" Unfortunately, we can't teach you everything. There are a few things that we assume that you are already familiar with: G The concept of client/server network applications and TCP/IP. G How the Internet works, and how to access it. G The Perl language. Perl was chosen as the language for examples in this book due to its ability to hide complexity. Instead of dealing with C's data structures and low-level system calls, Perl introduces higher-level functions and a straightforward way of defining and using data. If you aren't already familiar with Perl, I recommend Learning Perl by Randal Schwartz, and Programming Perl (popularly known as "The Camel Book") by Larry Wall, Tom Christiansen, and Randal Schwartz. Both of these books are published by O'Reilly & Associates, Inc. There are other fine Perl books as well. Check out http://www.perl.com for the latest book critiques. Is This Book for You? Some of you already know why you picked up this book. But others may just have a nagging feeling that it's something useful to know, though you may not be entirely sure why. At the risk of seeming self-serving, let me suggest some ways in which this book may be helpful: G Some people just like to know how things tick. If you like to think the Web is magic, fine--but there are many who don't like to get into a car without knowing what's under the hood. For those of you who desire a better technical understanding of the Web, this book demystifies the web protocol and the browser/server interaction. G Some people hate to waste even a minute of time. Given the choice between repeating an action over and over for an hour, or writing a script to automate it, these people will choose the script every time. Call it productivity or just stubbornness--the effect is the same. Through web automation, much time can be saved. Repetitive tasks, like tracking packages or stock prices, can be relegated to a web robot, leaving the user free to perform more fruitful activities (like eating lunch). G If you understand your current web environment, you are more likely to recognize areas that can be improved. Instead of waiting for solutions to show up in the marketplace, you can take an active role in shaping the future direction of your own web technology. You can develop your own specialized solutions to fit specific problems. G In today's frenzied high-tech world, knowledge isn't just power, it's money. A reasonable understanding of HTTP looks nice on the resume when you're competing for software contracts, consulting work, and jobs.
已解决java.net.ConnectException异常的正确解决方法，亲测有效！！！
小明的Java问道之路
01-20 1万+
已解决java.net.ConnectException异常的正确解决方法，亲测有效！！！
java.net.ConnectException: Connection refused问题解决办法
09-01
主要介绍了java.net.ConnectException: Connection refused问题解决办法的相关资料,需要的朋友可以参考下
java.util.concurrent.ExecutionException 问题解决方法
09-01
主要介绍了java.util.concurrent.ExecutionException 问题解决方法的相关资料,需要的朋友可以参考下
java.net.ConnectException: Call From localhost/127.0.0.1 to localhost:8020 failed on connection
tszxlzc的专栏
03-13 1万+
执行《Hadoop权威指南》范例3-2时报错 执行命令 export HADOOP_CLASSPATH=ch03-hdfs.jar hadoop FileSystemCat hdfs://localhost/user/liuzc/quangle.txt错误信息Exception in thread "main" java.net.ConnectException: Call From local
运行Map Reduce报错Got exception: java.net.ConnectException: Call From master.localdomain/127.0.0.1 to
weixin_54412689的博客
04-27 2769
MapReduce运行出现报错：ot exception: java.net.ConnectException: Call From master.localdomain/127.0.0.1 to localhost:40721 failed on connection exception: java.net.ConnectException: 拒绝连接;
Call From localhost/127.0.0.1 to localhost:9000 failed on connection exception: java.net.ConnectExce
热门推荐
飞朋的博客
10-14 3万+
连接拒绝 当有指定地址的机器报出了Connection Refused 异常，而且端口没有被占用，网络也没有丢包的前提下。 除非在两端都有配置错误，否则通常的原因是Hadoop服务没有运行。 异常文本声明连接失败的主机名和端口。端口可用于标识服务。例如，端口9000是HDFS端口。其他更多的端口查阅：Hadoop常用端口号汇总 检查主机IP配置是否正确。包括 Hadoop 配置文件。 ...
schematool 初始化hive和hive启动经常出的问题
ge_gewu的博客
12-28 1万+
问题1：Call From localhost/127.0.0.1 to localhost:9000 failed on connection exception: java.net.ConnectException。 没有start dfs 和 yarn造成的问题，启动一下 start-dfs.sh,start-yarn.sh 问题2：schema初始化碰到如下问题，是mysql安装的有问...
安装好Hadoop集群环境之后,首次用来统计“/in“下每个单词出现次数出现的“Java.net.ConnectException:Call from localhost.localdomain/“
m0_53747349的博客
05-23 166
Hadoop刚配置好环境后运行会出现的一些配置问题
Call From hdp-1/192.168.234.129 to hdp-1:8020 failed on connection exception: java.net.ConnectExcept
01-20
分享一个我大晚上提交Hadoop作业到Yarn上因为一个小小小小错误解决了一晚上的问题！ 报错：Exception in thread “main” java.net.ConnectException: Call From hdp-1/192.168.234.129 to hdp-1:8020 failed on connection exception: java.net.ConnectException: Connection refused; For more details see:  http://wiki.apache.org/hadoop/ConnectionRefused 2
Java客户端调用.NET的WebService实例
08-29
下面小编就为大家带来一篇Java客户端调用.NET的WebService实例。小编觉得挺不错的，现在就分享给大家，也给大家做个参考。一起跟随小编过来看看吧
Modbus示例代码（jlibmodbus库）
12-28
jlibmodbus库适用于Java语言开发使用Modbus传输协议，支持Modbus RTU、Modbus TCP、Modbus ASCII、Modbus on Android Things device。 压缩包文件： jlibmodbus-1.2.9.7.zip jlibmodbus-1.2.9.7.tar.gz jlibmodbus_...
关于__Federico Milano 的电力系统分析工具箱.zip
04-26
1.版本：matlab2014/2019a/2021a 2.附赠案例数据可直接运行matlab程序。 3.代码特点：参数化编程、参数可方便更改、代码编程思路清晰、注释明细。 4.适用对象：计算机，电子信息工程、数学等专业的大学生课程设计、期末大作业和毕业设计。
mlab-upenn 研究小组的心脏模型模拟.zip
04-26
1.版本：matlab2014/2019a/2021a 2.附赠案例数据可直接运行matlab程序。 3.代码特点：参数化编程、参数可方便更改、代码编程思路清晰、注释明细。 4.适用对象：计算机，电子信息工程、数学等专业的大学生课程设计、期末大作业和毕业设计。
混合图像创建大师matlab代码.zip
04-26
1.版本：matlab2014/2019a/2021a 2.附赠案例数据可直接运行matlab程序。 3.代码特点：参数化编程、参数可方便更改、代码编程思路清晰、注释明细。 4.适用对象：计算机，电子信息工程、数学等专业的大学生课程设计、期末大作业和毕业设计。
中序遍历二叉树-java版本
04-26
在Java中，实现二叉树的中序遍历同样可以通过递归来完成。中序遍历的顺序是：首先递归地中序遍历左子树，然后访问根节点，最后递归地中序遍历右子树。 在这段代码中，Node类定义了二叉树的节点，BinaryTree类包含一个指向根节点的指针和inOrder方法，用于递归地进行中序遍历。printInOrder方法调用inOrder方法并打印出遍历的结果。 在Main类中，我们创建了一个示例二叉树，并调用printInOrder方法来输出中序遍历的结果。输出应该是：4 2 5 1 3，这表示中序遍历的顺序是左子树（4），然后是根节点（2），接着是右子树的左子树（5），然后是右子树的根节点（1），最后是右子树的右子树（3）。
无头单向非循环链表的实现（SList.c）
最新发布
04-26
无头单向非循环链表的实现（函数定义文件）
两个有序链表的合并pta
04-26
"PTA" 通常指的是一种在线编程平台，例如“Pata”或者某些特定学校或组织的编程练习与自动评测系统。在这种平台或系统中，学生或程序员会提交代码来解决各种问题，然后系统会自动运行并评测这些代码的正确性。 当提到“两个有序链表的合并PTA”时，这通常意味着在PTA平台上解决一个特定的问题，即合并两个有序链表。具体任务可能是给定两个已按升序排序的链表，要求编写代码来合并这两个链表，形成一个新的有序链表。
Call From master/192.168.69.130 to master:9000 failed on connection exception: java.net.ConnectException: Connection refused
04-06
根据提供的引用内容，"Call From master/192.168.69.130 to master:9000 failed on connection exception: java.net.ConnectException: Connection refused"是一个连接异常的错误信息[^1][^2]。这个错误通常发生在尝试建立网络连接时，但连接被拒绝。可能的原因包括目标主机未运行所需的服务、防火墙阻止了连接或网络配置错误。 解决这个问题的方法包括： 1. 确保目标主机正在运行所需的服务。在这种情况下，确保master主机上的服务正在运行，并且正在监听9000端口。 2. 检查防火墙设置。如果防火墙阻止了连接，可以尝试禁用防火墙或配置防火墙规则以允许连接。 3. 检查网络配置。确保网络配置正确，包括IP地址、子网掩码和网关设置。 请注意，具体的解决方法可能因环境和具体情况而异。如果以上方法无法解决问题，请参考提供的链接以获取更多详细信息。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

懒笑翻

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值