Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

innodb crashed...!

Discussion in 'Database Discussions' started by remshad, Mar 24, 2014.

  1. remshad

    remshad Member

    Feb 13, 2011
    Likes Received:
    Trophy Points:
    hi ,
    i cant start mysql .

    it gives an error "ERROR! The server quit without updating PID file (/var/lib/mysql/server1.*******.pid)."

    while i sneak through .err file i seen below message

     h 4       d 0       ` ,       \ (       X $       T         P         L       | H       x D       t @       p <       l 8       h 4       d 0       ` ,       \ (       X $       T         P         L       | H       x D       t @       c   +< ,T;
    InnoDB: End of page dump
    2014-03-24 10:49:16 7fd5fd16f700 InnoDB: uncompressed page, stored checksum in field1 335704524, calculated checksums for field1: crc32 57077953, innodb 1497864469, none 3735928559, stored checksum in field2 43, calculated checksums for field2: crc32 57077953, innodb 4235337380, none 3735928559, page LSN 43 1007365204, low 4 bytes of LSN at page end 1007365204, page number (if stored to page already) 96680, space id (if created with >= MySQL-4.1.1 and stored already) 943
    InnoDB: Page may be an index page where index id is 2908
    InnoDB: (index "PRIMARY" of table "multidic_dictnory"."word_detail")
    InnoDB: Corruption of an index tree: table "multidic_dictnory"."word_detail", index "PRIMARY",
    InnoDB: father ptr page no 320672, child page no 320673
    PHYSICAL RECORD: n_fields 10; compact format; info bits 0
     0: len 4; hex 80f62af9; asc   * ;;
     1: len 6; hex 00006a57b0de; asc   jW  ;;
     2: len 7; hex de000001b60abc; asc        ;;
     3: len 5; hex 457373656e; asc Essen;;
     4: len 7; hex 656e676c697368; asc english;;
     5: len 8; hex 4a6170616e657365; asc Japanese;;
     6: len 7; hex 756e6b6e6f776e; asc unknown;;
     7: len 9; hex e9a39fe381b9e789a9; asc          ;;
     8: len 4; hex 80000000; asc     ;;
     9: len 4; hex 80000000; asc     ;;
     n_owned: 0; heap_no: 2; next rec: 201
    PHYSICAL RECORD: n_fields 2; compact format; info bits 0
     0: len 4; hex 80f62a27; asc   *';;
     1: len 4; hex 0004e4a0; asc     ;;
     n_owned: 0; heap_no: 982; next rec: 12878
    InnoDB: You should dump + drop + reimport the table to fix the
    InnoDB: corruption. If the crash happens at the database startup, see
    InnoDB: about
    InnoDB: forcing recovery. Then dump + drop + reimport.
    2014-03-24 10:49:16 7fd5fd16f700  InnoDB: Assertion failure in thread 140557050902272 in file line 1466
    InnoDB: We intentionally generate a memory trap.
    InnoDB: Submit a detailed bug report to
    InnoDB: If you get repeated assertion failures or crashes, even
    InnoDB: immediately after the mysqld startup, there may be
    InnoDB: corruption in the InnoDB tablespace. Please refer to
    InnoDB: about forcing recovery.
    15:49:16 UTC - mysqld got signal 6 ;
    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.
    It is possible that mysqld could use up to
    key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68242 K  bytes of memory
    Hope that's ok; if not, decrease some variables in the equation.
    Thread pointer: 0x0
    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 = 0 thread_stack 0x40000
    The manual page at contains
    information that should help you find out what is causing the crash.

    How i resolve this issue ?
  2. talk2prakash

    talk2prakash Member

    Sep 29, 2013
    Likes Received:
    Trophy Points:
    cPanel Access Level:
    Root Administrator
    What was the task performed with respect to your mysql server recently ?

    Did you move the mysql directory or innodb data files to the different location ?

    Seems like the only option you have now is to restore all the databases from the backup available.
  3. remshad

    remshad Member

    Feb 13, 2011
    Likes Received:
    Trophy Points:
    How do i restore crashed db ...'
    since mysql server is not running ....

    - - - Updated - - -

    recently i upgraded to mysql 5.6+ ... That was the last cause
  4. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Apr 11, 2011
    Likes Received:
    Trophy Points:
    cPanel Access Level:
    Root Administrator

Share This Page