When working with Xdebug 3 in CLI, it constantly reports the message when there are no breakpoints set:
"Xdebug: [Step Debug] Could not connect to debugging client. Tried: localhost:9003 (through xdebug.client_host/xdebug.client_port) :-("
Is there a way to disable that message form showing in CLI?
Unfortunately, the only way to disable this error is to disable generally ALL errors & warnings in xdebug.ini:
xdebug.log_level = 0
Hopefully there are other ways in future xdebug versions (imho this should only be a weak warning).
EDIT: As LazyOne mentioned, it's also possible to set an value for error_log in php.ini, for example /var/log/php_error.log. With that change, the log entries are written to this file and not sent to stderr.
xdebug.log_level value, which is 7). Perhaps it's some output redirection (error output stream or alike). –
Celtuce echo "<?php" | php on Ubuntu with default xdebug.log_level and without listing to PHP debug connection, I get this message: "Xdebug: [Step Debug] Could not connect to debugging client. Tried: localhost:9003 (through xdebug.client_host/xdebug.client_port) :-(" –
Spates xdebug_info() output) -- you can redact IP/host name or other private parts (share it as a link). I'm interested to know why it happens. –
Celtuce error_log PHP settings. (e.g. from phpinfo(); output or just ini_get('error_log');). I believe it will be empty (or perhaps some incorrect location). If you set it to some proper location (e.g. something like /var/log/php_error.log or maybe even /dev/null - -depends n your OS and distro) then you should not see such error in the first place. Can you do that and check the same that you did in your first comment here? –
Celtuce In my case the problem was that Xdebug tried to run on every request and since I didn't do debugging on every page refresh errors like Xdebug: [Step Debug] Could not connect to debugging client were reported and are understandable.
The most obvious solution with xdebug.log_level = 0 of course worked, but this was too broad and too blind way to fight this for me. So I checked the documentation, and the best way to get rid of that error in my opinion is to tell Xdebug when it should really run and when not, so the right option in my case is:
xdebug.start_with_request = trigger
as the documentation says:
The functionality only gets activated when a specific trigger is present when the request starts.
The name of the trigger is XDEBUG_TRIGGER, and Xdebug checks for its presence in either $_ENV (environment variable), $_GET or $_POST variable, or $_COOKIE (HTTP cookie name).
and I recommend checking at least that part of their docs because there's more info and you can even do more fine tuning if needed.
+50 –
Genovese Starting from version 3.1, xdebug does not redirect its logs to php logs if you set the path to the log file. In my case, I use the following settings and these messages no longer dazzle the eyes in the console
xdebug.log=/var/www/var/log/xdebug.log
xdebug.log_level=3
PR for this issue: https://github.com/xdebug/xdebug/pull/738
If you are running a PHP script or command you can set INI entry using -d:
php -d xdebug.log_level=0 your_sript.php
if you only need to suppress the output for one call you can use this - e.g. show version:
XDEBUG_CONFIG="log_level=0" composer -v
Changing the php.ini 'xdebug.start_with_request' form 'yes' to 'trigger' solved my issue , I use MAMP.
xdebug.start_with_request = trigger
This is what you need:
xdebug.mode=debug
xdebug.start_with_request=yes
xdebug.discover_client_host=1
© 2022 - 2024 — McMap. All rights reserved.
phpinfo()or justxdebug_info(). – Celtucephpinfo()/php -ioutput I may compare with mine... as I do not see such warnings here when I do the same (I'm on Windows ... but I doubt it will make any difference here). Right now I believe it could be one of thexdebug.XXXoptions .. or perhaps howerror_logis handled (because that's where such message gets normally written). – Celtucexdebug.remote_autostart = yesis Xdebug v2 option while Xdebug v3 usesxdebug.start_with_request = yesinstead xdebug.org/docs/upgrade_guide. I've checked all options I could think of .. and could not locate the one that would force such entry to be printed in the normal output (except some sort of PHP's error log redirection .. as that's where such message normally goes). No better ideas from me (except perhaps checking Xdebug's Bug tracker for possible tickets) and thereforexdebug.log_level = 0sounds like a good solution here. – Celtuceerror_logsetting properly. – Celtuce