Open kevinjavitz opened 1 year ago
Actually this can be closed sorry, I updated to devilbox 3.0.0 beta 3 and magically the error is gone and all is working fine, so anyone has this same error I recommend updating using the instructions here https://devilbox.readthedocs.io/en/latest/maintenance/update-the-devilbox.html
actually still doing it, just not quite as frequently, even when xdebug debugging chrome extension is set to disabled
my php.ini:
xdebug.mode = debug
;xdebug.remote_handler = dbgp
;xdebug.start_with_request = yes
xdebug.scream = off
; How to connect
xdebug.client_port = 9003
xdebug.client_host = 172.19.240.1
xdebug.discover_client_host = true
; Logging
; xdebug.log = /var/log/php/xdebug.log
; xdebug.log_level = 7
; IDE Configuration
xdebug.idekey = PHPSTORM
;xdebug.idekey = VSCODE
; vim: set ft=dosini:
max_input_time = 0
max_execution_time = 0
error_reporting = E_ALL & ~E_DEPRECATED
xmlrpc_errors = Off
report_memleaks = On
display_errors = On
display_startup_errors = On
html_errors = On
Have you already looked into this bug?
(Optional) Error message
[Mon Jul 10 03:29:12.162862 2023] [proxy_fcgi:error] [pid 528:tid 140006501874488] (11)Resource temporarily unavailable: [client 172.16.238.1:55990] AH01075: Error dispatching request to : (reading input brigade)
What went wrong?
When Xdebug is enabled I constantly am getting 400 bad request errors when not step debugging, the error message in apache 2.4 is:
[Mon Jul 10 03:29:12.162862 2023] [proxy_fcgi:error] [pid 528:tid 140006501874488] (11)Resource temporarily unavailable: [client 172.16.238.1:55990] AH01075: Error dispatching request to : (reading input brigade)
Xdebug log is: [1324] Log opened at 2023-07-10 03:32:15.496884 [1324] [Config] INFO: Trigger value for 'XDEBUG_TRIGGER' not found, falling back to 'XDEBUG_SESSION' [1324] [Config] INFO: Trigger value for 'XDEBUG_SESSION' not found, so not activating [1324] [Config] INFO: Trigger value for 'XDEBUG_TRIGGER' not found, falling back to 'XDEBUG_SESSION' [1324] [Config] INFO: Trigger value for 'XDEBUG_SESSION' not found, so not activating [1324] [Config] INFO: Trigger value for 'XDEBUG_TRIGGER' not found, falling back to 'XDEBUG_SESSION' [1324] [Config] INFO: Trigger value for 'XDEBUG_SESSION' not found, so not activating [1324] [Config] INFO: Trigger value for 'XDEBUG_TRIGGER' not found, falling back to 'XDEBUG_SESSION' [1324] [Config] INFO: Trigger value for 'XDEBUG_SESSION' not found, so not activating [1324] [Config] INFO: Trigger value for 'XDEBUG_TRIGGER' not found, falling back to 'XDEBUG_SESSION' [1324] [Config] INFO: Trigger value for 'XDEBUG_SESSION' not found, so not activating [1324] Log closed at 2023-07-10 03:32:15.569692
I am wondering if it's possible to update xdebug to version 3.2.1? I tried running docker-compose pull but it did not update.
Expected behaviour
No 400 Bad Request Error
How can we reproduce the bug?
Using PHP 8.1.13 (from Devilbox 2.4.0) and WordPress. Using WSL2 with docker installed inside of it.
Host Operating System
Linux
Host Platform (amd64, arm64, other)
amd64
(Linux only) Is SELinux enabled?
Yes, SELinux is enabled
Docker version
23.0.4, build f480fb1
Docker Compose version
1.29.2, build 5becea4c
Devilbox version
1.29.2, build 5becea4c
Have you removed stopped containers before starting?
Yes
Have you pulled latest Docker images before starting?
Yes
Devilbox start command
docker-compose up -d
Config: .env file
Config: docker-compose.override.yml
No response
Config: ./check-config.sh
Log: docker-compose logs
(Optional) Additional information
No response