轮询成功,但出错:操作正在进行中(29)。当Xdebug尝试从docker容器连接到PhpStorm时

时间:2019-02-19 12:46:32

标签: docker phpstorm xdebug

我正在尝试调试CLI脚本,而Xdebug无法连接到PhpStorm。
我在Xdebug远程日志中看到错误Operation now in progress (29).
我确定Xdebug配置正确,但是我不知道如何调试PhpStorm。

https://xdebug.org/wizard.php生成的phpinfo()的摘要

Tailored Installation Instructions
Summary
Xdebug installed: 2.6.1
Server API: Command Line Interface
Windows: no
Zend Server: no
PHP Version: 7.1.24
Zend API nr: 320160303
PHP API nr: 20160303
Debug Build: no
Thread Safe Build: no
OPcache Loaded: no
Configuration File Path: /usr/local/etc/php
Configuration File: /usr/local/etc/php/php.ini
Extensions directory: /usr/local/lib/php/extensions/no-debug-non-zts-20160303
You're already running the latest Xdebug version

Xdebug日志

Log opened at 2019-02-19 11:59:37
I: Connecting to configured address/port: 46.201.50.194:9000.
W: Creating socket for '46.201.50.194:9000', poll success, but error: Operation now in progress (29).
E: Could not connect to client. :-(
Log closed at 2019-02-19 11:59:37

Xdebug配置

xdebug

xdebug support => enabled
Version => 2.6.1
IDE Key => PHPSTORM

Supported protocols
DBGp - Common DeBuGger Protocol

Directive => Local Value => Master Value
xdebug.auto_trace => Off => Off
xdebug.cli_color => 0 => 0
xdebug.collect_assignments => Off => Off
xdebug.collect_includes => On => On
xdebug.collect_params => 0 => 0
xdebug.collect_return => Off => Off
xdebug.collect_vars => Off => Off
xdebug.coverage_enable => On => On
xdebug.default_enable => On => On
xdebug.dump.COOKIE => no value => no value
xdebug.dump.ENV => no value => no value
xdebug.dump.FILES => no value => no value
xdebug.dump.GET => no value => no value
xdebug.dump.POST => no value => no value
xdebug.dump.REQUEST => no value => no value
xdebug.dump.SERVER => no value => no value
xdebug.dump.SESSION => no value => no value
xdebug.dump_globals => On => On
xdebug.dump_once => On => On
xdebug.dump_undefined => Off => Off
xdebug.extended_info => On => On
xdebug.file_link_format => no value => no value
xdebug.filename_format => no value => no value
xdebug.force_display_errors => Off => Off
xdebug.force_error_reporting => 0 => 0
xdebug.gc_stats_enable => Off => Off
xdebug.gc_stats_output_dir => /tmp => /tmp
xdebug.gc_stats_output_name => gcstats.%p => gcstats.%p
xdebug.halt_level => 0 => 0
xdebug.idekey => PHPSTORM => PHPSTORM
xdebug.max_nesting_level => 256 => 256
xdebug.max_stack_frames => -1 => -1
xdebug.overload_var_dump => 2 => 2
xdebug.profiler_aggregate => Off => Off
xdebug.profiler_append => Off => Off
xdebug.profiler_enable => Off => Off
xdebug.profiler_enable_trigger => Off => Off
xdebug.profiler_enable_trigger_value => no value => no value
xdebug.profiler_output_dir => /tmp => /tmp
xdebug.profiler_output_name => cachegrind.out.%p => cachegrind.out.%p
xdebug.remote_addr_header => no value => no value
xdebug.remote_autostart => On => On
xdebug.remote_connect_back => Off => Off
xdebug.remote_cookie_expire_time => 3600 => 3600
xdebug.remote_enable => On => On
xdebug.remote_handler => dbgp => dbgp
xdebug.remote_host => 127.0.0.1 => localhost
xdebug.remote_log => /app/xdebug.log => no value
xdebug.remote_mode => req => req
xdebug.remote_port => 9000 => 9000
xdebug.remote_timeout => 200 => 200
xdebug.scream => Off => Off
xdebug.show_error_trace => Off => Off
xdebug.show_exception_trace => Off => Off
xdebug.show_local_vars => Off => Off
xdebug.show_mem_delta => Off => Off
xdebug.trace_enable_trigger => Off => Off
xdebug.trace_enable_trigger_value => no value => no value
xdebug.trace_format => 0 => 0
xdebug.trace_options => 0 => 0
xdebug.trace_output_dir => /tmp => /tmp
xdebug.trace_output_name => trace.%c => trace.%c
xdebug.var_display_max_children => 128 => 128
xdebug.var_display_max_data => 512 => 512
xdebug.var_display_max_depth => 3 => 3

enter image description here

5 个答案:

答案 0 :(得分:2)

Xdebug无法连接到PhpStorm,因为我的外部主机ip无法访问PhpStorm。 我如何调试它。 首先,我从Docker容器检查了PhpStorm侦听端口(本例中为9000)

nc -vz external_ip 9000

它得到了(tcp) failed: Connection refused
我从主机尝试了同样的方法,也收到了错误 然后我从主持人那里尝试了

nc -vz localhost 9000

我得到了[tcp/*] succeeded! 因此,xdebug.remote_host中的问题可能不在PhpStorm中

我在容器中找到了主机ip

netstat -nr | grep '^0\.0\.0\.0' | awk '{print $2}'

将其放在xdebug.remote_host中,现在可以正常工作

感谢@LazyOne

答案 1 :(得分:1)

就我而言,我只需设置以下xdebug conf:

xdebug.remote_connect_back=0
xdebug.remote_host=host.docker.internal

host.docker.internal应该“神奇地”找到主机的IP(参见documentation)。请注意,这需要Docker v18.03 +,目前仅适用于Mac和Windows主机。

答案 2 :(得分:1)

可能是您的xdebug.remote_port 9000被php-fpm使用。您尝试更改其他端口。示例xdebug.remote_port = 9001,并且launch.json文件中的端口仍然是port = 9000

答案 3 :(得分:0)

如果有人不想硬编码或修改他们的 docker、Dockerfile 或撰写文件(也许有人使用 2.x xdebug,它不支持环境变量)。通过在浏览器上使用标头修改扩展程序添加标头X-Forwarded-For 以设置$_SERVER['HTTP_X_FORWARDED_FOR'] 是一种非常方便的方法。不要忘记配置xdebug.remote_connect_back=1

Dockerfile

FROM  php:7.1-apache

RUN yes | pecl install xdebug-2.5.5 \
    && echo "zend_extension=$(find /usr/local/lib/php/extensions/ -name xdebug.so)" > /usr/local/etc/php/conf.d/xdebug.ini \
    && echo "xdebug.remote_port=9000" >> /usr/local/etc/php/conf.d/xdebug.ini \
    && echo "xdebug.remote_enable=1" >> /usr/local/etc/php/conf.d/xdebug.ini \
    && echo "xdebug.remote_connect_back=1" >> /usr/local/etc/php/conf.d/xdebug.ini \
    && echo "xdebug.remote_log=/tmp/xdebug.log" >> /usr/local/etc/php/conf.d/xdebug.ini \
    && echo "xdebug.remote_autostart=off" >> /usr/local/etc/php/conf.d/xdebug.ini

ModHeader 扩展 Xdebug helper

xdebug.log

Log opened at 2021-07-06 16:06:59
I: Checking remote connect back address.
I: Checking header 'HTTP_X_FORWARDED_FOR'.
I: Checking header 'REMOTE_ADDR'.
I: Remote address found, connecting to 172.17.0.1:9000.
W: Creating socket for '172.17.0.1:9000', poll success, but error: Operation now in progress (29).
E: Could not connect to client. :-(
Log closed at 2021-07-06 16:06:59

Log opened at 2021-07-06 16:07:40
I: Checking remote connect back address.
I: Checking header 'HTTP_X_FORWARDED_FOR'.
I: Remote address found, connecting to 172.30.112.1:9000.
I: Connected to client. :-)

答案 4 :(得分:0)

对我来说,修复此错误的方法是在 PhpStorm 中单击电话图标两次以禁用然后重新启用侦听调试连接。

它不应该改变任何东西,但它起作用了,因为在此之前我修复了许多其他问题,其中一个是端口 9003 被其他东西阻塞了。显然,PhpStorm 在无法使用指定端口时不会发出警告,因此在解决其他问题后,可能需要重新启动侦听调试连接。