Announcement

Collapse
No announcement yet.

Did repairs, checks and still get db errors

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

  • Wayne Luke
    replied
    Shut down your forums.
    Repair Table
    Backup Table
    Drop table
    Recreate table
    Import backup.

    Leave a comment:


  • jasonlitka
    replied
    Do you have a recent backup you can restore to see if the problems go away?

    Leave a comment:


  • ferreo
    replied
    Originally posted by jason|xoxide View Post
    Are you sure you have plenty of disk space free (for the data, for mysql's temp location, and for your log files)?


    Plenty. It's a RAID10 with plenty of gigs of free space.

    Leave a comment:


  • jasonlitka
    replied
    Are you sure you have plenty of disk space free (for the data, for mysql's temp location, and for your log files)?

    Leave a comment:


  • Wayne Luke
    replied
    Repeated table crashing would signify a problem with your MySQL installation or that it is being shutdown improprely (while the files are open). Make sure that your MySQL server has appropriately sized temporary partitions. You should make sure these are at least twice the size as your largest table.

    Leave a comment:


  • ferreo
    replied
    Originally posted by jason|xoxide View Post
    "-o" is the same as "REPAIR TABLE ... EXTENDED" so if that doesn't work, all that's left is to restore from a backup or to run "REPAIR TABLE ... USE_FRM" (which will break your auto-index numbers so you'd need to fix those manually).
    Thanks jason, I will keep that in mind. In the meanwhile, I am wondering if it may be a problem with disks, or a MySQL/PHP bug that is causing this.

    Leave a comment:


  • jasonlitka
    replied
    "-o" is the same as "REPAIR TABLE ... EXTENDED" so if that doesn't work, all that's left is to restore from a backup or to run "REPAIR TABLE ... USE_FRM" (which will break your auto-index numbers so you'd need to fix those manually).

    Leave a comment:


  • ferreo
    replied
    Originally posted by Floris View Post
    MySQL error code 126: Index file is crashed

    Not sure yet how to properly fix this.
    I am currently running a myisamchk -o, it's taking forever but maybe it'll take care of things.

    Leave a comment:


  • Floris
    replied
    MySQL error code 126: Index file is crashed

    Not sure yet how to properly fix this.

    Leave a comment:


  • ferreo
    replied
    Forgot to mention:

    I also tried to disable hooks in config.php, still got the same error.

    Leave a comment:


  • ferreo
    started a topic Did repairs, checks and still get db errors

    Did repairs, checks and still get db errors

    I previously had a single www server and single db server setup for my forum. Ever since I upgraded to two load balanced web servers and a new version of MySQL on the database server, I get weird errors like

    Code:
    Database error in vBulletin 3.6.5:
    
    Invalid SQL:
    UPDATE post SET
       title = 'MORE added - April 1st increase'
    WHERE postid = 2269540;
    
    MySQL Error  : Incorrect key file for table './pbvb/post.MYI'; try to repair it
    Error Number : 126
    Date         : Tuesday, April 3rd 2007 @ 10:28:03 AM
    Script       : http://forum.purseblog.com/postings.php?do=domergethread&t=113954
    Referrer     : http://forum.purseblog.com/postings.php?t=113954&pollid=
    IP Address   : 84.167.110.210
    Username     : Vlad
    Classname    : vB_Database
    I get such errors when trying to merge threads or edit certain posts. I ran a "Fix Unique Indexes", I repaired post.MYI and thread.MYI multiple times, and even ran the myisamchk -f on the tables while mysql was shut down.

    I still get this error... I run PHP 5.2.0 and MySQL 5.0.27.

    Please advise what else I should try.
    Last edited by ferreo; Tue 3 Apr '07, 9:53am.
Loading...
Working...
X