martomo
Time-out connecting to client. :-(
Hello, I've been trying to make xdebug work from a Vagrant ubuntu guest to a Windows 8 host with no luck. Tried all I found online with no luck.
You will finde more detail below, the main issue is that at some point of the debug session execution the xdebug extension starts loging connection timeouts to the client. It does initially start the sesison, and even receives the test breakpoint I put in Sublime, but when the extension should start sending debug info to the client, those connecitons time out.
I tried all I found out there, from changes in the config files, to setting up a private network between host and guest, not much improvement, since it does not seem to be a networking issue (the initial communication is succesful).
So, I'm reaching out for help. Thanks in advanced!
What operation system(s) and version of Sublime Text are you using? Windows 8 is the host, Ubuntu 12.4 the gest, running on Vagrant. Sublime Text 2 is the version of the IDE.
How did you install SublimeTextXdebug, Package Control, git clone or download? Package control.
Are you trying to debug the script remotely or locally, through browser or command line? Remotely, through browser.
Which version of Xdebug extension do you have? 2.2.5
Can you post your project/settings file and Xdebug configuration from the *.ini located on your server. My project file looks like this: { "folders": [ { "follow_symlinks": true, "path": "C:\backup\git-wc\hm-wc" } ], "settings": { "xdebug": { "close_on_stop": true, "path_mapping": { "/var/www/hm/user/": "C:\backup\git-wc\hm-wc\hm\user" }, "super_globals": true, "url": "http://dev.hm.local/index.php", "ide_key": "sublime.xdebug", "port": 9001 } } }
/etc/php5/apache2/php.ini has in it: ;;;;;;;;;;;;;;;;;;;;;;;;;; ; Added to enable Xdebug ; ;;;;;;;;;;;;;;;;;;;;;;;;;; [xdebug] zend_extension="/usr/lib/php5/20090626+lfs/xdebug.so" xdebug.default_enable = 1 xdebug.idekey = "vagrant" xdebug.remote_enable = 1 xdebug.remote_autostart = 0 xdebug.remote_port = 9001 xdebug.remote_handler=dbgp xdebug.remote_log="/var/log/xdebug/xdebug.log" xdebug.remote_host=10.0.2.2 ; xdebug.remote_connect_back = 1;
Does the console window (Ctrl+`) show any more information regarding the error? Nop, the error shows the xdebug extension in the guest is not reaching Sublime in the host, so, not much in the Sublime console at all.
Finally, here is a brief exerp of what xdebug writes in the log, notice the initial communication works, but then for some reason it starts throwing timeouts:
Log opened at 2014-09-17 02:41:16
I: Connecting to configured address/port: 10.0.2.2:9001.
I: Connected to client. :-)
->
<- feature_set -i 1 -v 1 -n show_hidden
->
<- feature_set -i 2 -v 32 -n max_children
->
<- feature_set -i 3 -v 1024 -n max_data
->
<- feature_set -i 4 -v 1 -n max_depth
->
<- breakpoint_set -i 5 -n 14 -f file%3A//C%3A%5Cbackup%5Cgit-wc%5Chm-wc%5Chm%5Capplication%5Cbootstrap.php -t line
->
<- breakpoint_set -i 6 -x "Fatal error" -t exception
->
<- breakpoint_set -i 7 -x "Catchable fatal error" -t exception
->
<- breakpoint_set -i 8 -x "Warning" -t exception
->
<- breakpoint_set -i 9 -x "Parse error" -t exception
->
<- breakpoint_set -i 10 -x "Notice" -t exception
->
<- breakpoint_set -i 11 -x "Strict standards" -t exception
->
<- breakpoint_set -i 12 -x "Deprecated" -t exception
->
<- breakpoint_set -i 13 -x "Xdebug" -t exception
->
<- breakpoint_set -i 14 -x "Unknown error" -t exception
->
<- run -i 15
->
Log closed at 2014-09-17 02:41:20
Log opened at 2014-09-17 02:41:20 I: Connecting to configured address/port: 10.0.2.2:9001. E: Time-out connecting to client. :-( Log closed at 2014-09-17 02:41:20
Log opened at 2014-09-17 02:41:27 I: Connecting to configured address/port: 10.0.2.2:9001. E: Time-out connecting to client. :-( Log closed at 2014-09-17 02:41:27
Log opened at 2014-09-17 02:41:27 I: Connecting to configured address/port: 10.0.2.2:9001. E: Time-out connecting to client. :-( Log closed at 2014-09-17 02:41:27
Log opened at 2014-09-17 02:41:27 I: Connecting to configured address/port: 10.0.2.2:9001. E: Time-out connecting to client. :-( Log closed at 2014-09-17 02:41:28
Log opened at 2014-09-17 02:41:28 I: Connecting to configured address/port: 10.0.2.2:9001. E: Time-out connecting to client. :-( Log closed at 2014-09-17 02:41:28
Log opened at 2014-09-17 02:41:28 I: Connecting to configured address/port: 10.0.2.2:9001. E: Time-out connecting to client. :-( Log closed at 2014-09-17 02:41:28
Log opened at 2014-09-17 02:41:28 I: Connecting to configured address/port: 10.0.2.2:9001. E: Time-out connecting to client. :-( Log closed at 2014-09-17 02:41:29
Log opened at 2014-09-17 02:41:33 I: Connecting to configured address/port: 10.0.2.2:9001. E: Time-out connecting to client. :-( Log closed at 2014-09-17 02:41:34
Log opened at 2014-09-17 02:41:34 I: Connecting to configured address/port: 10.0.2.2:9001. E: Time-out connecting to client. :-( Log closed at 2014-09-17 02:41:34
Log opened at 2014-09-17 02:41:34 I: Connecting to configured address/port: 10.0.2.2:9001. E: Time-out connecting to client. :-( Log closed at 2014-09-17 02:41:34
Log opened at 2014-09-17 02:41:34 I: Connecting to configured address/port: 10.0.2.2:9001. E: Time-out connecting to client. :-( Log closed at 2014-09-17 02:41:34
Log opened at 2014-09-17 02:41:34 I: Connecting to configured address/port: 10.0.2.2:9001. E: Time-out connecting to client. :-( Log closed at 2014-09-17 02:41:34
I'm having a similar problem the only differences being that my host is running osx 10.9.4 and my guest is running Centos 6.5 x86_64.
I see these symptoms as well, and I think it's caused by a watch expression that produces an exception or fatal error. See #127
