My mac froze earlier today and I forced it to reboot (involving several force quits and eventually holding the power button). After it started up, everything worked except MAMP Pro. When it starts, it doesn't report any errors but just hangs on starting MySQL, with a spinner next to it indefinitely.
I've tried uninstalling and reinstalling to no avail. However, regular MAMP works just fine. I've deleted and reinstalled /Library/Application Support/appsolute/MAMP Pro several times, but maybe there's other files I'm missing?
I had this problem tonight.
The reason was that I had created a hostname, but forgot to assign it to a disk location before I clicked Apply.
Amazingly, once you do this, there is no way to actually correct your mistake - it hangs every time you start up, and you never get the option to fix the disk location.
The solution is to remove the entry manually from the MAMP settings plist.
Quit MAMP Pro
Open ~/Library/Application Support/appsolute/MAMP PRO/settings.plist
Find the <dict> entry that contains your incorrect host - you'll see this inside the XML:
<key>serverName</key>
<string>yourhostname</string>
Delete the entire <dict>...</dict> node that contains your hostname missing the disk location and save the file
Re-open MAMP Pro
You should be back in business.
For future avoidance of this, it's best to open MAMP Preferences and uncheck Allow apply when disk location of a host isn't valid
simply run this on terminal
killall -9 mysqld
Fixed it by overwriting /etc/apache2/httpd.conf with /etc/apache2/httpd.conf~original
I added a vhost with an underscore in it's name just before this problem occurred.
After replacing the underscore with a dash by manually editing ~/Library/Application Support/appsolute/MAMP PRO/settings4.plist everything worked again.
Mamp Pro 6 (updated from version 5 in July 2021) had this same boot problem and the following fixed it...
Remove the entire htdocs folder out of /Applications/MAMP/ (moved it to my Documents folder)
Start up MAMP. All working again. Very strange but it worked and none of the other answers here did, so...
Related
I deleted MAMP cause' I needed to free the space on my hard-drive and now I want to install it again, but I can't. I keep getting the mistake 'MAMP setup will now exit and the existing map installation will not be removed'. I thought that I still have some MAMP-files on my PC, but I don't. Can't figure out what's wrong and need some help!
I too had the same problem. I tried this method and it was solved.
Open the control panel>programs>programs and features>there comes the list of programs,find mamp and right click on it and click on 'uninstall'.
After getting uninstalled you can try to install it again. Then it works đź‘Ť.
Since upgrading from MAMP 3 to MAMP 4, the GUI hangs on each action. Clicking something like the menu occurs after around 30 seconds of the spinning wheel of death. This happens for any action within the interface. Running 10.12.2
This almost makes the software unusable, as I can't configure the interface to begin development.
My experience was identical. Searching for some errors I ended up running Tools > Verify MySQL Databases... Among tons of OK'ed databases, several had errors - innodb_index_stats, innodb_table_stats, slave_master_info, slave_relay_log_info, and slave_worker_info.
From here a search lead me to mysql error: Table “mysql”.“innodb_table_stats” not found.
So, I deleted all the .frm and .ibd of the tables above and I ran the five-tables.sql file in Terminal: source five-tables.sql
Now MAMP Pro 4 runs smoothly and responsive.
Thanks, Kay Nelson.
I ended up doing a search for MAMP in all parts of the file, and removed every reference to it, after running the uninstaller.
I also removed references to any PHP & memcache not in the /Applications/MAMP folder.
I renamed /Applications/MAMP to /Applications/MAMP-old and reinstalled. This set everything up fresh and appears to be working. Something with a conflict with a system binary or other package was causing the issue.
I've downloaded and installed STS 3.8.2 on my Mac (10.12.1). Each time the STS.app file is launched, it creates a new org.springsource.sts_3.8.2.RELEASE_########_macosx_cocoa_x86_64 folder under the hidden .eclipse folder (the hashes are there because I have MANY of the same folder with the numbers in the hash area being the only difference). In doing so, the default workspace and all plugins I installed the last time it was running are wiped out (because they exist in the previous #### folder).
I've tried installing the previous 3.8.1 and 3.8.0 version, but they are doing the same thing. My previous STS install started at 3.7 and has been upgraded to 3.8.1, but will not update anymore because of update errors that I can't seem to fix (none of the StackOverflow "fixes" have worked for me).
Is there a way to have STS not create a new folder (instance) in the .eclipse folder each time it launches? If so, how?
This got reported to STS and is documented here:
https://issuetracker.springsource.com/browse/STS-4406
The corresponding bug at Eclipse is:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=507328
To cut a long story short:
This is caused by macOS Sierra Gatekeeper App Translocation, a security feature that moves the app into a private read-only location for security reasons. Therefore Eclipse/STS creates a folder for its configuration in that location that you described above.
Since macOS Sierra does the app translocation again after every restart, Eclipse/STS doesn't know anything about the "old" configuration area anymore and creates a new one. As far as I can see, there is no way for Eclipse/STS to distinguish between a separate install and a newly translocated app... :-(
The workaround is:
A) Move STS.app into a different location on your disc after
unpacking the tar.gz archive (using the Finder, not the command
line). If you move it to "Applications", for example, everything
works as before (no app translocation happens in that case).
B) You could also start Eclipse/STS by clicking on the Executable (in
STS.app/Contents/MacOS). That also doesn't cause app translocation
and therefore everything is fine.
As this bug — alternatively unfortunate side-effect of Apple security measures — still exists in STS 3.9.8 (I assume also in 3.9.9) and the Eclipse bug report in the previous answer is closed as a duplicate of Workspace Preferences Do Not Persist on MacOS Sierra that, while being marked as "solved, actually in itself actually do not solve this dislocation issue — in that moving the app to /Applications or having a signed DMG, both making no difference — the info missing is that one can turn off App Dislocation on an app by app basis by using the "xattr" command in the Terminal, that works upon extended file attributes.
Use the command
sudo xattr -r -d com.apple.quarantine /Applications/sts.app
where -r makes the command recursive for all app contents (macOS apps being folders) and -d deletes the particular attribute at the given path.
To verify a successful result simply run
sudo xattr /Applications/sts.app
The successful result you want is a new prompt line. If you get "quarantine" on there you were not successful.
Note that, I could only test this in macOS 10.12.6
At present I cannot run it (SQL Developer 4.1) because it hangs on "Restoring Editors" while starting. I suppose I've done it by exiting it before by killing sql developer process because it was hanged on fetching objects to Schema Browser so long...
Maybe I would clean some temporary files but can't find any.
Any ideas?
Deleting files from c:\Users\MY_USER\AppData\Roaming\SQL Developer\SQL History
and c:\Users\MY_USER\AppData\Roaming\SQL Developer\System...
Really helped me to resolve the connection issues
Basing on this thread https://community.oracle.com/thread/2564842 I've created own solution.
Extract installation of current version SQL Developer (4.1.0.17.29)
At "c:\Users\MY_USER\AppData\Roaming\SQL Developer\"
I've changed directory name system4.1.0.17.29 to system4.1.0.17.28.
After running newly extracted SQL Developer (4.1.0.17.29) I was prompted to let copy configuration from version 4.1.0.17.28 to 4.1.0.17.29 ;)
Everything works great now. I suppose that running the same (broken) installation after decreasing version could also help.
Remove folders c:\Users\USERNAME\AppData\Roaming\SQL Developer\system4.1.3.20.78\system_cache*. SQLDeveloper will recreate it after launching.
Just execute sqldeveloper as administrator. It works fine!
In my case the problem was because of windows compatibility issue. So I've selected my windows version and it's stop from randomly crash after startup
Our setup:
Windows 10
Sqldeveloper Versions <= 20.4.0
We observed this problem as well. Even worse while working over a VPN connection. I followed a couple of hints with more or less no effect.
To move
C:\Users\<USER>\AppData\Roaming\SQL Developer
to a local directory by adding this line
AddVMOption -Dide.user.dir=c:\temp\sqldev-conf
in the \sqldeveloper\bin\sqldeveloper.conf file gave us some improvement, but the “IndexPreferencesTask” still got stuck several times on startup.
After some more hours on unsuccessful research, we moved back from JDK 11 to JDK 8.
This solved 99% of the problem. The “IndexPreferencesTask” still hangs on startup but for less than a second.
Sounds to me like a problem with JDK 11.
In my case when i changed Tools --> Preferences --> Environment -> Look and Feel to Windows it is solved.
Delete the History files from C:\Users\User\AppData\Roaming\sqldeveloper
Restart the PC
In my case, the solution was kind of weird. After battling to resolve this for 2 days, no luck. Suddenly, on my mac, I searched for sql developer, not sqldeveloper. It popped up a sqldeveloper application (not sure how that is different from what I have been trying to open ), clicked it and boom, it opened. My guess is that there is a copy of that app on my system that I should have been opening rather than trying to open the reinstalled app. Note: I reinstalled the app after it started misbehaving though.
Operating System: Windows 10
Oracle Sqldeveloper Ver: 17.4.0
The problem has been noticed sometime when any network security
patch was installed on your machine. Looks like the patch impacts
your cached data under your user profile folder.
As above Lakh, rtbf and others answered. Removing below folders
will resolve the issue.
C:\Users\<userId>\AppData\Roaming\SQL Developer\SqlHistory
C:\Users\<userId>\AppData\Roaming\SQL Developer\system17.4.0.355.2349
If any one find more approriate reason please feel free to
disagree with my answer.
When I create a new window based application, I get:
Failed to launch simulated
application: iOS Simulator failed to
install the application.
I tried to do what this post suggest, but didn't work
Any suggestions? I haven't tried re-installing xcode yet.
Choose Reset Content and Settings in the File menu of the Simulator.
Build Clean in Xcode
Then try again.
I'm not sure why, but rebooting my machine seemed to fix it.
I had the same problem. A reboot also did the trick, but then I realized that the directory
~/Library/Application Support/iPhone Simulator/6.1/
looked "different" after the reboot (Directory "Root" was missing). So I tried to reproduce the error by deleting the directory or parts of it. The simulator each time recreated the directory and worked fine. Maybe the reboot is not really needed just recreating the mentioned directory would also help.
Try to delete project.xcworkspace file and xcuserdata dirctory in your project
It seems that the processes don't get cleaned up properly each time you stop the app with ps aux in Terminal showing a large number of processes representing your app on the simulator.
I expect some kind of upper limit is reached with the number of processes / memory. (Indeed I have found that XCode will fail to build because some posix resource can't be found because there isn't memory to load it)
A machine restart clears all of these dead processes and allows room for new ones. For me, I only have to do this after about 2-3 weeks of not turning my computer off, but I suppose what resources you have and how often you use the Simulator will affect it.
If someone knows how to clear all these dead processes without restarting, that would be useful please, killall ... doesn't seem to have worked for me, but feel free to add to this answer.
Simply go the info.plist file property and set 'Copy to Output Directory' to 'Copy Always' it will resolve your problem.