Recently I have started to use React Native and I didn't want to use Android Studio, so I manually installed every thing including hyper-v but after that I have a really strange problem if I put any port in .env file when I run npm start it saying that the port is in use!
And the other issue was when I was using JetBrains' products (like WebStorm) it won't start. I found this in log files :
java.net.BindException: Address already in use: bind
And the most strange thing was that the ports were not in use !
So after a week I found the solution .
The answer is really simple this is a problem with hyper-v and wsl2, and I don't know why it cause this problem.
I solved my problem using two commands (I'm using Windows 10) :
net stop winnat
net start winnat
I hope this fix your issue!
Edit:
Even after you reset the reserved ports by the command, after a full restart then you will need to run the command again.
This is because of windows sandbox. It'll re-reserve the ports.
So to fully fix the problem you need to turn off windows sandbox in windows features, that will fully fix the problem
Am getting below error while setup.
I have setup my ANDRIOD_HOME variable too. But still getting the below error.
Can anyone help me on this:
java.lang.RuntimeException: io.selendroid.exceptions.SelendroidException: Enviro
nment variable 'ANDROID_HOME' was not found!
Please setup Android sdk correctly. If you don't know how to do it, have a look at this guide: http://spring.io/guides/gs/android/
Please have a look at https://github.com/selendroid/selendroid/issues/198
I got these issues resolved.
Do vote the answer after you get your issue resolved.
ANDROID_HOME variable should point to the SDK:
set ANDROID_HOME=C:\${installation location}\SDK
set PATH=%PATH%;%ANDROID_HOME%\tools;%ANDROID_HOME%\platform-tools
[Try setting path through the command prompt before running selendroid]
(This is only for Windows. For other OS you can check this link:
http://spring.io/guides/gs/android/)
I've spent some time trying to figure out why the autostart, remote , and connect_back settings wont turn on. I've typed in:
xdebug.remote_enable=1
xdebug.remote_handler=dbgp
xdebug.remote_port=9000
xdebug.remote_autostart=1
xdebug.remote_connect_back=1
;xdebug.remote_host=192.168.1.108
All this into the php.ini file, restarted servers, and when I check the configuration page on the MAMP page, these settings still read OFF. Any idea why this is...
Bit late answer maybe but here's how I solved this issue.
For some reason MAMP conf files doesn't affect these settings, what I did was:
Go to /MAMP/bin/php/[phpX.X.XX ie your current version]/conf/php.ini and set it here.
This is super late, but, you need to edit the correct php.ini file. MAMP comes with 2 or more!
From the MAMP control/app launch the PHP_INFO() page, or make your own. Check the path value for the Loaded Configuration File
That is the php.ini to edit.
I have a projects in cakephp which is a big size projects.. It is running perfectly in another computer or in the server. But when I copy the files and database to my local computer then it shows the following error.
Fatal error: Maximum function nesting level of '100' reached, aborting! in D:\wamp\www\faceadz\cake\libs\debugger.php on line 248
Project is running in wamp server.
Please help me...
thanks
there might be 2 solution will work for you in you local machine configuration
1. A simple solution solved to your problem. you can just commented the:
"zend_extension = "d:/wamp/bin/php/php5.3.8/zend_ext/php_xdebug-2.1.2-5.3-vc9.dll"
in your php.ini file. This extension was limiting the stack to 100 so I disabled it. The recursive function is now working as anticipated.
2. and
Assuming you're using xdebug, you can set your own limit with
ini_set('xdebug.max_nesting_level', $limit)
EDIT
Also it will help you
changes the file /etc/mysql/my.cnf parameter to something like that max_allowed_packet = 512M
Get sure you've got xdebug installed (use phpinfo()) and then change the file /etc/php5/fpm/php.ini adding or editing the line : xdebug.max_nesting_level=1000
Restart both services sudo service mysql restart sudo service php5-fpm restart
If it doesn't work you can still set those two parameters to false at /etc/php5/fpm/php.ini xdebug.remote_autostart=0 xdebug.remote_enable=0
hope it will help you,
I've been beating my head against this for hours.
I've come back to do some work in PHPStorm after not having used it in a couple of weeks, and for some reason the debug doesn't work any more. It used to work, but now it doesn't and I have no idea what is going on.
I'm running on Windows, using IIS, PHP version 5.3.8. The XDebug is installed, and I've set the configuration in PHP.ini as per the usual instructions.
When I run phpinfo() everything looks normal (ie. XDebug is there).
I've rechecked various settings, downloaded a slightly newer version of XDebug than I was using (Xdebug v2.2.1), but nothing seems to kick it into life.
Can someone please give me some clues as to what I can look at next?
UPDATE:
I've spent a few more hours beating my head against this, and don't seem to have gotten much further. XDebug is installed and loaded, according to phpinfo(). I turned on logging, but it doesn't really tell me much except that XDebug is indeed connecting...
Log opened at 2013-02-17 04:13:07
I: Connecting to configured address/port: localhost:9000.
I: Connected to client. :-)
-> <init xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" fileuri="file:///C:/web/dbg/index.php" language="PHP" protocol_version="1.0" appid="6912" idekey="PHPSTORM"><engine version="2.2.1"><![CDATA[Xdebug]]></engine><author><![CDATA[Derick Rethans]]></author><url><![CDATA[http://xdebug.org]]></url><copyright><![CDATA[Copyright (c) 2002-2012 by Derick Rethans]]></copyright></init>
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" status="stopping" reason="ok"></response>
Log closed at 2013-02-17 04:13:07
So it seems that the problem is on the PHPStorm side, but I cannot see where. I tried creating a very simple project, but could not get that to debug either.
Don't you hate it when you spend hours wrestling with something, then in desperation try something simple, and it works?
I decided to try a different port, 9001 instead of the default 9000, and it WORKED!
I now realise that I recently installed Twonky (for video streaming to my TV), and when I checked the settings, there it was... port 9000.
Had the same issue this afternoon - found this question along with several other SO questions so I thought I'd post the solution that fixed it for me.
I was missing a mapping to the file system. Which is odd because I've seen PHPStorm prompt me when they've been missing previously.
Hopefully this helps someone in the future :)
Had the same problem after updating to El Capitan. First hint to that I used is Run -> Web Server Debug Validation.
This tool from PHPStorm gave me a hint about xdebug.remote_host I'm using v-hosts and it was complaining localhost being not the correct value there. So I updated xdebug setting with xdebug.remote_connect_back=On and it worked!
Apparently if you try to debug on newer versions of xdebug you have to include this line to your xdebug-php.ini settings
xdebug.mode=debug
I had same problem and I resolved it by deleting all the watches, and then reboot phpStorm
I resolved by by myself also, cause PHP-Storm and PHP-FPM are listening same port... just kill all php-fpm port.
Had the same problem. For me I was using port 9010 for xdebug. Problem turned out to be Logitech's GHub software I recently installed for a new mouse listens on port 9010! You can use this to see what is listening on a given port on Macs:
lsof -nP -iTCP:9010 | grep LISTEN
Newer versions of PHPStorm have Debugger validation. The official PHPStorm Blog has a writeup on this feature which might help you figure it out.
One snafu for me when I set up a box with php-fpm configured is that php-fpm runs on port 9000 by default also, so I had to change the configured port in php.ini and PHPStorm's preferences to something like 9001.
For what it's worth, my current php.ini setup for xdebug:
[xdebug]
zend_extension="/the/path/to/xdebug.so"
xdebug.file_link_format="txmt://open?url=file://%f&line=%l"
xdebug.remote_enable=1
xdebug.remote_autostart=On
xdebug.remote_port=9001
xdebug.profiler_enable_trigger=1
xdebug.max_nesting_level=250
I had the same problem! I finally realized that all my configurations were correct, but on the browser side, I hadn't enabled debugging with the Chrome Browser. Each browser has their own way of enabling the debugging to start working.
I had the same issue and I tried all the solutions I could find in SO and in other sites (checked that both phpStorm and Xdebug are on the same ports, checked that I had the server mapping on the file system, reinstalled Xdebug, etc.) but eventually the problem was in the fact that we run the site on an internal server, and someone from IT changed my computer's IP address to an address which is filtered out of the allowed addresses that can be connected to that server. That's why phpStorm started to ignore the breakpoints from Xdebug.
Hopefully, this will help someone in the future and save him many hours.
Found that if xdebug log file is not writable then it could be not working. Always better to set xdebug.remote_log and make it writable.