I have installed suitectrm a few times, but this time, it is causing errors.
I followed the basic steps on the install process where you change the ownership and modify permissions. This worked find.
First of all, I get errors saying that I can not write a config.php file, or a .htaccess file. What can I do to remove these errors during install.
IO do create these files, as the installscript says I need to make them to allow the install to continue.
The install process (after the two errors fro config an dhtaccess, seems to stop at this point:
Creating default SuiteCRM data
Creating default users... done
Creating default scheduler jobs... done
It does not continue on to the normal screen where it asks you if you want to log in.
I installed 7.10.6 on my server not only 3 weeks back with no issues.
Any where to look? Pointers?
Thanks
Joseph
Your permissions might need to be different this time, if your web server is running under a different user name or has some other constraints.
Any way, I would start by looking at all the logs to see where it’s failing…
suitecrm.log
php_errors.log (or whatever your web server log is called)
install.log or upgradeWizard.log
Hello,
Thanks for the ideas. i will look the logs and see if I find anything, and understand things. I will share them,.
As for the server, the user was the same, but the domain changed. Same server, with no changes on the server.
I will be back later with news of some sort.
Thanks
Joe
pgr:
Your permissions might need to be different this time, if your web server is running under a different user name or has some other constraints.
Any way, I would start by looking at all the logs to see where it’s failing…
suitecrm.log
php_errors.log (or whatever your web server log is called)
install.log or upgradeWizard.log
Hello,
I looked and the suitecerm log was nto yet created.
As for the install.log file, I can not fidn it:(
Can tell em where it is?
Joseph
Hello,
I have tried thsi install a few times. Each time, same error.
But, you seemed ot have helped me with th esam eexact error awhile back:
https://suitecrm.com/suitecrm/forum/installation-upgrade-help/14585-can-not-write-config-php-and-htaccess-errors
It was an issue with the suitecrm folder. It was owned by root, but my the right owners.
But, I tried the same thing, by changing the permissions of the directory.
I’d love to troubel shoot it again with you, because I am sure I did all the steps.
I will even check all before I try installing.
Thanks
Joseph
I also use teh following top prepare files for installation:
sudo chown -R web3:client2 .
sudo chmod -R 755 .
sudo chmod -R 775 cache custom modules themes data upload
sudo chmod 775 config_override.php 2>/dev/null
Taken from:
https://docs.suitecrm.com/admin/installation-guide/downloading--installing/
Thanks
Joseph
The install.log should be at the root of your SuiteCRM installation.
Which web server are you using, is it Apache? If so, try this command
ps -ef | egrep '(httpd|apache2|apache)' | grep -v `whoami` | grep -v root | head -n1 | awk '{print $1}'
That should give you the user name that the web server is using. We need to check if that “web3” thing is good for this server also.
Hello,
I have had a busy few days. Sorry fr the delay.
The response is:
www-data
Thanks
Joseph
Hello,
Just to explain the web3 thing.
I use ISPConfig, a cpanel like software t manage my domains, emails, etc…
web3 is the identity of a given website.
client2 is my identity on the server.
Thanks
Joseph
pgr
17 July 2018 11:25
10
Ok, so if you web server user is www-data, do your chown like this, from the SuiteCRM root directory:
chown -R www-data:www-data .
Thansk for the tip.
But, do I need to chown all files in the folder?
This is also weird, because have another CRM installed on the same server, under a different domain name. It works fine with the web2:client2 ownership.
Thanks for the help.
Joseph
pgr
17 July 2018 15:13
12
That depends on which groups each user belongs to. If your www-data is part of a group called client2 then things are different. You just have to make the whole thing coherent.
Linux permissions are a cross between ALL these things:
So any question about which settings are adequate needs to be thorough and include ALL those things