Need help interpreting and solving mysql error when accessing dahsboard

Permalink
I'm looking for help interpreting an error message and some advice about how to fix it. The only solutions I've seen for this problem in the forums are to modify the server configuration (which I don't know anything about) or to re-update (although I was not updating when the problem started). I am more of a designer than a developer and have reached the limit of my understanding, so I'm hoping to find someone who can explain some of this in layperson terms and help me decide what to do next.

I can log in to the site, but when trying to access the dashboard I get this:

Fatal error: Uncaught exception 'ADODB_Exception' with message 'mysqlt error: [2006: MySQL server has gone away] in EXECUTE("SELECT TABLE_NAME, CASE WHEN TABLE_TYPE = 'VIEW' THEN 'V' ELSE 'T' END FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA=SCHEMA()") ' in /home/manufac3/public_html/updates/concrete5.6.3.1/concrete/libraries/3rdparty/adodb/adodb-exceptions.inc.php:78 Stack trace: #0 /home/manufac3/public_html/updates/concrete5.6.3.1/concrete/libraries/3rdparty/adodb/adodb.inc.php(1074): adodb_throw('mysqlt', 'EXECUTE', 2006, 'MySQL server ha...', 'SELECT TABLE_NA...', false, Object(ADODB_mysqlt)) #1 /home/manufac3/public_html/updates/concrete5.6.3.1/concrete/libraries/3rdparty/adodb/adodb.inc.php(1049): ADOConnection->_Execute('SELECT TABLE_NA...', false) #2 /home/manufac3/public_html/updates/concrete5.6.3.1/concrete/libraries/3rdparty/adodb/adodb.inc.php(2334): ADOConnection->Execute('SELECT TABLE_NA...') #3 /home/manufac3/public_html/updates/concrete5.6.3.1/concrete/libraries/3rdparty/adodb/drivers/adodb-mysql.inc. in /home/manufac3/public_html/updates/concrete5.6.3.1/concrete/libraries/3rdparty/adodb/adodb-exceptions.inc.php on line 78

The timeline of events (not sure if they are all relevant or not) is this:
- 2 weeks ago, we moved to a new host (the host did the migration for us)
- over this past weekend, the host did server maintenance (something like upgrading cPanel, but I'm not totally sure)
- on Monday, I was able to log in, browse the site like normal, and edit pages, but trying to access the dashboard resulted in a 504 timeout error.
- talked to the host who, after a long detour down a different path, set the dynamic timeout value for index.php in our account to 300 seconds
- after this, there was no timeout error, but we are now getting the fatal error listed above instead
- the host tells me now that there's nothing more they can do and that we need to hire a mySQL developer to optimize queries and scripts

Things I have tried:
- restoring mySQL and files backups from last Friday, where everything was working fine (did this through cPanel)
- downloaded fresh version of Concrete5.6.3.1 and replaced the existing directory in the /updates folder
- manually ran the upgrade script (which, predictably, told me it was already on the current version)
- verified that the version in SITE_APP_VERSION in config table is 5.6.3.1, as is DIRNAME_APP_UPDATED in site.php. (Although there is a line for SITE_INSTALLED_APP_VERSION that says 5.6.0.1, and I'm not sure what it means or why it's a different version)

Please let me know if you think you can help and if you have any kind of cost estimate. Thanks!

 
mhawke replied on at Permalink Reply
mhawke
The "server has gone away" indicates a failing mySQL server. In my experience, I would seriously consider migrating to a new host. Who is the host?
DustyStrings replied on at Permalink Reply
The host is Siteground, who we just moved to because they assured us they had lots of experience with Concrete5 sites and could guarantee better performance than our last host. Well, the speed has been much better and in general their support has been great, but we're stuck on this particular issue.
mhawke replied on at Permalink Reply
mhawke
I have lots of sites on Siteground and I like them very much. I have occasionally seen this error message (perhaps twice in 2 years)

I'll have a closer look at the error message.
exchangecore replied on at Permalink Reply
exchangecore
MySQL has gone away is a host related issue, nothing you can do from your end other than let them know it's happening. They should be able to pretty quickly track down the errors in the MySQL log files.

Not sure if siteground uses remote MySQL databases or uses localhost, if remote it could actually be a network issue.
DustyStrings replied on at Permalink Reply
Thanks for the advice. The host said there was nothing else they could do, and a week later the problem disappeared, so maybe they were able to change something. In any case, it's mysteriously solved for now!