I ran sudo find -L / -name .rvmrc and got:
/Library/Application Support/Comodo/Antivirus/Quarantine: Permission denied
and also: /dev/fd/3
When I try navigating to the directory I can only get to Application Support, and then from that directory when I run cd Comodo I get Comodo: No such file or directory But it is there if find is finding it right? or no? <<< I believe this is just the find process?
When I try to navigate to it using the finder I just get to Application Support, and Comodo is not there. I am displaying hidden files too. I am trying to remove all files of a certain type so I can get a new program to work properly. This find command suggests one of these files is still out there but I can not get to it.
For /dev/fd/3 why is this being matched? I'm no expert but I just did a quick google search and this is a file descriptor right? Does it even have content? How/Why could it match .rvmrc? When I try looking at it with cat I just get a bad file descriptor error. (Should I extract this into a separate question?)
Thanks for your help.
It looks like your user do not have sufficient privileges to access this Comodo directory.
Try ls -la "/Library/Application Support"/* . This should show who can access Comodo. If it is owned by yourself, then you can do a
chmod +rx "/Library/Application Support/Comodo/"
, then only view its content.
You might have access Quarantine because the find -L followed a link.
Edit
Once you have done this and cannot chmod anymore, then try to see who owns the dir:
ls -lad "/Library/Application Support/Comodo/Antivirus/"*
My Magento site that is consistently erroring out and giving me the report screen with the file name, but the file does not exist in the reports folder.
Also this folder have 777 permission.
what could be the cause of this issue.
Check permissions for the "var/cache" folder, it should be writeable to the system user running PHP. If yours is an Apache/mod_php installation, the user should be the same as in your Apache config (see User configuration directive).
Check the following folders:
var
var/log
var/report
var/cache
Just to test this, make sure all files and folders in Magento's "var" are accessible for the PHP user.
On Linux, your can do this by running:
#> cd /path/to/your/magento/folder/
#> find ./var -type f -exec chmod 666 '{}' ';'
#> find ./var -type d -exec chmod 777 '{}' ';'
Please note that 777 and 666 permissions are NOT recommended in production environment, as they represent a security threat. Please tune your permissions, for all Magento installation files and folders, in production environment.
Im getting blank page while using Laravel, I already gave perms to the folder with
find app/storage -type d -exec chmod 777 {} \;
But still blank page.
Another thing you can try...
run php artisan serve from your projects root dir, and see if the browser comes up if you go to http://localhost:8000
And give us feedback in the run... because now we only can guess.
I don't know where you're at on solving this problem. But, you'll want your permissions to be at 775 not 777. Also, you may want to check ownership on your htdocs folder and all files within that directory. This is pure speculation since I don't know what kind of dev enviroment you're using, but i run a lamp stack and when ever I have to create a new enviroment the htdocs folder is always owned by root. You may want/need to chown that to your user account.
How about chmod -R 777 app/storage
If that does not work it is a htaccess problem propably
Last but not least, and it might sound stupid, but can you verify if the directories are all there in app/storage ? Because it happened to me that i was checking out from svn and empty directories are not transferred, so make sure you check that app/storage/logs exists.
If there is no log file written then it sure has to do with access levels, for example not being able to write into those dirs, hence the chmod command above. And i posted that because i had never seen anybody do it the way you did.
At least if you are able to write to the log file you can find out what exactly is wrong.
But we have so minimal information it is hard to help you in a good way.
I installed XAMPP 1.7.3 on Mac OS X 10.6.8 without changing any defaults.
The webserver seems to work okay, but the permissions on the htdocs directory are set to "Read only" for everyone other than system. So (a) I have to provide root password every time I copy in web content, and, more problematic, (b) NetBeans says it can't create a target directory, and doesn't even generate the index.php file in the source directory.
Do I just need to manually change permissions on the htdocs directory, or is there some more global XAMPP setting that should be changed? Running NetBeans as root seems a bit extreme.
Tried the above but the option to amend the permission was not available for the htdocs folder,
My solution was:
Open applications folder
Locate XAMPP folder
Right click, get info (as described above)
In pop-up window locate the 'sharing & permission' section
Click the 'locked' padlock symbol
Enter admin password
Change 'Everyone' permissions to read & write
In the get info window still, select the 'cog' icon' drop down option at the very bottom and select 'Apply to enclosed items' this will adjust the permission across all sub-folders as well.
Re-lock the padlock symbol
Close the 'Get Info' window.
Task complete, this will now allow you to populate sub-folders within the htdocs folder as needed to populate your website(s).
Make sure the XAMPP app is running then:
Under General Tab, in XAMPP app, click Open Terminal
A terminal will be launched with something like, root#debian:~#, on the terminal shell
on that terminal shell, type, chmod -R 0777 /opt/lampp/htdocs/ and enter
Exit, the terminal and you be good to go
For latest OSX versions,
Right click on the folder
Select Get Info
Expand the Sharing & Permission section
Unlock the folder by clicking lock icon on bottom right-corner
Now, select the user list and enable Read & Write privilege for the users
Click on the + icon to add username
Finally click settings icon and select Apply to enclosed items...
Following the instructions from this page,
Open the XAMPP control panel (cmd-space, then enter manager-osx.app).
Select Manage Servers tab -> select Apache Web Server -> click Configure.
Click Open Conf File. Provide credentials if asked.
Change
<IfModule unixd_module>
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User daemon
Group daemon
</IfModule>
to
<IfModule unixd_module>
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User your_username
Group staff
</IfModule>
Save and close.
Using the XAMPP control panel, restart Apache.
Navigate to the document root of your server and make yourself the owner. The default is /Applications/XAMPP/xamppfiles/htdocs.
$ cd your_document_root
$ sudo chown -R your_username:staff .
Navigate to the xamppfiles directory and change the permission for logs and temp directory.
$ cd /Applications/XAMPP/xamppfiles
$ sudo chown -R your_username:staff logs
$ sudo chown -R your_username:staff temp
To be able to use phpmyadmin you have to change the permissions for config.inc.php.
$ cd /Applications/XAMPP/xamppfiles/phpmyadmin
$ sudo chown your_username:staff config.inc.php
For new XAMPP-VM for Mac OS X,
I change the ownership to daemon user and solve the problem.
For example,
$ chown -R daemon:daemon /opt/lampp/htdocs/hello-laravel/storage
If you use Mac OS X and XAMPP, let's assume that your folder with your site or API located in folder /Applications/XAMPP/xamppfiles/htdocs/API. Then you can grant access like this:
$ chmod 777 /Applications/XAMPP/xamppfiles/htdocs/API
And now open the page inside the folder:
http://localhost/API/index.php
Best solution for MAC OS Catalina Xampp
Open Finder
Press Cmd + shift + C
Macintosh HD => Users => copy {username}
Open /Applications/XAMPP/xamppfiles/etc/httpd.conf
Find User daemon edit daemon => {username}
Xampp Manage Server => Restart all
If you encounter problems in phpMyAdmin:
1. Browser (Chrome) restart
Goodluck
Go to htdocs folder, right click, get info, click to unlock the padlock icon, type your password, under sharing permission change the priviledge for everyone to read & write, on the cog wheel button next to the + and - icons, click and select apply to all enclosed items, click to accept security request, close get info. Now xampp can write and read your root folder.
Note:
If you copy a new folder into the htdocs after this, you need to repeat the process for that folder to have write permission.
When you move your files to the live server, you need to also chmod the appropriate files & folders on the server as well.
if you use one line folder or file
chmod 755 $(find /yourfolder -type d)
chmod 644 $(find /yourfolder -type f)
You can also simply change Apache Conf file to a different User Name and keep the group:
Apache Conf Applications/Xammp/etc/..
User 'User' = your user name in Mac os x.
Group daemon
sudo chown -R 'User':daemon ~/Sites/wordpress
sudo chmod -R g+w ~/Sites/wordpress
If you are running your page on the new XAMPP-VM version of MacOS you will have to set daemon as user and as group. Here you can find a great step-by-step illustration with screenshots from aXfon on how to do this.
As the htdocs folder under XAMPP-VM will be mounted as external volume, you'll have to do this as root of the mounted volume (root#debian). This can be achieved through the XAMPP-VM GUI:
See screenshot.
Once you are running as root of the mounted volume you can as described above change the file permission using:
chown -R daemon:daemon /opt/lampp/htdocs/FOLDER_OF_YOUR_PAGE
Source (w/ step-by-step illustration): aXfon
What worked for me was,
Open Terminal from the XAMPP app,
type in this,
chmod -R 0777 /opt/lampp/htdocs/
This Solved WordPress Filesystem Permissions in Bitnami XAMPP
By changing the file permissions in apps/wordpress folder mounted on MAC XAMPP-VM shown in the below screenshot.
sudo chown -R bitnami:daemon TARGET # [ Replace "TARGET" with your file/folder path ]
find TARGET -type d -print0 | xargs -0 chmod 775
find TARGET -type f -print0 | xargs -0 chmod 664
chmod 640 TARGET/wp-config.php
Source: bitnami
TARGET - Replace placeholder for your mounted filesystem wordpress path eg: '1.1.1.1/lampp/apps/wordpress'
Now you can edit your themes in VS-Code or any developer editor of your choice.
NOTE: This should be done only in your development environment.
Production build permissions are different & above doesn't apply
The above worked only for some directories but didn't for all root files. To change root files permissions, open Xampp app, within Xampp app click button 'open terminal'. once there do the following:
- go to root directory: cd ..
- got to directory where lamp is located: cd opt
- change lampp permissions: chown -R bitnami:root lampp
note: you can replace bitnami with your user, and root with your group.
as a second alternative that worked for some files:
go to your users folder in finder and find the .bitnami hidden folder, access xampp folder within it and change permissions:
/Users/username/.bitnami/stackman/machines/xampp
right click xampp folder under machines and change permissions to read & write
apply to enclosing folders with "cog icon"
I hope you can help get to the bottom of this. This is whats happened:
We duplicated our live Magento site (for example we'll call it domain1.com) to a development server (for this example I'll call this domain2.com)
Did a find/replace for the domain1.com to domain2.com in both the database and files
Deleted all var/cache and var/session files
Reindexed all indexes via SSH
Emptied browser cache
Checked all file permissions
Disabled the .htaccess incase this was causing a redirect
But it's still redirecting to the live server (domain1.com)??
Any ideas what may be triggering this?
Cheers,
Dave
Solved the issue...hopefully this helps some other people.
When the site was duplicated we edited the "local.xml" file with the new details but kept the old one and renamed it "localnew.xml"
It seems Magento was still picking up these details as so was redirecting to the old site.
Deleting the "localnew.xml" (or whatever you called it eg. localxxx.xml) fixed all our issues!
I'm working in a local Centos 6.4 running in a VM at the moment to test various things.
My production Magento site is in that folder: /var/www/html/magento
and the staging site is there: /var/www/html/staging/magento
I had the same issue than you, did everything I could come up with, triple checked the urls in the database, cleared the cache, checked the .htaccess file, rebooted multiple times.
The one thing that fixed the issue has been to set back the permissions properly:
cd /var/www/html/staging/magento
find . -type f -exec chmod 644 {} \;
find . -type d -exec chmod 755 {} \;
chown -R sysadmin:apache .
chmod -R 777 media app/etc var var/.htaccess
Just open your DB and open the table "core_config_data"
then edit the values for the path web/secure/base_url & web/unsecure/base_url