I've had similar issue before but usually ends up popping up. I recently upgraded to MAMP Pro 4 and any time I open app the main window doesn't appear. The application appears to be open, but can't see it. Any idea what the issue is?
Go into Applications/MAMP PRO and run MAMP PRO Uninstaller
Download MAMP_MAMP_PRO_3.5.2 and run it then quit MAMP PRO
Download MAMP_MAMP_PRO_4.5 and run it
Than should fix all the issues
First quit MAMP PRO.
Go to your
~/Library/Application Support/appsolute/MAMP PRO/templates/
folder.
Rename your my.cnf.temp file. Restart MAMP PRO.
You will then need to remake any changes you had previously made for your my.cnf template via the File > Edit Template > MySQL when you open MAMP PRO again
See also https://appsolute.zendesk.com/home first Article.
Related
When I try to run my project through the Xcode simulator, it keeps giving me the error "Software caused connection abort".
Tried restarting the simulator & Xcode, and I recently deleted the DerivedData folder as suggested in this post about broken playgrounds so that also didn't help.
QUICK FIX
This is happening because you have multiple versions of Xcode installed. MacOS unfortunately only supports running one version of Xcode at a time, and it needs to know the location of the currently running version. To sort things out, choose one of the following:
Quit all instances of Xcode and restart it
Try one of the other options below if that hasn't solved it.
Using the command line:
run sudo xcode-select --switch /Applications/your_custom_folder_if_needed/Xcode.app
Restart your terminal and Xcode and it will work just fine.
No-command line users:
Quit all instances of Xcode
Start the instance of Xcode that you want to use
Go to Xcode -> Preferences -> Locations
Select the correct version in Command Line Tools
Done!
It's due to multiple Xcode installed in your system. This is how you make it work:
Quit all running Xcodes
Re-launch Xcode
Go to Xcode > Preferences > Locations
Change to the correct version in Command Line Tools
Clean project and clear Derived data if necessary, then run!
In my case quitting and re-launching given Xcode was enough. I had two Xcodes, stable and beta.
For me, restarting the Mac OS worked (multiple times).
I used Mamp Pro 4 for a while with no problem on my Mac (Os X 10.11), then, suddenly, Apache won't start. I got an error: "Check the log" but log is empty.
I have made several test:
reinstalled Mamp Pro 4 (4.0.6);
rebuild permissions using utility disk and Onyx
update Mac os X El Captain to Sierra;
started Apache/MySql as "www" or as "user"
Note:
1) starting system Apache it works
2) using MAMP (not pro) Apache works fine.
Any other suggestions ? Thanks
Fixed!! The issue was in SSL. For some reasons it stopped to works. No logs and no warning occurred: just an empty log. I deleted the SSL and created a new certificate. Now Apache works fine as well.
Have you tried to force-quit apache? I got this issue sometimes as well and using the terminal-commands sudo killall httpd and sudo killall mysqld fixed this issue.
Sometimes I have to repeat the commands a few times.
Upgraded to mamp pro 4.2.1. Now apache won't start. followed directions here: https://appsolute.zendesk.com/hc/en-us/articles/215197286
Nothing in activity monitor.
Nothing in log file.
Resolved by deleting hosts in mamp pro, where the document root had been deleted.
If you are seeing a red circle-arrow next to the Hosts link in the upper left, find the hosts that are not resolving properly to a document root, then fix them or delete them. That resolved it.
I have been running MAMP Pro 3.05 successfully in Yosemite up to DP4 on a partition that was a clean install of Yosemite.
I now have run the installer for DP5 over my Mavericks install, and now that MAMP Pro install will not start Apache. It says to check the logs, but I don't see anything pertinent.
I'm assuming that since this is a pre-existing install, something in its config is wrong for Yosemite's Apache.
Any ideas?
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!
I didn't get it working by changing envvar to _envvar but was able to resolve by changing the apache port from 8888 to 80 then noticed I was missing the mod_example.so. See how I resolved below:
Why won't Apache Server start in MAMP?
I tried that solution and others over and over and did not work until I realised I should be restarting completely MAMP, after doing so, this simple change from envvars to _envvars worked like a charm.
You can completely restart MAMP checking if there's any process going on, open the terminal:
ps -cvx | grep "mysql"
That will output a list of the processes that involves mysql at the time, with a PDI associated, so you only have to take that number and:
kill PDI
Where PDI is the number associated to the process, after that, if you write again the command ps -cvx | grep "mysql" the pointer should be empty.
Once done, only execute MAMP.
The approved answer didn't work for me because the _envvars file was already there. I had to download the latest version of MAMP and install it and it worked.
Sometimes, it's not always the envars files that's the culprit. If you've been editing the vhost file at /Applications/MAMP/conf/apache/extra/httpd-vhosts.conf, a syntax error could cause MAMP's apache to not start without a warning.
In that case, you can run the following command and see if any errors are encountered.
sudo apachectl stop
Try this::
Rename the file “envvars” located in /Applications/MAMP/Library/bin into “_envvars” only for OS X Yosemite.
I got MAMP v3.4 working.
I renamed "envars_" to "_envars" ... but that didn't work.
I had to also go into preferences, and hit the "Set Web & MySql ports to 80 & 3306" button!
Works!
I have an updated MAC OS Mavericks, with DP5 and newly installed XCode 5.0.1. XCode crahses - I cannot create a new project and also cannot open an existing one. Please help.
Repare the rights in disk utility.
Reset PRAM.
If this doesn't help redownload Xcode.
I had the same problem and this worked for me:
Repair Rights in Disk Utility
Reboot
Open Xcode
Open project
Project opens as expected! Whoot.
Just update to DP7 and it will work!
I understand that those who installed Xcode 4 via the developer site are able to uninstall via /Developer/Library/uninstall-devtools –mode=all, however I installed via the App store and there doesn't seem to be an executable with the word "uninstall" in the name anywhere in the Developer folder at all. Any suggestions on how I should go about uninstalling Xcode 4?
This help for Xcode before MAS install
/Library/Developer/Shared/uninstall-devtools
If you install it from MAS you can remove from launchpad,
but also need to remove some folders** and files created by this app, you can use some helper application that found this files and safely remove it :)
** ex.: ~/Library/Developer, ~/Library/Application Support/Xcode, ~/Library/iPhone Simulator, Logs and etc.
From the above comment, the correct way is to:
Run sudo /Developer/Library/uninstall-devtools –mode=all
Delete "/Applications/Install Xcode" if you want the app store to allow you to reinstall it.
If you have installed xcode from Mac App store, then you need to delete it from Launch pad. You can do this by locating xcode icon in launch pad, long click on the icon till it starts dancing. Then delete it and wait for a while till the xcode.app is deleted from /Application. If you manually delete xcode.app from /Application, App store will continue to think its installed and will not allow you to reinstall in future.
In our installs of xCode 4 from the App Store, we are able to use:
sudo /Developer/Library/uninstall-developer-folder
You must uninstall first the
sudo /Library/Developer/Share/uninstall-devtools –mode=all
It might be something else in your particular case so maybe you can try
locate uninstall-devtools to find where the script is placed.
Then you can find the version you need of xcode from https://developer.apple.com/downloads/index.action
IMPORTANT: If you are going to install a previous version of the Developer Tools, be sure to restart the machine after installing.