Announcement

Collapse
No announcement yet.

Continue Getting Database Error

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

  • [Forum] Continue Getting Database Error

    I get this email everyone once in awhile:

    Database error in vBulletin 4.2.0:

    Invalid SQL:
    SHOW COLUMNS FROM user LIKE 'username';


    MySQL Error : Incorrect key file for table '/mysql-tmp/#sql_3dfb_0.MYI'; try to repair it
    Error Number : 126
    Request Date : Wednesday, December 26th 2012 @ 12:44:29 PM
    Error Date : Wednesday, December 26th 2012 @ 12:44:29 PM
    Script : register.php?do=addmember
    Referrer : register.php
    IP Address : XXX.XXX.XXX.XXX
    Username : xxxxxxxxxxxx
    Classname : vB_Database
    MySQL Version :
    I have already talked to my host and they insist this has to do with vBulletin. I'm starting to think it is an addon but cannot recreate with addons enabled. So I'm at a loss here.

  • #2
    temporarily disable all plugins.
    Note: To temporarily disable the plugin system, edit includes/config.php and add this line right under <?php:
    PHP Code:
    define('DISABLE_HOOKS'true); 
    Then run Repair/Optimize in the Admin CP. You may need to run it more than once to fix all errors:

    Admin CP -> Maintenance -> Repair/Optimize Tables -> Check All -> Continue

    If you cannot access the Admin CP you can also use phpMyAdmin to repair tables

    Former vBulletin Support Staff
    Need Help?, Or P.M. Me

    Comment


    • #3
      Ok did that, now what?

      Comment


      • #4
        If all tables now has Status: OK , the problem solved.
        Also check your Installed plugins if someone not compatible with vBulletin version.

        Former vBulletin Support Staff
        Need Help?, Or P.M. Me

        Comment


        • #5
          Run a repair of your db tables. If that won''t fix the error then contact your host and tell them about the error.

          Comment


          • #6
            borbole, as stated in my OP, I have done that already, just did it again, and in my OP I already contacted my host as I read a thread on here that stated to do that. They said it is coming from vBulletin. So I'm not sure now.

            Comment


            • #7
              Is the issue still there with all of your plugins disabled?
              Former vBulletin user

              Comment


              • #8
                I have plugins enabled and it seems to be fine for now but I'm sure it will happen again.

                Comment


                • #9
                  I think there is still some remnants of a plugin causing the issue. I'm going to disable the plugins and leave them disabled until this is all resolved. I disabled plugins through the admin panel instead of the config file to see if it happened that way.
                  Last edited by Mythotical; Tue 1st Jan '13, 1:20pm.

                  Comment


                  • #10
                    Originally posted by Mythotical View Post
                    I think there is still some remnants of a plugin causing the issue. I'm going to disable the plugins and leave them disabled until this is all resolved. I disabled plugins through the admin panel instead of the config file to see if it happened that way.
                    Enable them one at a time until you see the issue to find the culprit.
                    Former vBulletin user

                    Comment


                    • #11
                      The problem with that is the error does not occur immediately. Guess I can disable all mods and go one by one and wait a week to activate the next.

                      - - - Updated - - -

                      I had all registration mods disabled when the last error came in which was a few hours ago. So I'm not sure about it being a mod, I honestly think there is an issue either with my /tmp/ directory or the MySQL system not being properly installed.

                      Comment


                      • #12
                        I don't believe that this error is caused by vBulletin or a modification but chances are, that if you're seeing this error, you've run out of space in /tmp or wherever tmpdir points to. If only for the time it takes MySQL to create a temporary file (filling the parition) and delete it in disgust. The next step would be to contact your hoster about this and tell them to solve it.
                        No private support, only PM me when I ask for it. Support in the forums only.

                        Comment

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