We are experiencing page timeuts (Server error 500) for the past several days. When we edit a lead, Account, Contact, … and click on the Save button we eventually get a error 500 . If we refresh it will work. The permissions on all the files and directories is 0755 and using the same user, not root. We did a fresh install this past May and it has been running fine on a Centos 6 machine. We get the same result whether we use Chrome or Edge as the browser. The server is on our local network. We upgraded to Suite CRM 7.8.5 this am with no relief. I edited a contact by adding an email address, I used the “Save & Continue” and the page refreshed and the next contact was presented. Going back to the contact that was edited, the new content is missing. Anyone have any idea what might be going on?
Have you tried a Quick Repair and Rebuild? And some other Repairs?
There is a setting in php.ini to control timeouts, but it is usually at least 60 seconds, and you’re not waiting for 60 seconds before you see the 500 errors, are you?
You should start by checking your logs for any errors at the time of the timeouts.
Then you might have to look into your database performance, you might have too much data, or a corrupted index, or something.
If you know how to use phpMyAdmin or MySQL, here’s a fancy query to get a view of your database sizes:
SELECT CONCAT(table_schema, '.', table_name),
CONCAT(ROUND(table_rows / 1000000, 2), 'M') rows,
CONCAT(ROUND(data_length / ( 1024 * 1024 * 1024 ), 2), 'G') DATA,
CONCAT(ROUND(index_length / ( 1024 * 1024 * 1024 ), 2), 'G') idx,
CONCAT(ROUND(( data_length + index_length ) / ( 1024 * 1024 * 1024 ), 2), 'G') total_size,
ROUND(index_length / data_length, 2) idxfrac
FROM information_schema.TABLES
ORDER BY data_length + index_length DESC
LIMIT 10;
Thanks for the ideas.
I ran the query and almost all the entries are 0.00. The timeout is at 30 seconds. PHP.ini shows it set at 60 seconds. This issue appears to rear its ugly head when there is either a create or edit record is in progress. From the HTTPD error Log:
[Thu Aug 24 10:42:07 2017] [error] [client 192.168.0.68] PHP Strict Standards: Declaration of MyAccountsDashlet::process() should be compatible with DashletGeneric::process($lvsParams = Array, $id = NULL) in /var/www/html/CRM/modules/Accounts/Dashlets/MyAccountsDashlet/MyAccountsDashlet.php on line 48, referer: http://192.168.0.251/CRM/index.php
No errors in the php log.
Having this same issue and it’s driving us nuts. Any ideas?
@direshark, it’s better if you start your own thread.
List your versions of OS, PHP, Web Server, MySQL, and SuiteCRM.
Use the suggestions given here, tell us what you found in your logs, etc.
We were experiencing virtually identical issues that the original poster had, down to the errors received in the logs.
After long chats with the host and our dev team (the host had no idea, memory adjustments did nothing), we discovered the issue was because (I think) some scheduler mysteriously stopped working about a month ago, causing the indexing process to fail. A quick fix to this is to disable AOD, which we’ve done while we get the scheduler issue sorted out.
Hopefully, this is of use to anyone finding themselves in a similar position.
You might be interested in this article then