MAMP Apache does not start after updating OS X 10.8 (Mountain Lion)

Question

Today I upgraded to OS X Mountain Lion. I noticed that Apache does not start in MAMP. Nothing new seems to be contained in the apache log file. Running sudo apachectl -k start in a terminal gives me the following:

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

I have a server_name defined in my httpd.conf file.

I also noticed that "website sharing" is no longer in the "Settings" panel ... strange.

Any ideas?

Thanks!

Answer 1

Hi Ryan, we had this problem.

It turns out that native Apache is running. We registered it here http://support.servertastic.com/mamp-not-starting-after-upgrade-to-mountain-lion/

Greetings

Richard

Answer 2

To fix the problem and run MAMP apache, you can now turn to: (the link above was broken.)

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

Or just run the following command:

 sudo apachectl stop 

Also, if you encounter difficulties when your mysql no longer starts, try killing the mysql process that can be started by doing the following:

• Open the Activity Monitor on your Mac.
• Find a process called "mysqld".
• Click this process and "End Process"

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

Answer 3

In MAMP PRO 2.1.1, click Tools > Exit Embedded Apache .

Answer 4

I managed to solve this running OS X 10.8.4 by opening Activity Monitor, selecting "All Processes", and then killing anyone with "httpd" in the header. After that, I was able to start MAMP, and the MYSQL and Apache servers gave a green light!

Answer 5

this one fixes my mamp

Just go to / Applications / MAMP / bin / apache 2 / bin with Finder and rename envvars to _envvars (yes, just add an underscore). Boom! Done and done.

from codesoap

Answer 6

There was the same problem; no other tricks helped. I found that I have an instance with "allow from 127.0.0.1" - deleting this IP address did the trick. I do not know why.

http://cl.ly/image/253g1L1W472z

Answer 7

The problem with OSX Mountain Lion is that /usr/lib/libpq.5.3.dylib does not exist, but /usr/lib/libpq.5.dylib does.

To fix the problem, open a terminal and:

 ~# sudo ln -s /usr/lib/libpq.5.3.dylib /usr/lib/libpq.5.dylib 

Answer 8

just try changing mamp in httpd.conf with:

LoadModule php5_module / Applications / MAMP / bin / php / php5.5.3 / modules / libphp5.so

Answer 9

My solution to a similar problem. That is, MySQL did a great job with the MAMP manager utility. The Apache server did not, and the "Open Start Page" was gray, i.e. Did not work.

It seems that my problem was that the Apache server was not for one reason or another able to access the apache_error.log log file in the / Applications / MAMP / logs folder. The file is somehow "stuck", that is, I could not change the file permissions using the chmod command. Only after I completely deleted the log file and then restarted the MAMP management utility and started working with MySQL and Apache again, everything worked fine.

BR, Janne

Answer 10

Had the same problem.

Then I set ServerName to localhost and Listen to port 8080 , because 80 was somehow inaccessible (not even like sudo). In my case, this seems to fix the problem.

Answer 11

If nothing works for you, as for me, the problem is that you started the MAMP update with the start of MAMP, and then you closed the existing MAMP without stopping your server. All you have to do is restart your computer.