I doesn't understand the real meaning of this option, but it does following: Any php script automatically trying to connect to debugger (netbeans in my case).
Second problem was caused by option in my nf: xdebug.remote_autostart=1, it should be xdebug.remote_autostart=0. It should be placed to host's config file, or to /etc/nginx/fastcgi_params (in Debian) First problem (with 504 error) could be solved by nginx option fastcgi_read_timeout, for example, it could be fastcgi_read_timeout 600 for tell nginx that it should wait for 600 seconds. Thank you, everyone who tried to think in the direction of my problem. If anyone faced this problems, or have working config for using with nginx+php-fpm+xdebug+netbeans - please help me :) But in this case, I'm fighting with this ones for some MONTHS without luck. I don't like to disturb anyone with my problems, and always trying to solve it by myself. Php-fpm's logs doesn't contains ANY error messages. Record in nginx's error log file, when it cannot wait for script being debugged, or other script, locked by the problem #3, mentioned early:Ĥ 14:40:16 4822#0: *111 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.100.1, server: intranet.local, request: "GET /adminer.php?username=root&db=devel&table=user HTTP/1.1", upstream: "fastcgi://127.0.0.1:9999", host: "intranet.local", referrer: " " netbeans: options, that was just the same with apache server:. Php5-xdebug: 5.3.26-1~d (from dotdeb repository) Php5-fpm: 5.3.26-1~d (from dotdeb repository) It seems like the problem appears after some time of active debugging. Now, when I writing this question, I made some investigations, and found, that, if I start debug session for some seconds, after that stop it, and start again - it starts normally. If I see this behavior, I could just stop xdebug debug session in netbeans, and all other scripts starting to operate normally. After some time, I noticed, that my adminer (placed on intranet.local/adminer.php) doesnt run, the browser tries to load page for some time, and than shows "504 Gateway timeout error". For example, I start debug session on my website's and working with it. In come cases, that I couldn't understand, the debugging is "turning on for all php scripts" and prevent's any other scripts to run. After restart of netbeans the debug session could be started again normally. My debug session could be run only once, so, if I stop it, and try to launch debugging again, netbeans couldn't accept connection from xdebug (it writes "Waiting for xdebug connection" and it is forever). Though, it is not a very important for me, because of debugging session itself continues to run, and it's just a little uncomfortable thing. I've tried lots of recommendations for solve this, but no luck. My debug session could be very long (much more than 30 seconds) and it seems, that nginx couldn't wait so long, it shows "504 Gateway timeout error". But, when I moved to nginx+php_fpm+xdebug+netbeans I've experienced some problems with debugging. In the past, I've used apache+mod_php+xdebug+netbeans for development my website (server is my local machine, running Debian Squeeze), with pleasure - xdebug worked just as expected, debug sessions could be started and stopped any time, when I need it.
0 kommentar(er)
