MAMP Pro 3.05 on Mavericks updated to Yosemite - Apache does not start

Question

MAMP Folks just posted the workaround

Workaround for the 10.10 Preview 5 bug: Rename the file “envvars” located in /Applications/MAMP/Library/bin into “_envvars”

Test Update: It works!

Works for Yosemite release too!

Just found workaround from MAMP on Twitter

Workaround for the 10.10 Preview 5 bug: Rename the file “envvars” located in into “_envvars”

This works also for Mamp Pro 2.1.1 on Yosemite.

MAMP Folks just posted the workaround

Workaround for the 10.10 Preview 5 bug: Rename the file “envvars” located in /Applications/MAMP/Library/bin into “_envvars”

Test Update: It works!

Apparently the MAMP folks are working on a work-around:

https://twitter.com/mamp_en/status/496655943506350081

Follow their account for updates.

MAMP Pro 3.0.7.3 should run fine on Yosemite, but after installing it on a brand new machine, I experienced the same problem.

In my case, the problem occurred because I had defined Additional Parameters for my virtual host that contained quotes. By default, Yosemite keyboard settings are set to convert straight quotes to smart quotes ("no-cache" became “no-cache”. Depending on font and font size, this may not be immediately obvious). This made Apache crash, even when the host was disabled.

To change this settings, go to System Preferences -> Keyboard. In the Text tab, uncheck Use smarts quotes and dashes.

Today, I upgraded to MAMP Pro 3.0.7.3 after I upgraded to OSX Yosemite 10.10 (official release) and I experienced this same problem. Apache could not start and it has an empty log file.

I tried this fix, but I noticed that the file is named "envvars_" not "envvars". I renamed it to envvars, restarted MAMP Pro and apache could not start and it had an empty log file. I also noticed that the envvars file had been renamed to envvars_ after I had renamed it.

I was running MAMP 3.0.5 on Mavericks. After upgrading Mavericks to El Capitan, I ran into the same issue. Mysql did start normally but Apache did not.

After renaming envvars to _envvars in the folder /Applications/MAMP/Library/bin such as suggested for Yosemite, I was able to start Apache as before.

So, this fix works for El Capitan as well!