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 database died

Discussion in 'Database Discussions' started by z3d3m0n, Nov 18, 2017.

Tags:
  1. z3d3m0n

    z3d3m0n Member

    Joined:
    Feb 8, 2016
    Messages:
    19
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Prague
    cPanel Access Level:
    Root Administrator
    Hello Fellow cPanel gurus,

    today in the morning i found mysql crashed , could not bring it up to do a check , nor event into recovery mode:

    would appreciate any advices

    here is the full story
    Code:
    InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
    InnoDB: We intentionally generate a memory trap.
    InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
    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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    InnoDB: about forcing recovery.
    21:33:34 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.
    
    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...
    2017-11-18 16:33:34 22020 [Note] InnoDB: Waiting for purge to start
    stack_bottom = 0 thread_stack 0x40000
    /usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8d7265]
    /usr/sbin/mysqld(handle_fatal_signal+0x494)[0x664b84]
    /lib64/libpthread.so.0(+0xf7e0)[0x7f168f6ec7e0]
    /lib64/libc.so.6(gsignal+0x35)[0x7f168e397495]
    /lib64/libc.so.6(abort+0x175)[0x7f168e398c75]
    /usr/sbin/mysqld[0xad9c40]
    /usr/sbin/mysqld[0xa36b90]
    /usr/sbin/mysqld[0xa4ddf3]
    /usr/sbin/mysqld[0xa4a92f]
    /usr/sbin/mysqld[0xa4b7f9]
    /usr/sbin/mysqld[0xa41b0f]
    /usr/sbin/mysqld[0xa42119]
    /lib64/libpthread.so.0(+0x7aa1)[0x7f168f6e4aa1]
    /lib64/libc.so.6(clone+0x6d)[0x7f168e44dbcd]
    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.
    2017-11-18 16:38:36 23120 [Note] Plugin 'FEDERATED' is disabled.
    2017-11-18 16:38:36 23120 [Note] InnoDB: Using atomics to ref count buffer pool pages
    2017-11-18 16:38:36 23120 [Note] InnoDB: The InnoDB memory heap is disabled
    2017-11-18 16:38:36 23120 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    2017-11-18 16:38:36 23120 [Note] InnoDB: Memory barrier is not used
    2017-11-18 16:38:36 23120 [Note] InnoDB: Compressed tables use zlib 1.2.3
    2017-11-18 16:38:36 23120 [Note] InnoDB: Using Linux native AIO
    2017-11-18 16:38:36 23120 [Note] InnoDB: Using CPU crc32 instructions
    2017-11-18 16:38:36 23120 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    2017-11-18 16:38:36 23120 [Note] InnoDB: Completed initialization of buffer pool
    2017-11-18 16:38:36 23120 [Note] InnoDB: Highest supported file format is Barracuda.
    2017-11-18 16:38:36 23120 [Note] InnoDB: Log scan progressed past the checkpoint lsn 2057712760
    2017-11-18 16:38:36 23120 [Note] InnoDB: Database was not shutdown normally!
    2017-11-18 16:38:36 23120 [Note] InnoDB: Starting crash recovery.
    2017-11-18 16:38:36 23120 [Note] InnoDB: Reading tablespace information from the .ibd files...
    2017-11-18 16:38:36 23120 [Note] InnoDB: Restoring possible half-written data pages
    2017-11-18 16:38:36 23120 [Note] InnoDB: from the doublewrite buffer...
    InnoDB: Doing recovery: scanned up to log sequence number 2057717700
    InnoDB: 1 transaction(s) which must be rolled back or cleaned up
    InnoDB: in total 1 row operations to undo
    InnoDB: Trx id counter is 3571200
    2017-11-18 16:38:36 23120 [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 87 88 89 90 91 92 93 94 95 96 97 98 99
    InnoDB: Apply batch completed
    2017-11-18 16:38:36 23120 [Note] InnoDB: 128 rollback segment(s) are active.
    InnoDB: Starting in background the rollback of uncommitted transactions
    2017-11-18 16:38:36 7f90b01d1700  InnoDB: Rolling back trx with id 3570807, 1 rows to undo
    2017-11-18 16:38:36 23120 [Note] InnoDB: Waiting for purge to start
    2017-11-18 16:38:36 7f90b01d1700  InnoDB: Assertion failure in thread 140259406714624 in file fut0lst.ic line 83
    InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
    InnoDB: We intentionally generate a memory trap.
    InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
    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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    InnoDB: about forcing recovery.
    21:38:36 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.
    
    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
    /usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8d7265]
    /usr/sbin/mysqld(handle_fatal_signal+0x494)[0x664b84]
    /lib64/libpthread.so.0(+0xf7e0)[0x7f90c18b27e0]
    /lib64/libc.so.6(gsignal+0x35)[0x7f90c055d495]
    /lib64/libc.so.6(abort+0x175)[0x7f90c055ec75]
    /usr/sbin/mysqld[0xad9c40]
    /usr/sbin/mysqld[0xa36b90]
    /usr/sbin/mysqld[0xa4ddf3]
    /usr/sbin/mysqld[0xa4a92f]
    /usr/sbin/mysqld[0xa4b7f9]
    /usr/sbin/mysqld[0xa41b0f]
    /usr/sbin/mysqld[0xa42119]
    /lib64/libpthread.so.0(+0x7aa1)[0x7f90c18aaaa1]
    /lib64/libc.so.6(clone+0x6d)[0x7f90c0613bcd]
    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.
    2017-11-18 16:41:21 24005 [Note] Plugin 'FEDERATED' is disabled.
    2017-11-18 16:41:21 24005 [Note] InnoDB: Using atomics to ref count buffer pool pages
    2017-11-18 16:41:21 24005 [Note] InnoDB: The InnoDB memory heap is disabled
    2017-11-18 16:41:21 24005 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    2017-11-18 16:41:21 24005 [Note] InnoDB: Memory barrier is not used
    2017-11-18 16:41:21 24005 [Note] InnoDB: Compressed tables use zlib 1.2.3
    2017-11-18 16:41:21 24005 [Note] InnoDB: Using Linux native AIO
    2017-11-18 16:41:21 24005 [Note] InnoDB: Using CPU crc32 instructions
    2017-11-18 16:41:21 24005 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    2017-11-18 16:41:21 24005 [Note] InnoDB: Completed initialization of buffer pool
    2017-11-18 16:41:21 24005 [Note] InnoDB: Highest supported file format is Barracuda.
    2017-11-18 16:41:21 24005 [Note] InnoDB: Log scan progressed past the checkpoint lsn 2057712760
    2017-11-18 16:41:21 24005 [Note] InnoDB: Database was not shutdown normally!
    2017-11-18 16:41:21 24005 [Note] InnoDB: Starting crash recovery.
    2017-11-18 16:41:21 24005 [Note] InnoDB: Reading tablespace information from the .ibd files...
    2017-11-18 16:41:21 24005 [Note] InnoDB: Restoring possible half-written data pages
    2017-11-18 16:41:21 24005 [Note] InnoDB: from the doublewrite buffer...
    InnoDB: Doing recovery: scanned up to log sequence number 2057717700
    InnoDB: 1 transaction(s) which must be rolled back or cleaned up
    InnoDB: in total 1 row operations to undo
    InnoDB: Trx id counter is 3571200
    2017-11-18 16:41:21 24005 [Note] InnoDB: Starting an apply batch of log records to the database...
    InnoDB: Progress in percent: 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
    InnoDB: Apply batch completed
    2017-11-18 16:41:21 24005 [Note] InnoDB: 128 rollback segment(s) are active.
    InnoDB: Starting in background the rollback of uncommitted transactions
    2017-11-18 16:41:21 7fe192af7700  InnoDB: Rolling back trx with id 3570807, 1 rows to undo
    2017-11-18 16:41:21 24005 [Note] InnoDB: Waiting for purge to start
    2017-11-18 16:41:21 7fe192af7700  InnoDB: Assertion failure in thread 140606805341952 in file fut0lst.ic line 83
    InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
    InnoDB: We intentionally generate a memory trap.
    InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
    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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
    InnoDB: about forcing recovery.
    21:41:21 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.
    
    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
    /usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8d7265]
    /usr/sbin/mysqld(handle_fatal_signal+0x494)[0x664b84]
    /lib64/libpthread.so.0(+0xf7e0)[0x7fe1a2dd87e0]
    /lib64/libc.so.6(gsignal+0x35)[0x7fe1a1a83495]
    /lib64/libc.so.6(abort+0x175)[0x7fe1a1a84c75]
    /usr/sbin/mysqld[0xad9c40]
    /usr/sbin/mysqld[0xa36b90]
    /usr/sbin/mysqld[0xa4ddf3]
    /usr/sbin/mysqld[0xa4a92f]
    /usr/sbin/mysqld[0xa4b7f9]
    /usr/sbin/mysqld[0xa41b0f]
    /usr/sbin/mysqld[0xa42119]
    /lib64/libpthread.so.0(+0x7aa1)[0x7fe1a2dd0aa1]
    /lib64/libc.so.6(clone+0x6d)[0x7fe1a1b39bcd]
    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.
    
     
  2. rpvw

    rpvw Well-Known Member

    Joined:
    Jul 18, 2013
    Messages:
    618
    Likes Received:
    192
    Trophy Points:
    43
    Location:
    Spain
    cPanel Access Level:
    Root Administrator
  3. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    42,715
    Likes Received:
    1,705
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Hello,

    The link referenced on the previous post is a good place to start.

    Thank you.
     
Loading...

Share This Page