[MDEV-25963] MariaDB crashed without apparent reason Created: 2021-06-18  Updated: 2021-06-20

Status: Open
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.3.27
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Stefano T. Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Environment:

Linux Debain 10.9 with Plesk Obsidian. Virtualized hardware.


Issue Links:
Relates
relates to MDEV-24489 Server crashes: double free or corrup... Closed

 Description   

MariaDB server crashed without any apparent reason.

In MariaDB errorlog there is:

double free or corruption (!prev)
210618 11:20:31 [ERROR] 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.
 
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.27-MariaDB-0+deb10u1-log
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=44
max_threads=152
thread_count=50
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 465226 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7f3428000c08
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 = 0x7f34b2a7edd8 thread_stack 0x49000

The DB server became unresponsive, but in init.d mariadb process status was OK.


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