Having the same issue here ---> http://forum.mamp.info/viewtopic.php?f=2&t=10135
Console kicks back this exact same error. Nothing at all has changed since last I used MAMP Pro in a working state, to when MAMP Pro decided to get in a fight with me (MAMP is winning). This inexplicable faceplant is infuriating.
It's worth mentioning that this happens regardless of what port MAMP is running on.
After googling about, and watching Console, I was able to find a solution. This seems to work on MAMP Pro 2, though for some reason, the httpd.conf in the Application directory is different from the one that is editable from within MAMP via the "Edit template" menu.
Open up httpd.conf in MAMP, and comment out line #105
- Code: Select all
MAMP_unique_id_module_MAMPLoadModule unique_id_module modules/mod_unique_id.so
Apache has begun to start again, though I do not know why, and I do not know what disabling this module does. I'm a designer. Either way, I feel that MAMP Pro 2 is not behaving properly, and this shouldn't be required to start Apache. Hopefully there's some response to this problem from someone who understands server admin, as I'm just throwing haymakers in the dark.
Something of note
While troubleshooting this, I noticed my hosts file was completely wiped out. Don't know by what.