I get the following error in Eclipse:
我在Eclipse中得到以下错误:
[timestamp - ddms] Can't bind to local 8600 for debugger
Why?
为什么?
20 个解决方案
#1
83
In addition to adding "127.0.0.1 localhost" to your hosts file, make the following changes in Eclipse.
除了将“127.0.0.1 localhost”添加到您的主机文件之外，还需要在Eclipse中进行以下更改。
Under Window -> Preferences -> Android -> DDMS:
在窗口下->首选项-> Android -> DDMS:
- Set Base local debugger port to "8601"
- 将基本本地调试器端口设置为“8601”
- Check the box that says "Use ADBHOST" and the value should be "127.0.0.1"
- 勾选“使用ADBHOST”的框，值应为“127.0.0.1”
Thanks to Ben Clayton in the comments for leading me to a solution.
感谢Ben Clayton为我提供了解决方案。
Some Google keywords: Ailment or solution for Nexus S Android debugging with the error message: Can't bind to local 8600 for debugger.
一些谷歌关键字:故障或解决方案的Nexus S Android调试与错误消息:无法绑定到本地8600调试器。
#2
23
Try killing port 8600 with this command:
尝试用这个命令杀死端口8600:
fuser -k 8600/tcp
That fixed it for me.
这帮我搞定了。
#3
15
Don't uninstall, this is just a dumb thing done by the system which as trouble finding localhost it seems. Take a look in here, it's quite easy to fix. I had the same issue a few weeks ago and solved it this way.
不要卸载，这只是系统做的一件蠢事，因为它看起来很难找到本地主机。看看这里，很容易修复。几个星期前我也遇到过同样的问题。
the window Host file that is messed up:
the file is at this place :
C:\WINDOWS\system32\drivers\etc窗口搞砸了主机文件:这个文件在这个地方:C:\WINDOWS\system32\drivers\etc
And should contain this line : 127.0.0.1 localhost
并且应该包含这一行:127.0.0.1 localhost
#4
10
I had the following hosts file
我有以下的主机文件
127.0.0.1 localhost192.168.1.2 localhost
127.0.0.1 localhost 192.168.1.2 localhost
and i started getting the error continously and it was very annoying
我开始不断地得到错误，这很烦人
“Can't bind to local 8600 for debugger”
“Can't bind to local 8601 for debugger”
“Can't bind to local 8602 for debugger” and so on
“无法绑定到本地8600调试器”“无法绑定到本地8601调试器”“无法绑定到本地8602调试器”等等
I deleted the second line from the hosts file 192.168.1.2 localhost and everything is back to normal.
我从主机文件192.168.1.2 localhost中删除了第二行，一切恢复正常。
Hope this helps.
希望这个有帮助。
#5
8
In addition to adding 127.0.0.1 localhost to your hosts file, make the following changes in Eclipse.
除了向主机文件中添加127.0.0.1 localhost之外，还需要在Eclipse中进行以下更改。
Under
下
Window -> Preferences -> Android -> DDMS
窗口->首选项-> Android -> DDMS
Set Base local debugger port to 8601
将基本本地调试器端口设置为8601
Check the box that says Use ADBHOST and the value should be 127.0.0.1 Thanks to Ben Clayton & Doguhan Uluca in the comments for leading me to a solution.
勾选ADBHOST的复选框，其值应该是127.0.0.1，感谢Ben Clayton & Doguhan Uluca在评论中引导我找到解决方案。
Some Google keywords:
一些谷歌关键词:
Ailment or solution for Nexus S Android debugging with the error message: Can't bind to local 8600 for debugger.
Nexus S Android调试的故障或解决方案带有错误消息:无法绑定到本地8600进行调试。
#6
7
I had a similar problem on OSX. It just so happens I had opened two instances of Eclipse so I could refer to some code in another workspace. Eventually I realized the two instances might be interfering with each other so I closed one. After that, I'm no longer seeing the "Can't bind..." error.
我在OSX上遇到了类似的问题。碰巧我打开了两个Eclipse实例，因此我可以在另一个工作区中引用一些代码。最后我意识到这两个实例可能互相干扰，所以我关闭了一个。在那之后，我不再看到“无法绑定…”的错误。
#7
7
For people running Android Studio and Eclipse:
对于运行Android Studio和Eclipse的人:
I know that answers are already saturated, but I'll just add that it appears that this error surfaces after installing Android Studio and returning to Eclipse to build and run your project.
我知道答案已经饱和了，但我要补充的是，在安装Android Studio并返回到Eclipse来构建和运行项目之后，这个错误出现了。
Make sure you close all other instances of ADB that may be running (including Android Studio). Once you've done this if you are still having troubles try killing all ADB server processes and restarting. If you haven't setup a global variable, open terminal and navigate to the platform-tools folder of the Android SDK Eclipse is referencing, then run:
确保关闭所有可能正在运行的ADB实例(包括Android Studio)。一旦您这样做了，如果您仍然有麻烦，尝试杀死所有ADB服务器进程并重新启动。如果您还没有设置全局变量，打开终端并导航到Android SDK Eclipse正在引用的平台工具文件夹，那么运行:
./adb kill-server
./adb start-server
#8
4
I'm running the Android ADT bundle on Windows 8. Both solutions described in this topic (editing the host file and changing the eclipse preferences) did not solve the problem.
我在Windows 8上运行Android ADT包。在本主题中描述的两个解决方案(编辑主机文件和更改eclipse首选项)并没有解决问题。
In my situation the problem has been solved by a de-installation of Java 7 (now using Java 6). The debugger is now working again!
在我的情况下，这个问题已经通过Java 7的反安装(现在使用Java 6)得到了解决。
#9
4
Running two instances of adb (eg eclipse debugger and android studio) at same time causes conflicts as this too
同时运行两个adb实例(如eclipse调试器和android studio)也会导致冲突
#10
3
In my case the problem was that there was a ghost eclipse hanging on background; it was not using any workspace and had no windows, so it was only on process list that I found it. Killing it resolved the issue.
在我的例子中，问题是有一个幽灵eclipse挂在背景上;它没有使用任何工作区，也没有窗口，所以我只在进程列表中找到了它。杀死它解决了问题。
#11
3
On Windows 8 I was batteling with this for some time:
do you have AVG installed? uninstalling AVG did the trick for me
在Windows 8上，我用了一段时间的时间:你安装了AVG吗?卸载AVG对我来说很有用
#12
3
For me, this was due to the fact that I was trying to debug using eclipse yet also running Android Studio. Both programs were trying to monitor android devices on the similar ports. Either quit all IDEs other than one, or modify the port number used for debugging in the IDE preferences so they are not similar.
对我来说，这是因为我正在尝试使用eclipse调试，同时也运行Android Studio。这两个程序都试图在类似的端口上监控android设备。要么退出除一个以外的所有IDE，要么修改IDE首选项中用于调试的端口号，使它们不类似。
#13
2
In my case, it just worked when I killed the Eclipse process, and restart the software.
在我的例子中，当我终止Eclipse进程并重新启动软件时，它就开始工作了。
#14
1
The only fix that really worked for me was uninstalling Java 7 and installing Java 6 on my Windows 8 x64 based machine.
唯一对我有效的修复是卸载Java 7并在基于Windows 8 x64的机器上安装Java 6。
You can download Java 6 from here.
您可以从这里下载Java 6。
#15
1
Try another cable and if that doesn't work try another phone.
试试另一根电缆，如果不行，试试另一部手机。
I wrestled with this and all the tips above for several days. But the connector on my devices was flakey. As a test move the phone and see if you get connections dropping.
我在上面花了好几天的时间来处理这个问题。但是我的设备上的连接器有点不正常。作为一个测试，移动手机，看看是否连接丢失。
Some of the tips such a ADB USB will fix it temporarily and explicitly (re) selecting the device process to debug. But for me the root cause was that the physical connection.
诸如ADB USB之类的一些技巧将临时和显式地修复它，重新选择要调试的设备进程。但对我来说，根本原因是物理连接。
So now with the new device I have no problem ever! A flakey cable would cause the same issue. Good luck! I feel your pain.
所以现在有了新设备，我就没有任何问题了!一个flakey电缆会引起同样的问题。好运！我觉得你的痛苦。
#16
1
On my mac from a terminal:
在我的mac电脑上
$ ./adb kill-server
$ ./adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
I opened the eclipse and set the ddms port to 5037. it works fine.
我打开eclipse并将ddms端口设置为5037。它将正常工作。
#17
0
Based on an Aptana Studio support response, it was confirmed that the Aptana plugin and Android Development Tools collide on this port (i.e. Aptana's Comet server overlapped on this port). Aptana opened a ticket back in 2010.
基于Aptana Studio支持响应，我们确认Aptana插件和Android开发工具在这个端口上发生了碰撞(即Aptana的Comet服务器在这个端口上重叠)。2010年，Aptana开了一张门票。
Unfortunately, it does not appear that Aptana has fixed it yet or made their Comet server port configurable. Changing the port number in eclipse and restarting adb did NOT fix it for me. I finally was forced to uninstall the Aptana plugin.
不幸的是，Aptana似乎还没有修复它或使其Comet服务器端口可配置。更改eclipse中的端口号并重新启动adb并没有为我修复它。我最终*卸载Aptana插件。
#18
0
Worked for me, based on this answer
基于这个答案，我工作了
In Eclipse go to
在Eclipse中去
Window->Preference->Android->DDMS
Then tick "Use ADBHOST" as "127.0.0.1".
然后勾选“使用ADBHOST”为“127.0.0.1”。
Then just restart eclipse
然后重新启动eclipse
#19
0
After hours trying to fix it with java sdks, eclipse.ini file, and all material found on the question, what definetely worked for me :
在尝试用java sdk修复它几个小时之后，eclipse。ini文件，以及所有关于这个问题的资料，什么确实对我有用:
UINSTALLED AVG ANTI-VIRUS
UINSTALLED AVG杀毒
then all ports on DDMS get green, no matter java or Genymotion settings or what the...
然后，DDMS上的所有端口都变成绿色，无论java或Genymotion设置是什么。
#20
0
Maybe it's too late for an answer to this question but i think i have found a fix for it, what i noticed is within the info.plist file > JVMoption (Mac) with in the application package there is two version of java i.e it was showing "1.6*,1.7+" so i just changed it to "1.8*" which is my current java version and now its working for me
也许现在回答这个问题已经太晚了，但是我想我已经找到了一个解决方法，我注意到的是在信息中。plist文件> JVMoption (Mac)在应用程序包中有两个版本的java i。它显示的是“1.6*，1.7+”，所以我把它改成了“1.8*”，这是我当前的java版本，现在它对我很有用
#1
83
In addition to adding "127.0.0.1 localhost" to your hosts file, make the following changes in Eclipse.
除了将“127.0.0.1 localhost”添加到您的主机文件之外，还需要在Eclipse中进行以下更改。
Under Window -> Preferences -> Android -> DDMS:
在窗口下->首选项-> Android -> DDMS:
- Set Base local debugger port to "8601"
- 将基本本地调试器端口设置为“8601”
- Check the box that says "Use ADBHOST" and the value should be "127.0.0.1"
- 勾选“使用ADBHOST”的框，值应为“127.0.0.1”
Thanks to Ben Clayton in the comments for leading me to a solution.
感谢Ben Clayton为我提供了解决方案。
Some Google keywords: Ailment or solution for Nexus S Android debugging with the error message: Can't bind to local 8600 for debugger.
一些谷歌关键字:故障或解决方案的Nexus S Android调试与错误消息:无法绑定到本地8600调试器。
#2
23
Try killing port 8600 with this command:
尝试用这个命令杀死端口8600:
fuser -k 8600/tcp
That fixed it for me.
这帮我搞定了。
#3
15
Don't uninstall, this is just a dumb thing done by the system which as trouble finding localhost it seems. Take a look in here, it's quite easy to fix. I had the same issue a few weeks ago and solved it this way.
不要卸载，这只是系统做的一件蠢事，因为它看起来很难找到本地主机。看看这里，很容易修复。几个星期前我也遇到过同样的问题。
the window Host file that is messed up:
the file is at this place :
C:\WINDOWS\system32\drivers\etc窗口搞砸了主机文件:这个文件在这个地方:C:\WINDOWS\system32\drivers\etc
And should contain this line : 127.0.0.1 localhost
并且应该包含这一行:127.0.0.1 localhost
#4
10
I had the following hosts file
我有以下的主机文件
127.0.0.1 localhost192.168.1.2 localhost
127.0.0.1 localhost 192.168.1.2 localhost
and i started getting the error continously and it was very annoying
我开始不断地得到错误，这很烦人
“Can't bind to local 8600 for debugger”
“Can't bind to local 8601 for debugger”
“Can't bind to local 8602 for debugger” and so on
“无法绑定到本地8600调试器”“无法绑定到本地8601调试器”“无法绑定到本地8602调试器”等等
I deleted the second line from the hosts file 192.168.1.2 localhost and everything is back to normal.
我从主机文件192.168.1.2 localhost中删除了第二行，一切恢复正常。
Hope this helps.
希望这个有帮助。
#5
8
In addition to adding 127.0.0.1 localhost to your hosts file, make the following changes in Eclipse.
除了向主机文件中添加127.0.0.1 localhost之外，还需要在Eclipse中进行以下更改。
Under
下
Window -> Preferences -> Android -> DDMS
窗口->首选项-> Android -> DDMS
Set Base local debugger port to 8601
将基本本地调试器端口设置为8601
Check the box that says Use ADBHOST and the value should be 127.0.0.1 Thanks to Ben Clayton & Doguhan Uluca in the comments for leading me to a solution.
勾选ADBHOST的复选框，其值应该是127.0.0.1，感谢Ben Clayton & Doguhan Uluca在评论中引导我找到解决方案。
Some Google keywords:
一些谷歌关键词:
Ailment or solution for Nexus S Android debugging with the error message: Can't bind to local 8600 for debugger.
Nexus S Android调试的故障或解决方案带有错误消息:无法绑定到本地8600进行调试。
#6
7
I had a similar problem on OSX. It just so happens I had opened two instances of Eclipse so I could refer to some code in another workspace. Eventually I realized the two instances might be interfering with each other so I closed one. After that, I'm no longer seeing the "Can't bind..." error.
我在OSX上遇到了类似的问题。碰巧我打开了两个Eclipse实例，因此我可以在另一个工作区中引用一些代码。最后我意识到这两个实例可能互相干扰，所以我关闭了一个。在那之后，我不再看到“无法绑定…”的错误。
#7
7
For people running Android Studio and Eclipse:
对于运行Android Studio和Eclipse的人:
I know that answers are already saturated, but I'll just add that it appears that this error surfaces after installing Android Studio and returning to Eclipse to build and run your project.
我知道答案已经饱和了，但我要补充的是，在安装Android Studio并返回到Eclipse来构建和运行项目之后，这个错误出现了。
Make sure you close all other instances of ADB that may be running (including Android Studio). Once you've done this if you are still having troubles try killing all ADB server processes and restarting. If you haven't setup a global variable, open terminal and navigate to the platform-tools folder of the Android SDK Eclipse is referencing, then run:
确保关闭所有可能正在运行的ADB实例(包括Android Studio)。一旦您这样做了，如果您仍然有麻烦，尝试杀死所有ADB服务器进程并重新启动。如果您还没有设置全局变量，打开终端并导航到Android SDK Eclipse正在引用的平台工具文件夹，那么运行:
./adb kill-server
./adb start-server
#8
4
I'm running the Android ADT bundle on Windows 8. Both solutions described in this topic (editing the host file and changing the eclipse preferences) did not solve the problem.
我在Windows 8上运行Android ADT包。在本主题中描述的两个解决方案(编辑主机文件和更改eclipse首选项)并没有解决问题。
In my situation the problem has been solved by a de-installation of Java 7 (now using Java 6). The debugger is now working again!
在我的情况下，这个问题已经通过Java 7的反安装(现在使用Java 6)得到了解决。
#9
4
Running two instances of adb (eg eclipse debugger and android studio) at same time causes conflicts as this too
同时运行两个adb实例(如eclipse调试器和android studio)也会导致冲突
#10
3
In my case the problem was that there was a ghost eclipse hanging on background; it was not using any workspace and had no windows, so it was only on process list that I found it. Killing it resolved the issue.
在我的例子中，问题是有一个幽灵eclipse挂在背景上;它没有使用任何工作区，也没有窗口，所以我只在进程列表中找到了它。杀死它解决了问题。
#11
3
On Windows 8 I was batteling with this for some time:
do you have AVG installed? uninstalling AVG did the trick for me
在Windows 8上，我用了一段时间的时间:你安装了AVG吗?卸载AVG对我来说很有用
#12
3
For me, this was due to the fact that I was trying to debug using eclipse yet also running Android Studio. Both programs were trying to monitor android devices on the similar ports. Either quit all IDEs other than one, or modify the port number used for debugging in the IDE preferences so they are not similar.
对我来说，这是因为我正在尝试使用eclipse调试，同时也运行Android Studio。这两个程序都试图在类似的端口上监控android设备。要么退出除一个以外的所有IDE，要么修改IDE首选项中用于调试的端口号，使它们不类似。
#13
2
In my case, it just worked when I killed the Eclipse process, and restart the software.
在我的例子中，当我终止Eclipse进程并重新启动软件时，它就开始工作了。
#14
1
The only fix that really worked for me was uninstalling Java 7 and installing Java 6 on my Windows 8 x64 based machine.
唯一对我有效的修复是卸载Java 7并在基于Windows 8 x64的机器上安装Java 6。
You can download Java 6 from here.
您可以从这里下载Java 6。
#15
1
Try another cable and if that doesn't work try another phone.
试试另一根电缆，如果不行，试试另一部手机。
I wrestled with this and all the tips above for several days. But the connector on my devices was flakey. As a test move the phone and see if you get connections dropping.
我在上面花了好几天的时间来处理这个问题。但是我的设备上的连接器有点不正常。作为一个测试，移动手机，看看是否连接丢失。
Some of the tips such a ADB USB will fix it temporarily and explicitly (re) selecting the device process to debug. But for me the root cause was that the physical connection.
诸如ADB USB之类的一些技巧将临时和显式地修复它，重新选择要调试的设备进程。但对我来说，根本原因是物理连接。
So now with the new device I have no problem ever! A flakey cable would cause the same issue. Good luck! I feel your pain.
所以现在有了新设备，我就没有任何问题了!一个flakey电缆会引起同样的问题。好运！我觉得你的痛苦。
#16
1
On my mac from a terminal:
在我的mac电脑上
$ ./adb kill-server
$ ./adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
I opened the eclipse and set the ddms port to 5037. it works fine.
我打开eclipse并将ddms端口设置为5037。它将正常工作。
#17
0
Based on an Aptana Studio support response, it was confirmed that the Aptana plugin and Android Development Tools collide on this port (i.e. Aptana's Comet server overlapped on this port). Aptana opened a ticket back in 2010.
基于Aptana Studio支持响应，我们确认Aptana插件和Android开发工具在这个端口上发生了碰撞(即Aptana的Comet服务器在这个端口上重叠)。2010年，Aptana开了一张门票。
Unfortunately, it does not appear that Aptana has fixed it yet or made their Comet server port configurable. Changing the port number in eclipse and restarting adb did NOT fix it for me. I finally was forced to uninstall the Aptana plugin.
不幸的是，Aptana似乎还没有修复它或使其Comet服务器端口可配置。更改eclipse中的端口号并重新启动adb并没有为我修复它。我最终*卸载Aptana插件。
#18
0
Worked for me, based on this answer
基于这个答案，我工作了
In Eclipse go to
在Eclipse中去
Window->Preference->Android->DDMS
Then tick "Use ADBHOST" as "127.0.0.1".
然后勾选“使用ADBHOST”为“127.0.0.1”。
Then just restart eclipse
然后重新启动eclipse
#19
0
After hours trying to fix it with java sdks, eclipse.ini file, and all material found on the question, what definetely worked for me :
在尝试用java sdk修复它几个小时之后，eclipse。ini文件，以及所有关于这个问题的资料，什么确实对我有用:
UINSTALLED AVG ANTI-VIRUS
UINSTALLED AVG杀毒
then all ports on DDMS get green, no matter java or Genymotion settings or what the...
然后，DDMS上的所有端口都变成绿色，无论java或Genymotion设置是什么。
#20
0
Maybe it's too late for an answer to this question but i think i have found a fix for it, what i noticed is within the info.plist file > JVMoption (Mac) with in the application package there is two version of java i.e it was showing "1.6*,1.7+" so i just changed it to "1.8*" which is my current java version and now its working for me
也许现在回答这个问题已经太晚了，但是我想我已经找到了一个解决方法，我注意到的是在信息中。plist文件> JVMoption (Mac)在应用程序包中有两个版本的java i。它显示的是“1.6*，1.7+”，所以我把它改成了“1.8*”，这是我当前的java版本，现在它对我很有用