MySQL connection shaky after upgrade

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • janaf
    Senior Member
    • Dec 2009
    • 245
    • 4.0.0

    [Forum] MySQL connection shaky after upgrade

    Í had to reinstall MySQl and read back the database for a vBulletin site.

    It works fairly well but there are issues:

    1. In the ACP I get the Login prompt all the time, almost whatever I do. I login and can continue.

    2. I frequently loose connection with the SQL server, with the message:

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

    Could someone help

    The front-end works but frequently gives database connection errors too.
    Where do I start?!?
    Last edited by janaf; Sat 29 Oct '11, 12:26am.
  • janaf
    Senior Member
    • Dec 2009
    • 245
    • 4.0.0

    #2
    Done some more digging.

    In the MySQL error log I find (part of a longer message)

    InnoDB: Serious error! InnoDB is trying to free page 93558
    InnoDB: though it is already marked as free in the tablespace!
    InnoDB: The tablespace free space info is corrupt.
    InnoDB: You may need to dump your InnoDB tables and recreate the whole
    InnoDB: database!
    InnoDB: Please refer to
    InnoDB: http://dev.mysql.com/doc/refman/5.1/...-recovery.html
    InnoDB: about forcing recovery.
    111027 1:02:12 InnoDB: Assertion failure in thread 140477374269184 in file ../../../storage/innobase/fsp/fsp0fsp.c line 3007
    InnoDB: We intentionally generate a memory trap.
    InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
    InnoDB: If you get repeated assertion failures or crashes, even
    InnoDB: immediately after the mysqld startup, there may be
    InnoDB: corruption in the InnoDB tablespace. Please refer to
    InnoDB: http://dev.mysql.com/doc/refman/5.1/...-recovery.html
    InnoDB: about forcing recover
    Any more hands-on help on how to recover my database?

    Comment

    • janaf
      Senior Member
      • Dec 2009
      • 245
      • 4.0.0

      #3
      Solved. Dumped all the databases, deleted the log files and imported the databases again.
      This got rid of the old MySQL log files which where corrupt.

      Comment

      widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
      Working...