Php xDebug在端口9000(nginx)上随机启动大量连接

Php xDebug在端口9000(nginx)上随机启动大量连接,php,nginx,xdebug,Php,Nginx,Xdebug,我在xdebug中遇到了以下问题: 当我尝试连接到xDebug并通过从浏览器发送请求开始调试时,使用?xDebug_SESSION_start=netbeans xDebug,会有很多连接到端口9000,如netstat-a | grep 9000 这似乎是随机发生的。如果幸运的话,netstat-a | grep9000只显示一个连接,一切正常。但当存在多个连接时,调试将无法工作。唯一的解决方案是停止调试器,并终止端口9000上的所有连接 问题是在不久前从Apache切换到Nginx时出现的

我在xdebug中遇到了以下问题:

当我尝试连接到xDebug并通过从浏览器发送请求开始调试时,使用
?xDebug_SESSION_start=netbeans xDebug
,会有很多连接到端口9000,如
netstat-a | grep 9000

这似乎是随机发生的。如果幸运的话,netstat-a | grep9000只显示一个连接,一切正常。但当存在多个连接时,调试将无法工作。唯一的解决方案是停止调试器,并终止端口9000上的所有连接

问题是在不久前从Apache切换到Nginx时出现的

nginx版本:nginx/1.6.1 使用PHP5.5.15在Ubuntu服务器12.04.5 LTS上运行

xdebug配置:

xdebug support => enabled
Version => 2.2.5
IDE Key => marijn

Supported protocols => Revision
DBGp - Common DeBuGger Protocol => $Revision: 1.145 $

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.idekey => no value => no value
xdebug.max_nesting_level => 100000 => 100000
xdebug.overload_var_dump => On => On
xdebug.profiler_aggregate => Off => Off
xdebug.profiler_append => Off => Off
xdebug.profiler_enable => Off => Off
xdebug.profiler_enable_trigger => On => On
xdebug.profiler_output_dir => /tmp => /tmp
xdebug.profiler_output_name => cachegrind.out.%p => cachegrind.out.%p
xdebug.remote_autostart => Off => Off
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 => localhost => localhost
xdebug.remote_log => no value => no value
xdebug.remote_mode => req => req
xdebug.remote_port => 9000 => 9000
xdebug.scream => 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_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

我已经能够重现这个问题,因此,当我在Chrome中启动调试会话(使用扩展名'xDebug Helper')比在netbeans中启动调试会话更早时,就会出现这个问题

因此,首先从netbeans启动调试会话,然后在chrome中启动调试会话,就解决了这个问题