-
Notifications
You must be signed in to change notification settings - Fork 9.4k
File Permission Check Error #2885
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@Khushik Are there any errors in your brower's console? Also, please give details about your environment like OS, Server, PHP version etc. |
In addition, it could be a problem with ownership. You should NOT set 777 permissions on anything. Please refer to ownership and permissions documentation |
My environment: chown -R :apache . |
@Khushik is the logged in user (the one running command on prompt) in the same group as apache as mentioned in @xcomSteveJohnson's doc link? |
If the correct owner and file permissions are set, it's most likely SELinux. You can try setting SELinux to permissive mode to see if that's the issue:
If that does work, you can either leave SELinux in permissive mode or enable it and grant SE permissions on just the directory:
|
If you're seeing only 1 directory with setenforce 0 it's not SELinux, it's either the owner or file permissions. Try chown -R :apache magento2/var and setting file permissions on the magento2/var directory again. |
Finally I have launched my magento 2 test site. Thank you so much for your speed replies. |
Thank you. Setting the SELinux to permissive mode fixed this for me. I'm installing Magento 2.1 on PHP 7.0.6 on OpenLogic centos 7 all running on Windows Azure. I suggest the docs at http://devdocs.magento.com/guides/v2.0/install-gde/prereq/file-system-perms.html#perms-private get updated. Thanks once again @anaxmedia. took me a while to find out what I was doing wrong. |
sad to hear that only chmod -R 0777 whole-magento-folder/ worked for me |
[performance] MAGETWO-92402: Write tests for price indexer parallelization
Could you please help me to fix this error. All permission were granted but no results.
The text was updated successfully, but these errors were encountered: