Every time I make a change to php.ini through FILE > EDIT TEMPLATE > PHP > appropriate ini file, MAMP won't restart. I try using terminal to quit apache and mysql but it makes no difference and tells me they aren't running. I'm convinced there is some local non-mamp server running that is clashing with it but am not clever enough to work out what. My only solution is to restart my Mac (Macbook Pro Early 2013 running OSX 10.9.3) every time I make a change to php.ini. Which is not the end of the world but just a bit annoying.
Any ideas?
I think after you make changes in php.ini and restart, there is another application who take your port 80 and apache can't start.
so to do a test you can close application like : skype, teamviewer,...
or change in there settings to not use this port.
or you can change the apache port to something like : 8094
Related
I've been working on a computing server and I need to make sure it restart properly in case of crash. The computer restarts properly, so I'm trying to start my process.
Our server is a C++ executable attached to Apache on a wamp server, the whole thing on a Windows computer. So I need to find a way to :
Start Wamp when Windows restarts
Start my process when Wamp is ready
I found out how to start Wamp when Windows reboots but I'm stuck on how to get my process to start when Wamp is ready. How can I do that ?
I'm using NSSM to create windows services out of regular processes. It's painless and you can set another service as a dependency, ensuring your process won't start before it.
I am trying to start wamp serve which was totally running fine on my laptop two weeks ago, but now after two weeks I suddenly get this error:
could not execute menu item(internal error)[exception] could not execute run action: the directory name is invalid
When I click on wamp, then I go to apache, then I select service then test port 80 and this is what I see:
when I write localhost, it goes there but when I click on Localhost and phpMyAdmin, i get this error:
please tel me how I can fix this . thanks
WAMP is trying to open your browser, but the directory in the settings is not correct. It could be that your browser is now located somewhere else. To fix this:
Edit the file wampmanager.conf inside your wamp direcotry.
Replace the full file path under the [main] section for the navigator parameter
Save the file
Right-click on the wamp icon and select refresh
Try it now
Good luck!
The paths are incorrect in multiple ini files and the wampmanager conf file. Here are the ones I changed since my installed moved from g drive to e drive. I had to change all instances of g:/ to e:/ as well as my chrome.exe location
wampmanager.conf:
in the [main] section update the path of chrome.exe or ensure it is correct.
wampmanager.ini:
change all instances of g:/ to e:/ (or whatever your install drive letter is)
php.ini (under /wamp/bin/php/php5.5.12/)
again, change all instances of g:/ to e:/ (change to your install letter)
Wampmanager started correctly once these changes were made.
I had a similar problem, and to get my WAMP server working again on my laptop I ran the executables for Apache and MySql independant of the WAMP system tray icon.
In Windows Explorer, I ran (elevated):
{wamp folder in my case C:\wamp}bin\apache\apache2.2.22\bin\ApacheManager.exe
This put the apache manager system tray icon in.
then I used the apache system tray icon to start apache server
Then I ran (elevated):
{C:\wamp}bin\mysql\mysql5.5.24\bin\mysqld.exe
This allowed me to use localhost\phpmyadmin, which to me demonstrates the php, mysql and apache are all working.
My web app was also back and running.
The age of my MySql version and apache version show how long this had been stable for.
I initially thought the problem may have been caused by a google chrome upgrade which included the notifications icon in the system tray, as the chrome upgrade was the only thing I recall changing. I unistalled chrome but this did not fix it - although this does not rule out Chrom Notifications being what broke it!
This appears to be an oversight on the WAMPSERVER developers. For some reason it does not translate the file path syntax from Linux to Windows, resulting in the following error message:
Aestan Tray Menu: Could not execute menu item (internal error)
[Exception] Could not execute run action: The directory name is invalid
To fix this, edit wampmanager.conf and replace the forward slashes in the file path with backslashes.
EXAMPLE:
Incorrect
editor ="C:/Program Files/Sublime Text 3/sublime_text.exe"
Correct
editor ="C:\Program Files\Sublime Text 3\sublime_text.exe"
Save the file, then right click the tray icon and select "Refresh". You should now be able to edit your files with your selected editor without issue :)
i have met this problem and fixed by editing 4 files
- wampmanager.conf in root
- wampmanager.ini in root
- php.ini in (wamp64/bin/php/php5.5.12)
- httpd.conf in (wamp64\bin\apache\apache2.4.18\conf)
I read many similar questions about it but the solutions are not working for me.
The icon says WAMP Server online but it stays orange.
when I test port 80 under Apache/services/Test port 80 it says that port 80 is actually used by: Server: Apache/2.2.8 PHP/5.2.6
Shouldn't that be a good thing? As there are no other programs using port 80, despite that when I type local host I get a weird page instead of the normal one, it has pink bars
The AppServ Open Project - 2.5.10 for Windows
phpMyAdmin Database Manager Version 2.10.3
PHP Information Version 5.2.6
About AppServ Version 2.5.10 for Windows
AppServ is a merging open source software installer package for Windows includes :
Apache Web Server Version 2.2.8
PHP Script Language Version 5.2.6
MySQL Database Version 5.0.51b
phpMyAdmin Database Manager Version 2.10.3
ChangeLog
README
AUTHORS
COPYING
Official Site : http://www.AppServNetwork.com
Hosting support by : http://www.AppServHosting.com
Change Language :
Easy way to build Webserver, Database Server with AppServ :-)
I really need to start working in this project but this is preventing me from even starting.
I have solution...
Click WampServer icon in tray icons -> Apache -> Service -> Install service
(same for mysql -> Service -> Install service )
Then, Apache -> Service -> Start service (same for MySql -> Service -> Start service)
done! Enjoy :-)
If you are running Skype, stop it since it uses port80 which is needed by WAMP
You can also switch the port needed for Wamp.
Follow this article
How to change port number for apache in WAMP
Unless you really know what you are doing you should only have ONE Apache on your system.
Basically WAMPServer and APPServ are the same thing, that is they are installers for the WAMP Stack i.e. Apache, MySQL and PHP.
You only need one of them so uninstall the other, of course remember to backup anything you may want to move over to the other before you uninstall one of them.
Check if MySQL is running or not
Click on Wamp icon in icon tray then
MySQL->Service
if Start/Resume Service is visible and clickable it means your MySQL service is not running that's why it is giving you problem.
It's possible that you have installed some other application that installed and running MySQL - so already having one MySQL running is what conflicting with wamp's MySQL.
How to stop other MySQL from running?
Simply go to My Computer and search for file name "my.ini" (without quotes)
There should be at-least two my.ini files on your computer delete all other my.ini except the one in wamp directory
Restart your computer and start the wamp server it should solve your problem
As of WampServer 2.5 (64bit), these are the things I had to do to get it to go green:
In your my.ini
Change [wampmysqld] to [wampmysqld64]. Now when you start/stop wamp you should get information in your mysql log file (and errors if you have any).
I uncommented all the innodb lines under where it says Uncomment the following if you are using InnoDB tables (except for innodb_log_arch_dir and innodb_additional_mem_pool_size).
Make sure the innodb_data_home_dir is set properly, like innodb_data_home_dir = C:/wamp/bin/mysql/mysql5.6.17/data/. Do the same for innodb_log_group_home_dir.
Change the locale line to read lc-messages=en_US for English.
You can confirm mysql is up and running with Wamp Icon > Mysql > Service (Start/Resume service should be greyed out)
Install and start apache:
Wamp Icon > Apache > Service > Install Service.
Wamp Icon > Apache > Service > Start. (you can click on "test port 80" to see if something was blocking it like others have mentioned, such as skype, sql reports, etc.)
During the starting of WAMP server, the Apache service should be started as well. In case, it doesn’t start; WAMP server won’t perform as it should be.
To fix this issue, navigate to the WAMP server icon in the system tray > Apache > Service administration ‘wampapache64’ > Install Service.
it will open the Command Prompt on your screen. After closing the Command Prompt, go to the same path and click on Start/Resume Service.
The WAMP server icon should turn to green right away.
In case you can have all these but still, the icon is displaying orange color, you need to click on Restart Service button.
Hi everyone i'm trying to learn the django framework and I'm using PyDev (Eclipse Python Development Framework/Plugin). When I try to run my application I get an error:
Error: [Errno 10013]
I know that this is because of the port. I use the port 8000 and i want to change it to 8080. Does anyone knows what exactly should i do to change the port?
pydev debugger: starting
Validating models...
0 errors found
Django version 1.3.1, using settings 'muapp.settings'
Development server is running at http://127.0.0.1:8000/
Quit the server with CTRL-BREAK.
Error: [Errno 10013]
It might be useful to point out that PyDev, like Eclipse, runs the configured command when the Run button is pressed. How is the default command and/or its options changed?
Have a look at this video tutorial. Skip about 14 minutes in. Then use runserver 8080 instead of runserver in the arguments.
Please take a look at the PyDev Documentation on how to change the Run configuration.
Run/Debug as Django
Run as Django/Debug as Django are available (note that they set the
--noreload by default).
This will create a default Run configuration, so, you may edit it
later through run > run configurations (or debug > debug
configurations) if you want to change a parameter.
Note: to know how to rerun the last launch see: the Rerun Last Launch
topic on PyDev Launching
Note 2: if the --noreload is not passed, only the parent process will
be killed from Eclipse and the others will only be killed when they'd
be reloaded (i.e.: on a code-change).
Whether it's "Eclipse" or "PyDev", right-click on the Project and select "Run As" --> "Run Configurations..."
Additionally, according to the django Documentation,
runserver [addrport]¶
Starts a lightweight development Web server on the local machine. By
default, the server runs on port 8000 on the IP address 127.0.0.1. You
can pass in an IP address and port number explicitly.
Therefore, in your Project's Run Configuration, on the Arguments tab, simply add:
runserver 0.0.0.0:8080
This should have the server listen on all interfaces/IPs. Alternatively, you can make it more specific to your public-facing IP instead:
runserver 123.456.789.123:45678
Please, note that in this case, my IP would be "123.456.789.123" and the port would be "45678".
The following Answers might also be of use:
How to make Django's devserver public ? Is it generaly possible?
How can i get the running server URL
External Link; Third-party blog-post
I develop web applications using Django on Mac OSX 10.6. I use Django's built in local development server which I run on my computer's IP (such as: http://192.168.0.11:8001/). I test my applications in Firefox, Safari and Chrome and all display fine. I use Sun's VirtualBox with 3 different instances of Windows XP that have IE6, IE7 and IE8 on them.
For whatever reason, these sometimes just don't display the Django sites. They come up with 'The page cannot be displayed'. Eight times out of ten, they display fine and function normally but for no reason at all they won't display. Sometimes restarting Django's local development server from the Terminal will fix the problem, sometimes it won't.
Is there some sort of VirtualBox settings or Django settings that I need to set to ensure smooth operation of this? Am I overlooking something? Has anyone else had these problems?
By default the dev server binds to localhost. to run it on all interfaces use ./manage.py runserver 0.0.0.0:8000
I found the best way to do this is using the normal localhost:8000 or localhost:8001 (any port you need, especially if running multiple Django projects at the same time) in the Mac Terminal.
Then in VirtualBox with Windows, using the ipconfig command in the Command Prompt to find out the IP settings. Grab the Default Gateway (mine was 10.0.2.2 for example) then, in the browser, use this as the address to get to your Django project along with the original port setting that was set in the terminal. So in this case: http://10.0.2.2:8000/
I've been running it like this now for almost a week and it seems to of stopped the problems I was getting before totally. I couldn't really tell you why though!