[MDEV-25081] Mariadb 10.3.17 aria recovery crash ([ERROR] mysqld got signal 11 ) Created: 2021-03-08  Updated: 2021-05-26  Resolved: 2021-05-26

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - Aria
Affects Version/s: 10.3.17
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Gianpietro Germi Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: crash, need_feedback
Environment:

Embedded Linux - Debian Buster (arm)



 Description   

2021-03-05 10:40:28 0 [Note] mysqld: Aria engine: starting recovery
recovered pages: 0% 10%210305 10:40:28 [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.17-MariaDB-0+deb10u1
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466218 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
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 /var/lib/mysql
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        0                    unlimited            bytes
Max resident set          unlimited            unlimited            bytes
Max processes             7413                 7413                 processes
Max open files            16364                16364                files
Max locked memory         65536                65536                bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       7413                 7413                 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-04-28 ]

does it happen only on ARM? What if you copy the datadir and start MariaDB on x86_64?
Can you provide a copy of the datadir that cases this crash?

Comment by Gianpietro Germi [ 2021-04-28 ]

Thank you Sergei for your reply.

I have only ARM platform, I'm not able to reproduce same system on other platform (i.e. x86_64).

Unfortunately I don't have datadir that create this bug, I solved erasing aria log and losing some info and old datadir.
If this problem will come back, I'll save datadir and I'll share it with you, unfortunately is not reproducible.

Comment by Sergei Golubchik [ 2021-04-28 ]

Okay, thanks. This bug report will stay open for a month and then we'll close it as "Incomplete". But feel free to add new info any time, we can reopen it if you do.

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