Announcement

Collapse
No announcement yet.

'Indexqueue' database error whenever a search is performed.

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

  • [Forum] 'Indexqueue' database error whenever a search is performed.

    About a month ago, a hacker tore around in the server our site is on. He exploited a hole in the version of Linux we run and replaced all of the index files on all sites on the server with his mugshot. He was stopped and we always have off site backups, so the server was restored in a few hours.

    ...Almost...

    Ever since this happened we get a db error whenever someone performs a search. The actual search works as it should and we are seeing no results excluded or anything else awry other than the search numbering--the sequential numbering started over at '1'. And it throws a database error ever time someone performs a search.

    Anyone have any ideas or suggestions? I'm thinking the 'indexqueue' table is corrupt (it does have the word 'index' in it), but I have no idea how to repair it. Thanks!

    Here's a copy of the error:

    Database error in vBulletin 4.0.7:

    Invalid SQL:
    SELECT indexqueue.* FROM indexqueue AS indexqueue ORDER BY queueid;

    MySQL Error : Incorrect file format 'indexqueue'
    Error Number : 130
    Request Date : Wednesday, October 6th 2010 @ 07:34:24 AM
    Error Date : Wednesday, October 6th 2010 @ 07:34:25 AM
    Script : http://site.com/cron.php?rand=1286368460
    Referrer : http://site.com/forums/news/sub-forum/thread/
    IP Address : 111.111.111.111
    Username : Unregistered
    Classname : vB_Database_MySQLi
    MySQL Version :

  • #2
    To fix this 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.

    If that doesn't work then this may be too damaged to fix with the normal methods. Please check out this thread for other ways to repair a db, particularly items #2 and 3:

    http://www.vbulletin.com/forum/showt...threadid=44909

    You may have to ask your host to try and repair this for you.
    Steve Machol, former vBulletin Customer Support Manager (and NOT retired!)
    Change CKEditor Colors to Match Style (for 4.1.4 and above)

    Steve Machol Photography


    Mankind is the only creature smart enough to know its own history, and dumb enough to ignore it.


    Comment


    • #3
      I should have added that I tried using the built-in repair function and this is what I get:

      Click image for larger version

Name:	maint_error.JPG
Views:	1
Size:	39.8 KB
ID:	3680222

      I am not opposed to manually editing the table in phpMyAdmin, but I don't know its structure, can you tell me what it is?

      The host said he would take care of it a month ago...looking for new host now.

      Comment


      • #4
        You can't fix the structure without removing and recreating that table. If you want to do that, first drop that table, then run this query:

        CREATE indexqueue (
        queueid INTEGER UNSIGNED NOT NULL AUTO_INCREMENT,
        contenttype VARCHAR(45) NOT NULL,
        newid INTEGER UNSIGNED NOT NULL,
        id2 INTEGER UNSIGNED NOT NULL,
        package VARCHAR(64) NOT NULL,
        operation VARCHAR(64) NOT NULL,
        data TEXT NOT NULL,
        PRIMARY KEY (queueid)
        );
        Steve Machol, former vBulletin Customer Support Manager (and NOT retired!)
        Change CKEditor Colors to Match Style (for 4.1.4 and above)

        Steve Machol Photography


        Mankind is the only creature smart enough to know its own history, and dumb enough to ignore it.


        Comment


        • #5
          Perfect. Thanks.

          Comment


          • #6
            Originally posted by Steve Machol View Post
            You can't fix the structure without removing and recreating that table. If you want to do that, first drop that table, then run this query:

            CREATE indexqueue (
            queueid INTEGER UNSIGNED NOT NULL AUTO_INCREMENT,
            contenttype VARCHAR(45) NOT NULL,
            newid INTEGER UNSIGNED NOT NULL,
            id2 INTEGER UNSIGNED NOT NULL,
            package VARCHAR(64) NOT NULL,
            operation VARCHAR(64) NOT NULL,
            data TEXT NOT NULL,
            PRIMARY KEY (queueid)
            );

            I have been facing a similar problem after a recent server hack attempt. I tried the above method you recommended but it returned an error upon executing the query.

            Error Message: #1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'indexqueue ( queueid INTEGER UNSIGNED NOT NULL AUTO_INCREMENT, contenttype VAR' at line 1

            We currently have MySQL version 5.0.91 installed on the server.

            Any idea what could be causing this error and how it can be fixed?
            Webmaster Forum - Webmaster Marketplace

            Comment


            • #7
              For future reference, you should start your own thread with all the relevant details.

              Try this:

              CREATE TABLE indexqueue(queueid INTEGER UNSIGNED NOT NULL AUTO_INCREMENT ,
              contenttype VARCHAR( 45 ) NOT NULL ,
              newid INTEGER UNSIGNED NOT NULL ,
              id2 INTEGER UNSIGNED NOT NULL ,
              package VARCHAR( 64 ) NOT NULL ,
              operation VARCHAR( 64 ) NOT NULL ,
              DATA TEXT NOT NULL ,
              PRIMARY KEY ( queueid )
              );


              I ran that successfully on a test database.
              Steve Machol, former vBulletin Customer Support Manager (and NOT retired!)
              Change CKEditor Colors to Match Style (for 4.1.4 and above)

              Steve Machol Photography


              Mankind is the only creature smart enough to know its own history, and dumb enough to ignore it.


              Comment


              • #8
                Originally posted by Steve Machol View Post
                For future reference, you should start your own thread with all the relevant details.

                Try this:

                CREATE TABLE indexqueue(queueid INTEGER UNSIGNED NOT NULL AUTO_INCREMENT ,
                contenttype VARCHAR( 45 ) NOT NULL ,
                newid INTEGER UNSIGNED NOT NULL ,
                id2 INTEGER UNSIGNED NOT NULL ,
                package VARCHAR( 64 ) NOT NULL ,
                operation VARCHAR( 64 ) NOT NULL ,
                DATA TEXT NOT NULL ,
                PRIMARY KEY ( queueid )
                );


                I ran that successfully on a test database.

                Sure, will keep that in mind.

                I tried the query again and it worked it fine now.

                Thanks.
                Webmaster Forum - Webmaster Marketplace

                Comment

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