When I try to send a test email, the resulting error is in three parts.
Tue Oct 31 20:51:40 2017 [FATAL] SugarPHPMailer encountered an error: An outgoing mail server is not configured to send emails. Please configure an outgoing mail server or select an outgoing mail server for the mail account that you are using in Settings >> Mail Account.
Tue Oct 31 20:51:40 2017 [FATAL] SugarPHPMailer encountered an error: SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
Tue Oct 31 20:51:40 2017 [-none-][FATAL] Retrieving record by id users:1 found Query Failed: SELECT users.* FROM users WHERE users.id = ‘1’ AND users.deleted=0 LIMIT 0,1: MySQL error 2006: MySQL server has gone away
I have to assume these errors are all related based on the timestamp of their creation. Since the crontab edit did not fix this, do you want to try something else?
How did you set the timezone? Was it with the command-line parameter? I’d like to have a confirmation if that works.
The SMTP errors we can handle on the other thread.
The “SQL has gone away” error is problematic, it’s SQL crashing or timing out. I sure hope it disappears when you fix the SMTP problems, if not, you’ll have to check your database setup, corruption, rebuild indexes, etc.
Sorry, I have to reopen this thread. As I resumed troubleshooting this morning I realized there was a typo in my crontab and the timezone error did not go away, the cronjob simply was not running. Upon resuming the cronjob, the error reappeared, so I loaded a new php.ini file in the root directory and changed some settings to confirm Suite was pulling the right information. I changed my max post size and the diagnostic tool picked up the change immediately, so I know it is seeing the correct PHP configuration. With that said, the time zone is set correctly in the file, but SuiteCRM is still throwing the error. I tried manually passing the timezone variable in the crontab, as you suggested, but that did not fix the error.