0
455
ViewsXdebug: [Paso de depuración] No se pudo conectar al cliente de depuración. Intenté: localhost: 9003 (retroceso a través de xdebug.client_host/xdebug.client_port) :-(
¿Cuál es la solución de este mensaje para xdebug ang php?
Xdebug: [Step Debug] Could not connect to debugging client. Tried: localhost:9003 (fallback through xdebug.client_host/xdebug.client_port) :-( Este mensaje aparece cuando ejecuto la composer update en WSL2 instalado con UBUNTU 20.01 .
Mi versión actual de php es php8 y xdebug3
Actualizar:
Esta es la sección de depuración x
xdebug __ __ _ _ \ \ / / | | | | \ V / __| | ___| |__ _ _ __ _ > < / _` |/ _ \ '_ \| | | |/ _` | / . \ (_| | __/ |_) | |_| | (_| | /_/ \_\__,_|\___|_.__/ \__,_|\__, | __/ | |___/ Version => 3.0.1 Support Xdebug on Patreon, GitHub, or as a business: https://xdebug.org/support Feature => Enabled/Disabled Development Aids => ✘ disabled Coverage => ✘ disabled GC Stats => ✘ disabled Profiler => ✘ disabled Step Debugger => ✔ enabled Tracing => ✘ disabled Debugger => enabled IDE Key => Directive => Local Value => Master Value xdebug.auto_trace => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.auto_trace" => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.auto_trace" xdebug.cli_color => 0 => 0 xdebug.client_discovery_header => no value => no value xdebug.client_host => localhost => localhost xdebug.client_port => 9003 => 9003 xdebug.cloud_id => no value => no value xdebug.collect_assignments => Off => Off xdebug.collect_includes => This setting has been removed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#removed-"xdebug.collect_includes" => This setting has been removed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#removed-"xdebug.collect_includes" xdebug.collect_params => 0 => 0 xdebug.collect_return => Off => Off xdebug.collect_vars => This setting has been removed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#removed-"xdebug.collect_vars" => This setting has been removed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#removed-"xdebug.collect_vars" xdebug.connect_timeout_ms => 200 => 200 xdebug.coverage_enable => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.coverage_enable" => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.coverage_enable" xdebug.default_enable => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.default_enable" => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.default_enable" xdebug.discover_client_host => 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.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 => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.gc_stats_enable" => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.gc_stats_enable" xdebug.gc_stats_output_dir => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.gc_stats_output_dir" => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.gc_stats_output_dir" xdebug.gc_stats_output_name => gcstats.%p => gcstats.%p xdebug.halt_level => 0 => 0 xdebug.idekey => no value => no value xdebug.log => no value => no value xdebug.log_level => 7 => 7 xdebug.max_nesting_level => 256 => 256 xdebug.max_stack_frames => -1 => -1 xdebug.mode => debug => debug xdebug.output_dir => /mnt/c/www/traces => /mnt/c/www/traces xdebug.overload_var_dump => This setting has been removed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#removed-"xdebug.overload_var_dump" => This setting has been removed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#removed-"xdebug.overload_var_dump" xdebug.profiler_append => Off => Off xdebug.profiler_enable => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.profiler_enable" => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.profiler_enable" xdebug.profiler_enable_trigger => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.profiler_enable_trigger" => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.profiler_enable_trigger" xdebug.profiler_enable_trigger_value => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.profiler_enable_trigger_value" => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.profiler_enable_trigger_value" xdebug.profiler_output_dir => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.profiler_output_dir" => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.profiler_output_dir" xdebug.profiler_output_name => cachegrind.out.%p => cachegrind.out.%p xdebug.remote_autostart => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.remote_autostart" => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.remote_autostart" xdebug.remote_connect_back => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.remote_connect_back" => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.remote_connect_back" xdebug.remote_enable => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.remote_enable" => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.remote_enable" xdebug.remote_host => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.remote_host" => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.remote_host" xdebug.remote_log => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.remote_log" => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.remote_log" xdebug.remote_log_level => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.remote_log_level" => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.remote_log_level" xdebug.remote_mode => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.remote_mode" => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.remote_mode" xdebug.remote_port => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.remote_port" => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.remote_port" xdebug.remote_timeout => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.remote_timeout" => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.remote_timeout" 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 => This setting has been removed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#removed-"xdebug.show_mem_delta" => This setting has been removed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#removed-"xdebug.show_mem_delta" xdebug.start_upon_error => default => default xdebug.start_with_request => 1 => 1 xdebug.trace_enable_trigger => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.trace_enable_trigger" => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.trace_enable_trigger" xdebug.trace_enable_trigger_value => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.trace_enable_trigger_value" => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.trace_enable_trigger_value" xdebug.trace_format => 0 => 0 xdebug.trace_options => 0 => 0 xdebug.trace_output_dir => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.trace_output_dir" => This setting has been changed, see the upgrading guide at https://xdebug.org/docs/upgrade_guide#changed-"xdebug.trace_output_dir" xdebug.trace_output_name => trace.%c => trace.%c xdebug.trigger_value => no value => no value xdebug.var_display_max_children => 128 => 128 xdebug.var_display_max_data => 512 => 512 xdebug.var_display_max_depth => 3 => 34 answers
Answer question0
De la documentación de Xdebug sobre este tipo de errores:
Ocurre cuando Xdebug intenta conectarse a un cliente de depuración para iniciar una sesión de depuración.
El depurador no pudo establecer una conexión con el cliente. El mensaje de error indica qué combinaciones de host y puerto se probaron y mediante qué opciones de configuración se llegó a esa conclusión.
Un ejemplo:
No se pudo conectar con el cliente de depuración. Probado:
::1:9003(del encabezado HTTPREMOTE_ADDR),localhost:9003(retroceso a travésxdebug.client_host/xdebug.client_port)Este mensaje indica que Xdebug primero intentó usar
::1:9003(host local de IPv6) desde el encabezado REMOTE_ADDR, y luego recurrió alocalhost:9003como estaba configurado conxdebug.client_hostyxdebug.client_port.Las soluciones sugeridas:
- Compruebe si su cliente de depuración está escuchando en la dirección y el puerto indicados. En Linux y OSX, puede usar
netstat -a -n | grep LISTENpara verificar.- Cambie
xdebug.client_hosty/oxdebug.client_porta la dirección/nombre de host y puerto correctos donde escucha el cliente de depuración.
0
Lo que causa ese mensaje en primer lugar:
Tiene xdebug.start_with_request = yes (que es lo mismo que xdebug.remote_autostart = yes para Xdebug v2). Esta opción le dice a Xdebug que intente depurar cada solicitud/secuencia de comandos sin importar el indicador "depurarme".
Si Xdebug no puede conectarse al cliente de depuración (valores de xdebug.client_host y xdebug.client_port .. o host detectado automáticamente si xdebug.discover_client_host está habilitado), entonces se lo notifica.
Cómo evitar que aparezca en mi pantalla/en la salida:
Xdebug utiliza rutinas estándar de PHP para escribir dichas advertencias (por ejemplo , la función estándar de PHP error_log() ). Normalmente, dicho mensaje se escribirá en el registro de errores estándar de PHP . Parece que no lo tiene configurado en su php.ini (valor vacío), por lo tanto, PHP lo envía a su salida estándar (por lo que aún puede tener la oportunidad de verlo, ya que podría ser importante).
La solución es apuntar la configuración ini de error_log de PHP a alguna ubicación válida para que pueda leerla cuando sea necesario (la ruta depende de su sistema operativo y distribución, por ejemplo, error_log = /var/log/php_error.log sería muy común). Si no necesita dicho registro en absoluto (tiene otro sistema de registro en su lugar), use /dev/null o algo similar en su lugar.
También puede probar xdebug.log_level = 0 , pero esto debería evitar que Xdebug registre nada, incluso si especifica xdebug.log .
Consulte también esta explicación del autor de Xdebug sobre "por qué funciona de esta manera": https://stackoverflow.com/a/65670743/783119
0
Estoy usando: xdebug.start_with_request=trigger para activar xdebug cuando lo necesito (con el uso de la extensión xdebug del navegador para la depuración del servidor web).
O si necesito depurar el script php (usando cli), uso phpstorm con una configuración como esta:
Con este enfoque, no obtengo este error y puedo usar los registros de xdebug como siempre.
0
Deshabilite la extensión del navegador xdebug cuando no la esté usando.
Yo uso el depurador VSCode. Cuando la depuración estaba desactivada en el IDE, veía el error en el registro en cada visita a la página porque la extensión de mi navegador Chrome aún intentaba invocar xdebug.
Esto sucede a pesar de tener una buena configuración de php.ini para xdebug como:
xdebug.mode=debugo
xdebug.start_with_request=triggerAmbos documentados aquí: Xdebug: Documentación