Announcement

Collapse
No announcement yet.

MySQL Error : MySQL server has gone away Error Number : 2006

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • MySQL Error : MySQL server has gone away Error Number : 2006

    I've seen this a few times in the last 2 months. I've restarted the db, but has since returned.

    Thoughts?


    Invalid SQL:
    /** saveDbCache */ SELECT * FROM vb3cacheevent WHERE cacheid IN ('node_494069_lvl1data');

    MySQL Error : MySQL server has gone away
    Error Number : 2006
    Request Date : Monday, February 18th 2019 @ 04:30:48 AM
    Error Date : Monday, February 18th 2019 @ 04:35:49 AM
    Script : https://www.adkhighpeaks.com/forums/...etch?id=494069
    Referrer :
    IP Address : 141.8.143.168
    Username : Guest
    Classname : vB_Database_MySQLi
    MySQL Version :


    Stack Trace:
    #0 vB_Database->getErrorData() called in [path]/vb/database.php on line 1188
    #1 vB_Database->halt() called in [path]/vb/database/mysqli.php on line 201
    #2 vB_Database_MySQLi->execute_query() called in [path]/vb/database.php on line 557
    #3 vB_Database->query_read() called in [path]/vb/db/mysql/querydefs.php on line 7179
    #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 304
    #6 vB_dB_Assertor->assertQuery() called in [path]/vb/cache/db.php on line 390
    #7 vB_Cache_Db->shutdown() called in [path]/vb/vb.php on line 481
    #8 vB::shutdown() called in on line
    Organizations must hire quality people — "If you hire stupid people, they are not going to get better over time," ~ Gordon Graham.

    vB Mods That Rock!

  • #2
    I think your server ran out of memory.

    Comment


    • In Omnibus
      In Omnibus commented
      Editing a comment
      I should add the image opened perfectly well for me and took less than one second to do so.

  • #3
    If you had run out of memory, you would get different errors. This error specifically means that MySQL closed the connection before it returned a result. It could be because the query took too long to complete based on the wait_timeout specified in its configuration files. We recommend at least an 120 second wait_timeout. The default is 28800 seconds or 8 hours. It could also be that the query is too large to return to PHP.

    To resolve the issue immediately, I recommend running these queries:
    Code:
    truncate table cache;
    truncate table cacheevents;
    Depending on your server setup, you may have to run these periodically. You don't need to restart the server.



    Translations provided by Google.

    Wayne Luke
    The Rabid Badger - a vBulletin Cloud customization and demonstration site.
    vBulletin 5 Documentation - Updated every Friday. Report issues here.
    vBulletin 5 API - Full / Mobile
    I am not currently available for vB Messenger Chats.

    Comment


    • #4
      Originally posted by Wayne Luke View Post
      Depending on your server setup, you may have to run these periodically. You don't need to restart the server.
      Could/would this be a cron job?

      Organizations must hire quality people — "If you hire stupid people, they are not going to get better over time," ~ Gordon Graham.

      vB Mods That Rock!

      Comment


      • In Omnibus
        In Omnibus commented
        Editing a comment
        Joe released something for this as a cron job on vBulletin.org

      • NumNum
        NumNum commented
        Editing a comment
        I'll look for that. Thank You.

    • #5
      The interesting thing is the wait_timeout variable was set to 300 seconds, and not the recommended 28800. I have requested the threshold be changed.
      Last edited by NumNum; Mon 25th Feb '19, 10:22am.
      Organizations must hire quality people — "If you hire stupid people, they are not going to get better over time," ~ Gordon Graham.

      vB Mods That Rock!

      Comment

      Related Topics

      Collapse

      Working...
      X