No announcement yet.

Database Cache errors after PL1 Update (continues with PL2)

  • Filter
  • Time
  • Show
Clear All
new posts

  • Database Cache errors after PL1 Update (continues with PL2)

    I am receiving a large amount of database errors around 24 hours after restarting the environment, this has happened since the 5.5.4 Patch Level 1 (on PL2 Now) Update. Only way to rectify the issue is to bump MySQL and clear cache. It will crop up again after 24 hours or so. I have adjusted the lockout values to a higher amount (per a forum post i found for an earlier version) but the issue still remains.

    Server is IIS on Server 2019, PHP 7.3.7 and MySQL 5.7.27

    Database error in vBulletin 5.5.4:

    Invalid SQL:
    /** saveDbCache */REPLACE INTO cacheevent (cacheid, event) values

    MySQL Error : Lock wait timeout exceeded; try restarting transaction
    Error Number : 1205
    Request Date : Sunday, September 29th 2019 @ 01:23:24 PM
    Error Date : Sunday, September 29th 2019 @ 01:25:05 PM
    Script :
    Referrer :
    IP Address :
    Username : Guest
    Classname : vB_Database_MySQLi
    MySQL Version :

    Stack Trace:
    #0 vB_Database->getErrorData() called in [path]\vb\database.php on line 1207
    #1 vB_Database->halt() called in [path]\vb\database\mysqli.php on line 249
    #2 vB_Database_MySQLi->execute_query() called in [path]\vb\database.php on line 561
    #3 vB_Database->query_write() called in [path]\vb\db\mysql\querydefs.php on line 7206
    #4 vB_dB_MYSQL_QueryDefs->saveDbCache() called in [path]\vb\db\query\method.php on line 175
    #5 vB_dB_Query_Method->execSQL() called in [path]\vb\db\assertor.php on line 301
    #6 vB_dB_Assertor->assertQuery() called in [path]\vb\cache\db.php on line 387
    #7 vB_Cache_Db->shutdown() called in [path]\vb\shutdown.php on line 93
    #8 vB_Shutdown->shutdown() called in [path]\vb\vb.php on line 483
    #9 vB::shutdown() called in on line

    I tossed a support ticket in as soon as the issue cropped up but have not heard anything after a week. I'm currently watching out for these DB error emails and bumping MySQL when the issue crops up, but obviously I cannot keep doing that.

    Any assistance would be appreciated. Forum was operating perfectly prior to PL1

  • #2
    Retracted - I had tightened my DB permissions after the hack and the clear cache option in the ACP was just asking for Drop permissions.

    Error Invalid SQL: TRUNCATE TABLE cacheevent /**truncateTable**/;

    Exception trace:
    ## /home/.../public_html/core/vb/database.php(1208) Exception Thrown #0 /home/.../public_html/core/vb/database/mysqli.php(249): vB_Database->halt() #1 /home/.../public_html/core/vb/database.php(561): vB_Database_MySQLi->execute_query(true, Object(mysqli)) #2 /home/.../public_html/core/vb/db/mysql/querydefs.php(6878): vB_Database->query_write('Invalid SQL:\r\nT...') #3 /home/.../public_html/core/vb/db/query/method.php(175): vB_dB_MYSQL_QueryDefs->truncateTable(Array, Object(vB_Database_MySQLi), false, false) #4 /home/.../public_html/core/vb/db/assertor.php(301): vB_dB_Query_Method->execSQL() #5 /home/.../public_html/core/vb/cache/db.php(301): vB_dB_Assertor->assertQuery('truncateTable', Array) #6 /home/.../public_html/core/vb/cache.php(244): vB_Cache_Db->clean(false) #7 /home/.../public_html/core/admincp/misc.php(67): vB_Cache::resetCache() #8 /home/.../public_html/includes/api/interface/collapsed.php(142): require_once('/home/.../pu...') #9 /home/.../public_html/includes/vb5/frontend/controller/relay.php(33): Api_Interface_Collapsed->relay('admincp/') #10 /home/.../public_html/index.php(74): vB5_Frontend_Controller_Relay->admincp('misc.php') #11 {main}
    Last edited by woodmj; Mon 7 Oct '19, 1:28am.


    • #3
      Update on the issue, did some testing and simply bumping MySQL free's it up (without clearing Cache). Still not sure what the issue is and Its happening about every 12 or so hours at this point.


      • #4
        Does anyone have any thoughts? Support has ignored every inquiry I've made, its happening every day and I'm running out of ideas.


        • #5
          You should truncate the table using a user that has permission to do so. This doesn't necessarily need to be the user that you run vBulletin with.

          However in order for the software to properly maintain itself during normal operations, it needs delete permissions on all tables.
          Translations provided by Google.

          Wayne Luke
          The Rabid Badger - a vBulletin Cloud demonstration site.
          vBulletin 5 API


          Related Topics