循序渐进：如何对客户端IDE进行Xdebug故障排除连接 [英] Step-by-step: How to do Xdebug troubleshooting connection to client IDE
问题描述
背景
将Xdebug与PHP和Komodo IDE以及Eclipse PDT一起使用。
Using Xdebug with PHP and Komodo IDE, and Eclipse PDT.
Xdebug已安装在服务器上并正常运行。这是因为Xdebug代码命令在插入服务器上的PHP文件时按预期工作。
Xdebug is installed on the server and working properly. This is confirmed because the Xdebug code commands work as expected when inserted into PHP files on the server.
问题
连接到客户端工作站不起作用，很难确定原因，因为它失败了多个IDE。
Connecting to the client workstation is not working, and it is difficult to determine why because it fails with multiple IDEs.
问题
如果您知道Xdebug已安装并在服务器上运行，那么请逐步检查清单以解决问题。客户端无法连接。
It would be nice to have a step-by-step checklist to troubleshoot the case where you know Xdebug is installed and working on the server, but the client does not connect.
任何人都可以帮忙添加这个以制作全面的故障排除清单吗？
Can anyone help add to this to make a comprehensive troubleshooting checklist?
具体来说，是否有任何简单的方法来确保网络流量到达客户端，并按照IDE期望查看数据的方式正确格式化？
Specifically, is there any bare-bones way to make sure the network traffic is reaching the client, and is correctly formatted in the way the IDE expects to see the data?
-
SSH进入网络主机并尝试联系客户端：
SSH into web host and try to reach the client:
- 可以托管客户端吗？ （ping -c 5 xxx.xxx.xxx.xxx）
- 可以托管到达端口9000吗？ （nmap -p 9000 xxx.xxx.xxx.xxx）
- 如果以上两个成功，输出应该是什么？
- 如果以上两个失败，下一个故障排除步骤是什么？
- can host reach client at all? (ping -c 5 xxx.xxx.xxx.xxx )
- can host reach port 9000? (nmap -p 9000 xxx.xxx.xxx.xxx)
- if the above two succeed, what should the output be?
- if the above two fail, what is the next troubleshooting step?
验证客户端上基于软件的防火墙的设置
Verify settings of software-based firewall on client
目标
目标是找到客户端计算机上的人至少能够解决的问题确认某些到达客户端而不必确定IDE是否是问题，因为IDE是另一个可能引入问题的复杂程度。
The goal is to find some solution where the person on the client machine can at least confirm that something is reaching the client without having to determine whether the IDE is the problem, since IDE is another level of complexity that may be introducing problems.
推荐答案
这是我肯定想要包含在Xdebug文档中的内容。我认为最好让很多人就此进行合作，所以我在xdebug.org github存储库中创建了一个文件（ https://github.com/derickr/xdebug.org/blob/master/html/docs/tutorials/troubleshooting.rest ）收集提示。随意分叉和扩展！
This is something I would definitely want to include in the Xdebug documentation. I think it would work best to have many people collaborate on this, so I've created a file in the xdebug.org github repository (https://github.com/derickr/xdebug.org/blob/master/html/docs/tutorials/troubleshooting.rest) to collect tips. Feel free to fork and extend!
在Xdebug方面，在即将发布的版本（2.2）中，它已经在其xdebug.remote_log文件中转储了一些额外的诊断，例如它是否尝试连接以及连接是被接受还是被拒绝。
On the Xdebug side, in the upcoming version (2.2) it already dumps in its xdebug.remote_log file a couple of extra diagnostics such as whether it tried to connect and whether the connection was accepted or denied.
这篇关于循序渐进：如何对客户端IDE进行Xdebug故障排除连接的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
