Announcement

Announcement Module
Collapse
No announcement yet.

about repair table archive engine????

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • about repair table archive engine????

    mysql> repair table api_access_log extended;
    ERROR 2006 (HY000): MySQL server has gone away
    No connection. Trying to reconnect...
    Connection id: 8
    Current database: test

    ERROR 2013 (HY000): Lost connection to MySQL server during query
    mysql>
    mysql> select version();
    ERROR 2006 (HY000): MySQL server has gone away
    No connection. Trying to reconnect...
    Connection id: 39
    Current database: test

    +------------+
    | version() |
    +------------+
    | 5.1.51-log |
    +------------+
    1 row in set (0.00 sec)


    Archive engine how to fix, ask everybody to help me !!!!!

  • #2
    Hi,

    There are couple of bugs, which are similar to this issue but I'm not sure if anyone exactly related to this.
    http://bugs.mysql.com/bug.php?id=47357
    http://bugs.mysql.com/bug.php?id=60976

    Can you please provide the full error log and test case or steps to reproduce this error? thanks.

    Comment


    • #3
      error log: 131219 5:00:29 - mysqld got signal 11 ;
      This could be because you hit a bug. It is also possible that this binary
      or one of the libraries it was linked against is corrupt, improperly built,
      or misconfigured. This error can also be caused by malfunctioning hardware.
      We will try our best to scrape up some info that will hopefully help diagnose
      the problem, but since we have already crashed, something is definitely wrong
      and this may fail.

      key_buffer_size=16777216
      read_buffer_size=131072
      max_used_connections=529
      max_threads=1600
      threads_connected=420
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 442471 K
      bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      thd: 0x7f85204b8fd0
      Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      stack_bottom = 0x7f8515f12e88 thread_stack 0x30000
      /usr/sbin/mysqld(my_print_stacktrace+0x29) [0x7f8577830829]
      /usr/sbin/mysqld(handle_segfault+0x404) [0x7f857753ab14]
      /lib/libpthread.so.0(+0xef60) [0x7f8576d9cf60]
      /lib/libc.so.6(+0x742c8) [0x7f85758822c8]
      /lib/libc.so.6(__libc_malloc+0x70) [0x7f8575884930]
      /usr/sbin/mysqld(my_malloc+0x32) [0x7f857781a722]
      /usr/sbin/mysqld(reset_root_defaults+0x68) [0x7f857781b058]
      /usr/sbin/mysqld(THD::init_for_queries()+0x4e) [0x7f8577525d8e]
      /usr/sbin/mysqld(handle_one_connection+0x1eb) [0x7f85775459db]
      /lib/libpthread.so.0(+0x68ba) [0x7f8576d948ba]
      /lib/libc.so.6(clone+0x6d) [0x7f85758dd02d]
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort...
      thd->query at (nil) is an invalid pointer
      thd->thread_id=10482
      thd->killed=NOT_KILLED
      The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
      information that should help you find out what is causing the crash.
      131219 5:00:44 [ERROR] Couldn't repair table: gfan_log.api_access_log

      Comment


      • #4
        -rw-rw---- 1 mysql mysql 6.1G 12月 19 15:22 api_access_log.ARN
        -rw-r--r-- 1 root root 2.0G 12月 19 14:02 api_access_log.ARZ
        -rw-r--r-- 1 root root 9.1K 12月 19 11:27 api_access_log.frm

        Comment


        • #5
          What happens if you fix both files permissions from root to mysql?

          Comment

          Working...
          X