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.

MySQL has crashed

Discussion in 'Database Discussions' started by dudanger, Oct 2, 2017.

  1. dudanger

    dudanger Member

    Joined:
    Oct 10, 2016
    Messages:
    12
    Likes Received:
    4
    Trophy Points:
    3
    Location:
    Japan
    cPanel Access Level:
    Root Administrator
    hello,guy!
    After the server restart,mysql was crash,pls help me with it
    and i reinstall the mysql get the same error.
    cpanel version 11.64.0.36

    the error log:
    Code:
    2017-10-02 06:33:06 30685 [Note] Plugin 'FEDERATED' is disabled.
    2017-10-02 06:33:06 30685 [Note] InnoDB: Using atomics to ref count buffer pool pages
    2017-10-02 06:33:06 30685 [Note] InnoDB: The InnoDB memory heap is disabled
    2017-10-02 06:33:06 30685 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    2017-10-02 06:33:06 30685 [Note] InnoDB: Memory barrier is not used
    2017-10-02 06:33:06 30685 [Note] InnoDB: Compressed tables use zlib 1.2.3
    2017-10-02 06:33:06 30685 [Note] InnoDB: Using Linux native AIO
    2017-10-02 06:33:06 30685 [Note] InnoDB: Not using CPU crc32 instructions
    2017-10-02 06:33:06 30685 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    2017-10-02 06:33:06 30685 [Note] InnoDB: Completed initialization of buffer pool
    2017-10-02 06:33:06 30685 [Note] InnoDB: Highest supported file format is Barracuda.
    2017-10-02 06:33:06 30685 [Note] InnoDB: Log scan progressed past the checkpoint lsn 667377830
    2017-10-02 06:33:06 30685 [Note] InnoDB: Database was not shutdown normally!
    2017-10-02 06:33:06 30685 [Note] InnoDB: Starting crash recovery.
    2017-10-02 06:33:06 30685 [Note] InnoDB: Reading tablespace information from the .ibd files...
    2017-10-02 06:33:06 30685 [Note] InnoDB: Restoring possible half-written data pages
    2017-10-02 06:33:06 30685 [Note] InnoDB: from the doublewrite buffer...
    InnoDB: Doing recovery: scanned up to log sequence number 667388109
    2017-10-02 06:33:06 30685 [Note] InnoDB: Starting an apply batch of log records to the database...
    InnoDB: Progress in percent: 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 10:33:06 UTC - 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=8388608
    read_buffer_size=131072
    max_used_connections=0
    max_threads=151
    thread_count=0
    connection_count=0
    It is possible that mysqld could use up to
    key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68108 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
    87 /usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8d54f5]
    /usr/sbin/mysqld(handle_fatal_signal+0x494)[0x6641e4]
    /lib64/libpthread.so.0(+0xf7e0)[0x7f4ee721e7e0]
    88 89 90 /usr/sbin/mysqld[0x9c5dff]
    91 92 /usr/sbin/mysqld[0x9c7a36]
    93 94 95 96 /usr/sbin/mysqld[0x9b075e]
    97 98 99 /usr/sbin/mysqld[0x9b23f4]
    /usr/sbin/mysqld[0xa7dd5d]
    /usr/sbin/mysqld[0xabf9a0]
    /usr/sbin/mysqld[0xa2a3d8]
    /lib64/libpthread.so.0(+0x7aa1)[0x7f4ee7216aa1]
    /lib64/libc.so.6(clone+0x6d)[0x7f4ee5f7fbcd]
    The manual page at MySQL :: MySQL 5.7 Reference Manual :: B.5.3.3 What to Do If MySQL Keeps Crashing contains
    information that should help you find out what is causing the crash.
    
     
    #1 dudanger, Oct 2, 2017
    Last edited by a moderator: Oct 2, 2017
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    38,658
    Likes Received:
    1,425
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
Loading...

Share This Page