Table 'language' is marked as crashed and should be repaired

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • dirknerkle
    Member
    • May 2013
    • 33
    • 5.6.3

    Table 'language' is marked as crashed and should be repaired

    This keeps happening but repairing/reindexing the table (there is 1 record in it) seems futile -- whenever I check it, it always shows as OK.
    It's error # 1194, and in examining the 1-record table, many fields are null.
    My forum is using MySQL 5.5.44 and is hosted on a debian platform.

    Below is a copy of the error log that occurs. Any help anyone can offer would be greatly appreciated -- this is the only error I ever receive and otherwise, the forum performs just fine.

    Database error in vBulletin 4.2.3:

    Invalid SQL:

    SELECT languageid,
    phrasegroup_global AS phrasegroup_global,
    phrasegroupinfo AS lang_phrasegroupinfo,
    options AS lang_options,
    languagecode AS lang_code,
    charset AS lang_charset,
    locale AS lang_locale,
    imagesoverride AS lang_imagesoverride,
    dateoverride AS lang_dateoverride,
    timeoverride AS lang_timeoverride,
    registereddateoverride AS lang_registereddateoverride,
    calformat1override AS lang_calformat1override,
    calformat2override AS lang_calformat2override,
    logdateoverride AS lang_logdateoverride,
    decimalsep AS lang_decimalsep,
    thousandsep AS lang_thousandsep
    FROM diylanguage
    WHERE languageid = 1;
  • Wayne Luke
    vBulletin Technical Support Lead
    • Aug 2000
    • 73981

    #2
    As stated, you need to repair the table. Since this is the language table, you probably cannot access the AdminCP. You can attempt to repair it using phpMyAdmin, or similar tool, if your hosting provider makes this available to you. If you can't repair it through a tool like that, your hosting provider will have to repair it for you.
    Translations provided by Google.

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

    Comment

    • dirknerkle
      Member
      • May 2013
      • 33
      • 5.6.3

      #3
      I continually get this error message as well. I have tried repairing the file via the AdminCP and that always displays "OK" afterward. I have also tried it using phpMyAdmin via my web site's control panel, and that always goes through fine as well. In fact, I've tried repairing ALL the tables in the database and they all come out OK as well. But the problem persists. I'm thinking that it's likely a compatibility issue or something with either PHP or MySQL, or the vbulletin code is just not right. I'm using the most recent version of 4.2.3

      Comment

      • Mark.B
        vBulletin Support
        • Feb 2004
        • 24286
        • 6.0.X

        #4
        There is no problem with the code. If there was, we'd have hundreds, if not thousands of customers reporting it.

        If the tabel is constantly crashing, you should ask your host to look into it.
        MARK.B
        vBulletin Support
        ------------
        My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
        My Unofficial vBulletin Cloud Demo: https://www.adminammo.com

        Comment

        • Paul M
          Former Lead Developer
          vB.Com & vB.Org
          • Sep 2004
          • 9886

          #5
          Continually getting what error message exactly ?

          Baby, I was born this way

          Comment

          • dirknerkle
            Member
            • May 2013
            • 33
            • 5.6.3

            #6
            Exactly the same as post # 1 above:
            Database error in vBulletin 4.2.3:

            Error # 1195

            Invalid SQL:

            SELECT languageid,
            phrasegroup_global AS phrasegroup_global,
            phrasegroupinfo AS lang_phrasegroupinfo,
            options AS lang_options,
            languagecode AS lang_code,
            charset AS lang_charset,
            locale AS lang_locale,
            imagesoverride AS lang_imagesoverride,
            dateoverride AS lang_dateoverride,
            timeoverride AS lang_timeoverride,
            registereddateoverride AS lang_registereddateoverride,
            calformat1override AS lang_calformat1override,
            calformat2override AS lang_calformat2override,
            logdateoverride AS lang_logdateoverride,
            decimalsep AS lang_decimalsep,
            thousandsep AS lang_thousandsep
            FROM diylanguage
            WHERE languageid = 1;



            What I've tried to alleviate the issue:
            I have repaired the table via the AdminCP -- it always reports OK. I have tried it several times in succession.
            I have repaired the table with phpMyAdmin -- several times -- and it always reports that it was successful.
            I have never been unable to repair and/or optimize the language table (my tables have a DIY table prefix)
            I have tried taking the forum offline so that nobody was using it and then using the repair/optimize tools, to no different effect.
            Sometimes I get error # 1194, sometimes error 1195 but the text is always the same and the same table is the issue.

            This is the ONLY database error I encounter -- I do not recall ever getting different db errors, and the log files do not indicate any other error occurs.
            The problem typically happens every few days and seems to occur more often when there are 400+ users logged in but it has also happened when only a couple dozen are logged in. The user number that might be attached to the error message changes, too -- it's not a single user number which might indicate a corruption in another table.

            The tech people at the host have studied the server logs and they report they are not seeing any issues.

            I wondered about the program code and while it may be fine in general, the last update of 4.2.3 may have developed a corruption during the update. Of course, if this was a common problem you'd have a great many reports on it.

            More information:
            PHP version 5.5.33
            MySQL version 5.6.25
            Apache server
            Linux OS
            Last edited by dirknerkle; Mon 6 Jun '16, 6:43pm.

            Comment

            • Wayne Luke
              vBulletin Technical Support Lead
              • Aug 2000
              • 73981

              #7
              With Error 1195, your table cannot be repaired using the AdminCP. Contact your hosting provider and have them repair the table from the command line with more advanced tools.
              Translations provided by Google.

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

              Comment

              • Paul M
                Former Lead Developer
                vB.Com & vB.Org
                • Sep 2004
                • 9886

                #8
                Originally posted by dirknerkle
                Exactly the same as post # 1 above:

                The tech people at the host have studied the server logs and they report they are not seeing any issues.
                I'd start looking for another host, they dont seem to have much of a clue, those crashes should be recorded in the mysql error log.

                Baby, I was born this way

                Comment

                • dirknerkle
                  Member
                  • May 2013
                  • 33
                  • 5.6.3

                  #9
                  I discovered the source of the problem. The issue apparently was an overloaded MySQL server and the problem was being masked by an internal server error of the web site. Apparently the query requests were taking too long, which caused a chain of events to occur, the last of which was this vb error. The host suggested that they move the site to a different MySQL server, which they did, and not only has the performance of the site gone up by about 1000%, this issue has gone away as well.

                  Thanks to all who responded.

                  Comment

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