Package: mariadb-server-core-10.3
Version: 1:10.3.15-1
Severity: critical
Justification: causes serious data loss

-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mariadb-server-core-10.3 depends on:
ii  libaio1         0.3.112-3
ii  libc6           2.28-10
ii  libgnutls30     3.6.7-4
ii  liblz4-1        1.8.3-1
ii  libpcre3        2:8.39-12
ii  libsnappy1v5    1.1.7-1
ii  libstdc++6      8.3.0-6
ii  libsystemd0     241-5
ii  mariadb-common  1:10.3.15-1
ii  zlib1g          1:1.2.11.dfsg-1

mariadb-server-core-10.3 recommends no packages.

mariadb-server-core-10.3 suggests no packages.

-- no debconf information

How to trigger the issue:
 * install mariadb-server
 * start 'mysql' in a terminal
 * enter 'user information_schema'

The process mysqld will segfault, thus terminating all existing processes 
within the server.
It writes the following to the error log (e.g. /var/lib/mysql/error.log:

190710 16:45:48 [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

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.15-MariaDB-1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467420 K  
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x55b4ef5ef738
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 = 0x7f2beceeadd8 thread_stack 0x49000

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x55b4ef5fd1f0):
Connection ID (thread ID): 36

Optimizer switch: 

The manual page at 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             15580                15580                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       15580                15580                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

Systemd then automatically restarts mysqld so that operation continues, but at 
point data loss might have occurred already.

Reply via email to