Installation on Fedora Server 25

I am attempting to install SuiteCRM on Fedora Server 25. When I run through the installer I am receiving error messages that some directories and files are not writable. I have set the users/group to root, apache and nobody and the permissions to 777,765 and 766. Nothing seems to be able to make the files writable. Any suggestions?

Just use the chown and the two chmod’s given in the installation instructions. The values you’re using are not good (insecure!).


    cd your-suitecrm-main-folder
    sudo chown -R apache:nobody .
    sudo chmod -R 755 .
    sudo chmod -R 775 cache custom modules themes data upload config_override.php 

If you need more assistance, please post the exact commands you used to set permissions, and some directory listings with the permissions applied.

P.S. - I’m not 100% sure if it should be apache:nobody or nobody:apache or even some other thing. I don’t have Fedora to check which is the user, which is the group, and whether they belong to each other or not…

Those were the exact commands I used.

Here is the current permissions

drwxrwxr-x. 4 nobody apache 35 Feb 27 12:06 cache
drwxr-xr-x. 17 nobody apache 4096 Feb 27 12:06 .
-rwxr-xr-x. 1 nobody apache 3590 Feb 27 11:45 campaign_tracker.php
-rwxrwxr-x. 1 nobody apache 47 Feb 27 11:45 config_override.php
-rwxr-xr-x. 1 nobody apache 3922 Feb 27 11:45 cron.php
-rwxr-xr-x. 1 nobody apache 2446 Feb 27 11:45 crossdomain.xml
drwxrwxr-x. 6 nobody apache 91 Feb 27 11:45 custom
drwxrwxr-x. 3 nobody apache 104 Feb 27 11:45 data

I have tried apache:nobody, Nobody:nobody, apache:apache, and root:root

Then you should try analyzing with greater detail: exactly which files it complains that it can’t write to; and exactly what permissions are there on those files.

There are a few more quirks that might need attention (umask, sticky bits on directories). Linux perms can get tricky sometimes.

BTW, have you set up your Scheduler jobs in cron already? Sometimes these can be guilty of degraded permissions.

I did some trial and error and found that the user/group is apache:nobody.

I set the umaks to

[root@nx01 upload]# umask -S
u=rwx,g=rwx,o=rwx

Still getting the same errors.

Config override

The config override file exists but is not writeable. Please take the necessary steps to make the file writeable. Depending on your Operating system, this might require you to change the permissions by running chmod 766, or to right click on the filename to access the properties and uncheck the read only option.

Writeable Custom Directory

The Custom Directory exists but is not writeable. You may have to change permissions on it (chmod 766) or right click on it and uncheck the read only option, depending on your Operating System. Please take the needed steps to make the file writeable.

Writable Cache Sub-Directories

The files or directories listed below are not writeable or are missing and cannot be created. Depending on your Operating System, correcting this may require you to change permissions on the files or parent directory (chmod 755), or to right click on the parent directory and uncheck the ‘read only’ option and apply it to all subfolders.

Please fix the following files or directories before proceeding:
/var/www/html/CRM/cache/
/var/www/html/CRM/cache/images
/var/www/html/CRM/cache/layout
/var/www/html/CRM/cache/pdf
/var/www/html/CRM/cache/xml
/var/www/html/CRM/cache/include/javascript

Writable Modules Sub-Directories and Files

Warning: Not Writable
Please fix the following module directories and the files under them before proceeding:
/modules

Writable Upload Directory

Warning: Not Writable

Not sure where else to check.

That’s it, now do a
ls -al
of each file or directory mentioned as non-writeable. This way we’ll see what is there actually.

And see my “cron” question above. You can check the crontab of individual users like this:
crontab -l -u nobody
crontab -l -u root

I found the problem late last night and it was not in the permissions. The issue was actually an SELinux setting that needed to be modified. SELinux was running in enforcing mode and I needed to change it to Permissive mode.

Here is a link to the information I used to change the setting.

https://wiki.gentoo.org/wiki/SELinux/Tutorials/Permissive_versus_enforcing

I appreciate all of the help.

1 Like

Thanks you sooooo much! If I found one more post with a link to the install permissions I was going to lose my s#it!
Workd on Fedora 27 too