MAMP Apache Won't Start after OS X 10.8 (Mountain Lion) update

Question

Today I updated to OS X Mountain Lion. I noticed that Apache won't start in MAMP. Nothing new seems to be in the apache log file. Running sudo apachectl -k start in Terminal gives me this:

httpd: Could not reliably determine the server's fully qualified domain name, using Ryan-Smiths-MacBook.local for ServerName

I do have ServerName defined in my httpd.conf file.

I also noticed that "Web sharing" is no longer in the Settings pane... weird.

Any Ideas?

Thanks!

Solution 1

Hi Ryan we had this problem

It turns out the systems own apache is running. We've documented it here http://support.servertastic.com/mamp-not-starting-after-upgrade-to-mountain-lion/

Cheers

Richard

Solution 2

To fix the problem, and to start MAMP apache, you can now refer to: (the above link is broken now.)

https://support.servertastic.com/mamp-not-starting-after-upgrade-to-mountain-lion/

Or simply run the following command:

sudo apachectl stop

In addition if you run into trouble where your mysql no longer will start, try killing the mysql process that may already be running by doing the following:

1. Open up the program called "Activity Monitor" on your Mac.
2. Search for a process called “mysqld“.
3. Click on that process and “Quit Process”

Credits: http://eliteeternity.com/mysql-server-wont-start-mamp-red-light-mac/ http://forum.mamp.info/viewtopic.php?f=6&t=6149

Solution 3

In MAMP PRO 2.1.1, click Tools > Quit Built-in Apache.

Solution 4

I was able to solve this running OS X 10.8.4 by opening up Activity Monitor, choosing "All Processes" then killing any with "httpd" in the title. After that I was able to start MAMP and both the MYSQL and Apache servers gave the green light!

Solution 5

this one fix my MAMP

Just navigate to /Applications/MAMP/bin/apache2/bin using Finder, and rename envvars to _envvars (yes, just add the underscore). Boom! Done and done.

from codesoap

View more solutions

Comments

[Richard Askew]

Port 80 isn't available because the in-built Apache is running on that port, stop it as covered in my answer and you should be able to use it again

[Olie]

Am I right that you want to turn that around? So the command is sudo ln -s /usr/lib/libpq.5.dylib /usr/lib/libpq.5.3.dylib ...?

[elliotrock]

The above sude command for stopping the default apache server worked for me. Thanks