The Server crashes immediately after start

Description

Log entries

2020-02-03T18:06:00.667048Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.18-9) starting as process 3980
18:06:18 UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
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 0x46000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x3d) [0x1f76f5d]
/usr/sbin/mysqld(handle_fatal_signal+0x351) [0x11957f1]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390) [0x7f55e4841390]
/usr/sbin/mysqld(page_cur_insert_rec_low(unsigned char*, dict_index_t*, unsigned char const*, unsigned long*, mtr_t*)+0x36a) [0x213d93a]
/usr/sbin/mysqld(page_cur_parse_insert_rec(unsigned long, unsigned char const*, unsigned char const*, buf_block_t*, dict_index_t*, mtr_t*)+0x8a0) [0x21401f0]
/usr/sbin/mysqld() [0x21067c6]
/usr/sbin/mysqld(recv_recover_page_func(bool, buf_block_t*)+0xd64) [0x2108874]
/usr/sbin/mysqld(buf_page_io_complete(buf_page_t*, bool)+0x7b7) [0x22dc357]
/usr/sbin/mysqld(fil_aio_wait(unsigned long)+0x1e1) [0x23b7691]
/usr/sbin/mysqld() [0x2202188]
/usr/sbin/mysqld(std::thread::_Impl<std::_Bind_simple<Runnable (void :yellow_star:(unsigned long), unsigned long)> >::_M_run()+0xcb) [0x2201cab]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xb8c80) [0x7f55e3232c80]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba) [0x7f55e48376ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f55e299841d]

Environment

OS: Ubuntu 16.04.6 LTS
CPU: Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
Memory: 64GB

No SSD plan old hard disk

Smart Checklist

Activity

Show:

Jira Bot March 29, 2020 at 4:15 PM

Hello ,
It's been 54 days since this issue went into Incomplete and we haven't heard
from you on this.

At this point, our policy is to Close this issue, to keep things from getting
too cluttered. If you have more information about this issue and wish to
reopen it, please reply with a comment containing "jira-bot=reopen".

Jira Bot March 19, 2020 at 9:55 AM

Hello ,
It's jira-bot again. Your bug report is important to us, but we haven't heard
from you since the previous notification. If we don't hear from you on
this in 7 days, the issue will be automatically closed.

Jira Bot March 4, 2020 at 8:56 AM

Hello ,
I'm jira-bot, Percona's automated helper script. Your bug report is important
to us but we've been unable to reproduce it, and asked you for more
information. If we haven't heard from you on this in 3 more weeks, the issue
will be automatically closed.

Lalit Choudhary February 4, 2020 at 8:21 AM

Hi

Thank you for the report.

I could not find similar crash report reported already.

Help us with a few more info to verify this issue.

  • provide few more lines of entries from error log before and after the crash.

  • my.cnf

  • Do you have reproducible test case/ steps ?

  • is it a one-time crash or do you see every time when you start mysql server?

  • are you restoring a backup and starting mysql?

 

Incomplete

Details

Assignee

Reporter

Affects versions

Priority

Smart Checklist

Created February 3, 2020 at 6:12 PM
Updated March 6, 2024 at 11:21 AM
Resolved March 29, 2020 at 4:15 PM

Flag notifications