Running macOS Monterey 12.3 Apple M1 Pro, and opening Jupyter either through terminal (jupyter notebook) or Anaconda. When the http://localhost:8888/tree pulls up I only see some of my folders & most importantly I don't see by Box (box.com) and I cannot access it at all. I cannot even access my Users account. Any advice?
I have tried navigating all the available folders with no success.
I got into same issue when I upgrade my OS from catalina to Monterey.
I did some research today and found that it is because Box changes from kernel mode to FPE mode and causes this mount issue.
Some argues they can resolve this issue by deleting the FPE folder in content package.link:https://support.box.com/hc/en-us/community/posts/4413563848851-How-can-I-change-FPE-mode-to-Kernel-mode-
If this works for you then go for it.
Mine is OS monterey and it is not working. What I do to resolve this:
make an alias manually by run this in terminal:
ln -s ~/Library/CloudStorage/Box-Box ~/Box
This make an Box folder:
then allow access of Box in systems preferences/Security&privacy:
I allowed full disk access to anaconda and it works.
Also fizilla can access box as well
Good luck!
One of our engineers facing an error with PhpStorm. Whenever he edits anything in PhpStorm, it gives the error related to PHP_Codesniffer:
phpcs: env: php: No such file or directory...
If open PHPCodeSniffer Inspection Settings, the below attached settings can be seen.
One more point, it was working fine until he upgrades his MacOS from Big Sur to Monterey 12.0.1. Not sure this OS upgrade affect the application settings. Presently he cannot work with PhpStorm.
Could you please have a look and let me know?
One more point, it was working fine until he upgrades his MacOS from Big Sur to Monterey 12.0.1. Not sure this OS upgrade affect the application settings. Presently he cannot work with PhpStorm.
I had the same issue. Monterey removes the installed PHP version, as Mac OS no longer ships with php installed.
Install php and it should work again.
In my case, using homebrew
brew install php#7.4
brew link php#7.4
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 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!