[MDEV-26162] Server crash at startup following forced termination of server. Created: 2021-07-16  Updated: 2023-04-27

Status: Open
Project: MariaDB Server
Component/s: Server, Storage Engine - Aria
Affects Version/s: 10.3.13
Fix Version/s: 10.4, 10.5, 10.6

Type: Bug Priority: Major
Reporter: David Crimmins Assignee: Michael Widenius
Resolution: Unresolved Votes: 0
Labels: None
Environment:

Linux 64bit



 Description   

After terminating mysqld process with kill -9 <pid>, mysqld crashes on restart.

Extract from error log:

2021-07-16  5:35:13 0 [Note] mysqld: Aria engine: starting recovery
recovered pages: 0% 3712763670% 0%210716  5:35:13 [ERROR] 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.
 
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
 
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.
 
Server version: 10.3.18-MariaDB-log
key_buffer_size=3221225472
read_buffer_size=131072
max_used_connections=0
max_threads=402
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4029508 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 = 0x0 thread_stack 0x49000
/entuity/database/bin/mysqld(my_print_stacktrace+0x2b)[0x7faf6dd569ab]
/entuity/database/bin/mysqld(handle_fatal_signal+0x4b7)[0x7faf6d7f7657]
sigaction.c:0(__restore_rt)[0x7faf6cbf77e0]
/entuity/database/bin/mysqld(+0xc0e5b6)[0x7faf6dc365b6]
maria/ma_recovery.c:2164(exec_REDO_LOGREC_CLR_END)[0x7faf6dc3702d]
maria/ma_recovery.c:350(maria_apply_log)[0x7faf6dc3b954]
maria/ma_recovery.c:242(maria_recovery_from_log)[0x7faf6dc3c3be]
maria/ha_maria.cc:3547(ha_maria_init)[0x7faf6dc1539d]
sql/handler.cc:549(ha_initialize_handlerton(st_plugin_int*))[0x7faf6d7fa0a8]
sql/sql_plugin.cc:1433(plugin_initialize)[0x7faf6d646901]
sql/sql_plugin.cc:1715(plugin_init(int*, char**, int))[0x7faf6d6478aa]
sql/mysqld.cc:5424(init_server_components)[0x7faf6d583ed9]
sql/mysqld.cc:6031(mysqld_main(int, char**))[0x7faf6d587753]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x7faf6baa4d1d]
/entuity/database/bin/mysqld(+0x5542e9)[0x7faf6d57c2e9]
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.
Writing a core file...
Working directory at /entuity/database/data
Resource Limits:
Limit                     Soft Limit           Hard Limit           Units
Max cpu time              unlimited            unlimited            seconds
Max file size             unlimited            unlimited            bytes
Max data size             unlimited            unlimited            bytes
Max stack size            8388608              unlimited            bytes
Max core file size        unlimited            unlimited            bytes
Max resident set          unlimited            unlimited            bytes
Max processes             190628               190628               processes
Max open files            6581                 6581                 files
Max locked memory         65536                65536                bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       190628               190628               signals
Max msgqueue size         819200               819200               bytes
Max nice priority         0                    0
Max realtime priority     0                    0
Max realtime timeout      unlimited            unlimited            us
Core pattern: core



 Comments   
Comment by Sergei Golubchik [ 2021-07-29 ]

Do you still have this datadir that causes it? If yes — please, make a copy of it.

Do you think you'll be able to share it with us, if we ask?

Generated at Thu Feb 08 09:43:12 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.