database errors - need help!

Permalink November 13, 2008 at 10:40 AM

hi, just wondering if anyone can help translate what this means below?

thanks!

Fatal error: Uncaught exception 'ADODB_Exception' with message 'mysql error: [1053: Server shutdown in progress] in EXECUTE("select Pages.cID, Pages.pkgID, Pages.cPointerID, Pages.cPointerExternalLink, Pages.cFilename, Collections.cDateAdded, Pages.cDisplayOrder, Collections.cDateModified, cInheritPermissionsFromCID, cInheritPermissionsFrom, cOverrideTemplatePermissions, cPendingAction, cPendingActionUID, cPendingActionTargetCID, cPendingActionDatetime, cCheckedOutUID, cIsTemplate, uID, cPath, Pages.ctID, ctHandle, ctIcon, ptID, cParentID, cChildren, ctName from Pages inner join Collections on Pages.cID = Collections.cID left join PageTypes on (PageTypes.ctID = Pages.ctID) left join PagePaths on (Pages.cID = PagePaths.cID) where Pages.cID = 1") ' in /home/a8880993/public_html/concrete/libraries/3rdparty/adodb/adodb-exceptions.inc.php:78 Stack trace: #0 /home/a8880993/public_html/concrete/libraries/3rdparty/adodb/adodb.inc.php(918): adodb_throw('mysql', 'EXECUTE', 1053, 'Server shutdown...', 'select Pages.cI...', false, Ob in /home/a8880993/public_html/concrete/libraries/3rdparty/adodb/adodb-exceptions.inc.php on line 78

zit replied on Nov 13, 2008 at 3:42 pm Permalink Reply

Looks like it could be a few things: some hosting environments have a thread of their own which does a KILL QUERY or KILL CONNECTION on MySQL transactions they think are taking too long. Perhaps your host thought concrete5 was taking too long with it's mysql query?

Or it could be something in the code where they have one session, running a "long" select, then, from another session, they kill that first one, but the other select is still running, and then the server will send out a message "Server shutdown in progress" because it wasn't done doing the first long select when it was killed.

Which really doesn't help you fix it but tries to explain what might be going on.