I tried with a simpler password, it shows blank page again, seems like SuiteCRM cannot access the database.
Any other suggestion? Thanks
It is cloud MySQL VM.
You need to go through all possible logs until you find a message telling you whatās wrongā¦
Here are all the ones I can think of, in order of probability of being relevant to this case:
- some mysql log file
- php_errors.log
- suitecrm.log
- install.log
- other apache logs, like access.log and error.log
- upgradeWizard.log
I cannot find suitecrm.log and install.log in my suitecrm folder.
This log need create by myself?
You donāt need to create any log file manually.
Itās normal for suitecrm.log not to exist until after installation.
install.log should exist since the beginning of the installation process.
After installation, I donāt have any .log files in suitecrm folder.
I think this is unusual.
Yes, I think your ownerships/permissions are still not right, SuiteCRM probably is unable to write files.
How to fix this problem?
I gave all files to apache:apache
Many posts ago I asked you for a ls -al of your SuiteCRM dir. It would have given me more precise information to help you.
My guess is that your web server is running under user crm-test-admin so you would need to chown to that user and group.
[root@iZj6c9ipfjhle2a46dwllvZ suitecrm]# ls -al total 1372 drwxr-xr-x. 20 apache apache 4096 Apr 7 17:29 . drwxr-xr-x. 3 apache apache 4096 Apr 1 11:29 .. -rwxr-xr-x. 1 apache apache 411 Mar 2 2018 bower.json drwxr-xr-x. 2 apache apache 4096 Mar 2 2018 build drwxrwxr-x. 14 apache apache 4096 Apr 1 17:21 cache -rwxr-xr-x. 1 apache apache 3587 Mar 2 2018 campaign_tracker.php -rwxr-xr-x. 1 apache apache 3094 Mar 2 2018 CODE_OF_CONDUCT.md -rwxr-xr-x. 1 apache apache 1027 Mar 2 2018 composer.json -rwxr-xr-x. 1 apache apache 115616 Mar 2 2018 composer.lock -rwxr-xr-x. 1 apache apache 11277 Apr 6 18:02 config.php -rwxr-xr-x. 1 apache apache 5052 Mar 2 2018 cron.php -rwxr-xr-x. 1 apache apache 2446 Mar 2 2018 crossdomain.xml drwxrwxr-x. 11 apache apache 4096 Apr 7 17:16 custom drwxrwxr-x. 3 apache apache 4096 Mar 2 2018 data -rwxr-xr-x. 1 apache apache 2386 Mar 2 2018 dictionary.php -rwxr-xr-x. 1 apache apache 12566 Mar 2 2018 download.php -rwxr-xr-x. 1 apache apache 2390 Mar 2 2018 emailmandelivery.php -rwxr-xr-x. 1 apache apache 4918 Mar 2 2018 export.php -rwxr-xr-x. 1 apache apache 967627 Mar 2 2018 files.md5 -rwxr-xr-x. 1 apache apache 2808 Mar 2 2018 HandleAjaxCall.php -rwxr-xr-x. 1 apache apache 1566 Apr 1 17:21 .htaccess -rwxr-xr-x. 1 apache apache 2367 Mar 2 2018 ical_server.php drwxr-xr-x. 58 apache apache 4096 Mar 2 2018 include -rwxr-xr-x. 1 apache apache 2374 Mar 2 2018 index.php drwxr-xr-x. 6 apache apache 4096 Mar 2 2018 install -rwxr-xr-x. 1 apache apache 31893 Mar 2 2018 install.php -rwxr-xr-x. 1 apache apache 2275 Mar 2 2018 json_server.php drwxr-xr-x. 3 apache apache 4096 Mar 2 2018 jssource drwxr-xr-x. 6 apache apache 4096 Mar 2 2018 lib -rwxr-xr-x. 1 apache apache 34539 Mar 2 2018 LICENSE.txt -rwxr-xr-x. 1 apache apache 2313 Mar 2 2018 log_file_restricted.html -rwxr-xr-x. 1 apache apache 2376 Mar 2 2018 maintenance.php drwxr-xr-x. 2 apache apache 4096 Mar 2 2018 metadata drwxr-xr-x. 3 apache apache 4096 Mar 2 2018 ModuleInstall drwxrwxr-x. 122 apache apache 4096 Apr 7 16:58 modules -rwxr-xr-x. 1 apache apache 2886 Mar 2 2018 pdf.php -rwxr-xr-x. 1 apache apache 304 Mar 2 2018 php_version.php -rwxr-xr-x. 1 apache apache 3758 Mar 2 2018 README.md -rwxr-xr-x. 1 apache apache 73 Mar 2 2018 robots.txt -rwxr-xr-x. 1 apache apache 3588 Mar 2 2018 run_job.php drwxr-xr-x. 12 apache apache 4096 Mar 2 2018 service drwxr-xr-x. 2 apache apache 4096 Mar 2 2018 soap -rwxr-xr-x. 1 apache apache 3929 Mar 2 2018 soap.php -rwxr-xr-x. 1 apache apache 5327 Mar 2 2018 SugarSecurity.php -rwxr-xr-x. 1 apache apache 154 Mar 2 2018 sugar_version.json -rwxr-xr-x. 1 apache apache 2296 Mar 2 2018 sugar_version.php -rwxr-xr-x. 1 apache apache 170 Mar 5 2018 suitecrm_version.php drwxrwxr-x. 4 apache apache 4096 Mar 2 2018 themes -rwxr-xr-x. 1 apache apache 5839 Mar 2 2018 TreeData.php drwxrwxr-x. 3 apache apache 4096 Apr 7 16:58 upload -rwxr-xr-x. 1 apache apache 2248 Mar 2 2018 vcal_server.php -rwxr-xr-x. 1 apache apache 2976 Mar 2 2018 vCard.php drwxr-xr-x. 18 apache apache 4096 Mar 2 2018 vendor drwxr-xr-x. 2 apache apache 4096 Mar 2 2018 XTemplate drwxr-xr-x. 7 apache apache 4096 Mar 2 2018 Zend
how to check my web server is running apache or crm-test-admin?
ps -ef | egrep '(httpd|apache2|apache)' | grep -v `whoami` | grep -v root | head -n1 | awk '{print $1}'
The result is apache
Then Iām sorry, I canāt figure it out. Maybe something else is still keeping the file accesses from working.
Perhaps you could try, just as a test, giving it all 777 permissions and see if it works. Then set the permissions back to something safer. This would just be a step in our diagnosis.
I think it should be permissions problem, because I using another one Window IIS SuiteCRM for testing, SuiteCRM can access the database.
Apr 8 16:30:07 iZj6c9ipfjhle2a46dwllvZ setroubleshoot: SELinux is preventing /usr/sbin/httpd from write access on the directory /var/www/html/suitecrm. For complete SELinux messages run: sealert -l 2a348d5f-e2cd-4531-b4c6-7c8173579664 Apr 8 16:30:07 iZj6c9ipfjhle2a46dwllvZ python: SELinux is preventing /usr/sbin/httpd from write access on the directory /var/www/html/suitecrm.#012#012***** Plugin httpd_write_content (92.2 confidence) suggests ***************#012#012If you want to allow httpd to have write access on the suitecrm directory#012Then you need to change the label on '/var/www/html/suitecrm'#012Do#012# semanage fcontext -a -t httpd_sys_rw_content_t '/var/www/html/suitecrm'#012# restorecon -v '/var/www/html/suitecrm'#012#012***** Plugin catchall_boolean (7.83 confidence) suggests ******************#012#012If you want to allow httpd to unified#012Then you must tell SELinux about this by enabling the 'httpd_unified' boolean.#012#012Do#012setsebool -P httpd_unified 1#012#012***** Plugin catchall (1.41 confidence) suggests **************************#012#012If you believe that httpd should be allowed write access on the suitecrm directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'httpd' --raw | audit2allow -M my-httpd#012# semodule -i my-httpd.pp#012
I find it in /var/log/messages
SELINUX donāt give a write access to suitecrm folder?
Yes I often see people with SELinux issues here on the Forums. I would recommend that you install this on Ubuntu instead if you can, itās by far the most tested platform for SuiteCRM, and the one the SalesAgility Team always uses.
Of course CentOS is a good option also, but itās just that the SELinux that comes with it is a peculiar admin skill you need to have, otherwise you will be faced with these problemsā¦
If I disable SELinux, will be solve the problem?
I had to setup a test system on CentOS some time ago, these were the commands that I used to ādisarmā SELinux:
# fixing access / SELinux
setsebool -P httpd_can_network_connect 1
setsebool -P httpd_can_network_connect_db 1
setsebool -P httpd_can_sendmail 1
setsebool -P httpd_unified 1
cd /var/www/html
chcon -R -t httpd_sys_content_rw_t /var/www/html
tbh I believe I found them here in another thread, but it worked out quite nicely.
1 Like
It work!!!
All about SELinux problem.
Many thanks diligent and prg bros
2 Likes