This Terminal Emulator is not functional because no 'bash' shell could be found.
Please correct the problem and restart the ID
This is a brand new OSX laptop with 10.13.6, and I've been trying to replicate the setup with aptana 3. I'm not sure what I'm missing to be getting this error... previous threads with similar errors all seem to be dealing with windows environments
I had the same issue on macOS Mojave 10.14 with AptanaStudio 3.7.2 and could fix it based on the suggestion here (which is for linux) https://stackoverflow.com/a/6685532/5220160
So assuming your AptanaStudio.app sits in /Applications the fix would be chmod +x /Applications/AptanaStudio.app/Contents/Eclipse/plugins/com.aptana.terminal_3.0.0.201802081530/os/macosx/redtty
I have mac installed in my PC. I am running my xamarin project in Device.that is running fine.but when one of my teammate trying to deploy project in device that is connected to my PC.He is connected to my mac in VS.but it gives such error
the codesign_allocate helper tool cannot be found or used
anyone have idea about this.please help.
thanks in advance.
I tried most everything in codesign_allocate: error: unable to find utility "codesign_allocate", not a developer tool or in PATH and none of the answers at this time worked for my machine.
I had to take the nuclear option (use with caution):
rm -rf ~/Library/Developer/
Uninstall Xcode 😢
Fresh install from App Store
I have followed the instructions to install DB2 Express-C found here (which is the official guide on the IBM community forum). Everything worked quite fine until I had to run the db2_install.
When I execute it, it gives me the DBI1189E error:
"DBI1189E There has been an attempt to use db2_install
on an image for a platform that does not match the current platform
'MacOS' on which it is being run.
Explanation:
Possible causes include:
This DB2 install image is not valid for the current
platform.
The current platform is not supported by DB2.
User Response:
Install DB2 using the DB2 install image that corresponds
with the current platform 'MacOS'. "
Anyone knows what went wrong?
The last 2 days I also struggled with installing db2 on My Os X with the El Capitan.
First of all, important to know is that only version 10.1 is supported for mac, while for windows/linux, version 10.5 is supported.
This can cause troubles when migrating an existing database in 10.5 to your mac database in version 10.1. It is off course important to have the right distribution for mac os x.
I also tried the official guide on the IBM community forum, but it didn't work out for me too...
What I did was follow these instructions.
With these instructions, the installation went find, but I encountered some issues with the line:
Initialize the sample database using this command:
db2sampl
Make sure you issue the db2start command using the db2inst1 user.
After my db was started I had some issues with locked files.
I could solve them by issuing the command:
sudo chown db2inst1 /Users/db2inst1/sqllib/adm/*
And then everything worked fine.
Good luck!
I am finding references to seemingly the same problem for example here and here. All I am doing is googling for "DBI1189E mac os". Good luck and let me know if this has worked. Thanks!
I've followed all the steps here https://console.developers.google.com/start/appengine?_ga=1.82598931.449716086.1415074596 successfully up to step 5.3. When I try to start the server:
dev_appserver.py appengine-try-python-flask
I get the following output:
-bash: dev_appserver.py: command not found
I'm on a Mac running OS X 10.10. Any ideas what I'm doing wrong?
I'm running Python 2.7.6.
It seems like you didn't correctly add the dev_appserver (and other GAE tools) to the bash.
Did you restart your shell(s) to pick up the new environment changes?
If you did and the problem still persists, you can try downloading manually the GAE SDK.
After that, open the GoogleAppEngineLauncher, and just click OK on 'Make command symlinks'. This will solve your issue.
It's all easily explained in the official documentation:
Download and Install the Google App Engine SDK
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!