URGENT: MySQL Error : Table './db_name/searchcore_text' is marked as crashed and last (automatic?) repair failed

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • aagcrc
    New Member
    • Jul 2018
    • 10
    • 4.2.x

    URGENT: MySQL Error : Table './db_name/searchcore_text' is marked as crashed and last (automatic?) repair failed

    Hi

    I just got this error:

    ----- MySQL Error : Table './db_name/searchcore_text' is marked as crashed and last (automatic?) repair failed

    So I start the repair feature under AdminCP -> Maintenance -> Repair/Optimize Tables, and being stuck for hours


    When someone tries to do something in the forum, I also get this error:

    ---- MySQL Error : Can't create/write to file '/tmp/MYgPUht5' (Errcode: 28)

    Disk space:
    root@svr2 [/]# df -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/md3 442G 45G 376G 11% /
    tmpfs 7.8G 0 7.8G 0% /dev/shm
    /dev/md0 477M 51M 401M 12% /boot
    /usr/tmpDSK 4.0G 3.8G 0 100% /tmp

    Temp folder gets full
    root@svr2 [/]# mysqld --verbose --help | grep tmp
    180731 7:55:27 [Note] mysqld (mysqld 5.5.52-cll) starting as process 25435 ...
    180731 7:55:27 [Note] Plugin 'FEDERATED' is disabled.
    --max-tmp-tables=# Maximum number of temporary tables a client can keep open
    --slave-load-tmpdir=name
    --tmp-table-size=# If an internal in-memory temporary table exceeds this
    -t, --tmpdir=name Path for temporary files. Several paths may be specified,
    max-tmp-tables 32
    slave-load-tmpdir /tmp
    tmp-table-size 268435456
    tmpdir /tmp

    I can change it to another folder with more space, basically to the root, but I need to restart the MySQL service, how bad or safe is it since its repairing the table, but maybe stuck since no space.
    root@svr2 [/]# lsof | egrep '^COMMAND|deleted'
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    init 1 root txt REG 9,3 150352 8781962 /sbin/init (deleted)
    dovecot 2604 root 123u REG 9,3 0 2884562 /var/run/dovecot/login-master-notifyfdacd91a720156dc (deleted)
    dovecot 2604 root 140u REG 9,3 0 2884570 /var/run/dovecot/login-master-notify609544a0c72c41dd (deleted)
    dovecot 2604 root 143u REG 9,3 0 2884624 /var/run/dovecot/login-master-notify19dd2fce8eb704c0 (deleted)
    pop3-logi 2615 dovenull 4u REG 9,3 0 2884562 /var/run/dovecot/login-master-notifyfdacd91a720156dc (deleted)
    imap-logi 2616 dovenull 4u REG 9,3 0 2884624 /var/run/dovecot/login-master-notify19dd2fce8eb704c0 (deleted)
    pop3-logi 2620 dovenull 4u REG 9,3 0 2884562 /var/run/dovecot/login-master-notifyfdacd91a720156dc (deleted)
    imap-logi 2621 dovenull 4u REG 9,3 0 2884624 /var/run/dovecot/login-master-notify19dd2fce8eb704c0 (deleted)
    httpd 2624 root 11w REG 9,3 0 10882019 /usr/local/apache/logs/ssl_mutex (deleted)
    httpd 4312 nobody 11w REG 9,3 0 10882019 /usr/local/apache/logs/ssl_mutex (deleted)
    httpd 8977 nobody 11w REG 9,3 0 10882019 /usr/local/apache/logs/ssl_mutex (deleted)
    httpd 8978 nobody 11w REG 9,3 0 10882019 /usr/local/apache/logs/ssl_mutex (deleted)
    httpd 8979 nobody 11w REG 9,3 0 10882019 /usr/local/apache/logs/ssl_mutex (deleted)
    httpd 13611 nobody 11w REG 9,3 0 10882019 /usr/local/apache/logs/ssl_mutex (deleted)
    httpd 13613 nobody 11w REG 9,3 0 10882019 /usr/local/apache/logs/ssl_mutex (deleted)
    httpd 15645 nobody 11w REG 9,3 0 10882019 /usr/local/apache/logs/ssl_mutex (deleted)
    httpd 18190 nobody 11w REG 9,3 0 10882019 /usr/local/apache/logs/ssl_mutex (deleted)
    httpd 18191 nobody 11w REG 9,3 0 10882019 /usr/local/apache/logs/ssl_mutex (deleted)
    mysqld 23070 mysql 4u REG 7,0 0 11 /tmp/ibcjJNBb (deleted)
    mysqld 23070 mysql 5u REG 7,0 0 12 /tmp/ibIk2E7h (deleted)
    mysqld 23070 mysql 6u REG 7,0 0 13 /tmp/ibOiDwDo (deleted)
    mysqld 23070 mysql 7u REG 7,0 0 14 /tmp/ib2FfjpC (deleted)
    mysqld 23070 mysql 11u REG 7,0 0 15 /tmp/ibjChTdK (deleted)
    mysqld 23070 mysql 1120u REG 7,0 2477435882 18 /tmp/STbrwhd8 (deleted)
    mysqld 23070 mysql 1122u REG 7,0 19529728 19 /tmp/STeqT6pV (deleted)
    mysqld 23070 mysql 1128u REG 7,0 1369624576 20 /tmp/STVMcfDS (deleted)

    httpd 23976 nobody 11w REG 9,3 0 10882019 /usr/local/apache/logs/ssl_mutex (deleted)
    root@svr2 [/]#

    Those temp files are using all the space

    NEEDING some help urgent

    Thank you
  • K a M a L
    Senior Member
    • Dec 2009
    • 118

    #2
    It is not a big problem if you couldn't recover this table .. you can recreate it with query
    Code:
    CREATE TABLE `searchcore_text` (
      `searchcoreid` int(10) UNSIGNED NOT NULL,
      `keywordtext` mediumtext ,
      `title` varchar(254) NOT NULL DEFAULT ''
    )
    And Then rebuild Search index in admincp

    Comment

    • djbaxter
      Senior Member
      • Aug 2006
      • 1418
      • 4.2.5

      #3
      Originally posted by K a M a L
      It is not a big problem if you couldn't recover this table .. you can recreate it with query
      Code:
      CREATE TABLE `searchcore_text` (
      `searchcoreid` int(10) UNSIGNED NOT NULL,
      `keywordtext` mediumtext ,
      `title` varchar(254) NOT NULL DEFAULT ''
      )
      And Then rebuild Search index in admincp
      That sounds like bad advice to me.
      Psychlinks Web Services Affordable Web Design & Site Management
      Specializing in Small Businesses and vBulletin/Xenforo Forums

      Comment

      • djbaxter
        Senior Member
        • Aug 2006
        • 1418
        • 4.2.5

        #4
        Originally posted by aagcrc
        I just got this error:

        ----- MySQL Error : Table './db_name/searchcore_text' is marked as crashed and last (automatic?) repair failed

        So I start the repair feature under AdminCP -> Maintenance -> Repair/Optimize Tables, and being stuck for hours
        Log in to your cPanel and use phpMyAdmin to repair the table.


        Originally posted by aagcrc
        When someone tries to do something in the forum, I also get this error:

        ---- MySQL Error : Can't create/write to file '/tmp/MYgPUht5' (Errcode: 28)

        Disk space:
        root@svr2 [/]# df -h
        Filesystem Size Used Avail Use% Mounted on
        /dev/md3 442G 45G 376G 11% /
        tmpfs 7.8G 0 7.8G 0% /dev/shm
        /dev/md0 477M 51M 401M 12% /boot
        /usr/tmpDSK 4.0G 3.8G 0 100% /tmp

        Temp folder gets full
        root@svr2 [/]# mysqld --verbose --help | grep tmp
        180731 7:55:27 [Note] mysqld (mysqld 5.5.52-cll) starting as process 25435 ...
        180731 7:55:27 [Note] Plugin 'FEDERATED' is disabled.
        --max-tmp-tables=# Maximum number of temporary tables a client can keep open
        --slave-load-tmpdir=name
        --tmp-table-size=# If an internal in-memory temporary table exceeds this
        -t, --tmpdir=name Path for temporary files. Several paths may be specified,
        max-tmp-tables 32
        slave-load-tmpdir /tmp
        tmp-table-size 268435456
        tmpdir /tmp
        Submit a support ticket to your host and get them to look into your server and database configuration.
        Psychlinks Web Services Affordable Web Design & Site Management
        Specializing in Small Businesses and vBulletin/Xenforo Forums

        Comment

        • K a M a L
          Senior Member
          • Dec 2009
          • 118

          #5
          Originally posted by djbaxter

          That sounds like bad advice to me.
          Okay

          Comment

          • aagcrc
            New Member
            • Jul 2018
            • 10
            • 4.2.x

            #6
            I have full control of the server with Root access
            The forums was working and it just stopped....
            How safe is to restart the mysql service to cancel and start the repair, would be safter via SSH Console?
            Thank you\

            Comment

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

              #7
              Stopping and starting the MySQL Service without proper shutdown is probably what caused the table to crash to begin with. You should never restart the server while queries are running on it.

              MySQL Error : Can't create/write to file '/tmp/MYgPUht5' (Errcode: 28)


              This is probably your main issue. You're out of disk space where your temporary partition is. MySQL will not be able to operate until you provide more disk space on this partition. This partition should be at least three times the size of your largest table. If you want to play it safe, you should allocate five times your largest table to this partition.

              You should repair your tables from the command line. You can find instructions on how to do this in the MySQL Manual.


              Since you're the "Server Administrator" you should familiarize yourself with all software running on your server so you can handle these minor issues.
              Translations provided by Google.

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

              Comment

              • aagcrc
                New Member
                • Jul 2018
                • 10
                • 4.2.x

                #8
                Thanks everyone, you gave me some light and I fixed the issue. Basically I moved the MySQL temp folder to the root for now, and re-run the repair and that fixed the table. I did repair it from PHPmyAdmin
                root@svr2 [~]# mysqld --verbose --help | grep tmp
                180731 16:52:36 [Note] mysqld (mysqld 5.5.52-cll) starting as process 15795 ...
                180731 16:52:37 [Note] Plugin 'FEDERATED' is disabled.
                --max-tmp-tables=# Maximum number of temporary tables a client can keep open
                --slave-load-tmpdir=name
                --tmp-table-size=# If an internal in-memory temporary table exceeds this
                -t, --tmpdir=name Path for temporary files. Several paths may be specified,
                max-tmp-tables 32
                slave-load-tmpdir /mysqltemp
                tmp-table-size 268435456
                tmpdir /mysqltemp

                root@svr2 [~]# df -h
                Filesystem Size Used Avail Use% Mounted on
                /dev/md3 442G 52G 369G 13% /
                tmpfs 7.8G 0 7.8G 0% /dev/shm
                /dev/md0 477M 51M 401M 12% /boot
                /usr/tmpDSK 4.0G 137M 3.7G 4% /tmp


                ANALYZE TABLE `searchcore_text`
                db_name.searchcore_text
                analyze status OK


                Thank you
                Last edited by aagcrc; Tue 31 Jul '18, 1:02pm.

                Comment

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