RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1721237 - Mariadb server crashes
Summary: Mariadb server crashes
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: mariadb
Version: 8.0
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Michal Schorm
QA Contact: Lukáš Zachar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-17 16:20 UTC by Mikko Hirvonen
Modified: 2021-02-01 07:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-01 07:41:31 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Mikko Hirvonen 2019-06-17 16:20:43 UTC 
Description of problem:

mariadb 10.3 crashes.

Version-Release number of selected component (if applicable):

10.3.11
Release     : 2.module+el8+2885+7b8bb354

How reproducible:


Steps to Reproduce:
1. Install large wordpress multiuser database 
2. run wp-cli search-replace 
3. server crashes

Actual results:
$ time ~/bin/wp --url=https://blogs-test.it.helsinki.fi search-replace 'blogs-test.it.helsinki.fi' 'rhel8-test.it.helsinki.fi' --recurse-objects --skip-columns=guid --skip-tables=wp_users --network
PHP Notice:  Constant ABSPATH already defined in phar:///home/masse/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1169) : eval()'d code on line 57
PHP Warning:  mysqli_query(): MySQL server has gone away in /home/masse/blogs.helsinki.fi/wp-includes/wp-db.php on line 2007
Warning: mysqli_query(): MySQL server has gone away in /home/masse/blogs.helsinki.fi/wp-includes/wp-db.php on line 2007
PHP Warning:  mysqli_query(): Error reading result set's header in /home/masse/blogs.helsinki.fi/wp-includes/wp-db.php on line 2007
Warning: mysqli_query(): Error reading result set's header in /home/masse/blogs.helsinki.fi/wp-includes/wp-db.php on line 2007
Error: Error establishing a database connection.

real	0m24.121s
user	0m9.981s
sys	0m4.692s

cat /var/log/mariadb.log:
190617 18:33:10 [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.11-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=2
max_threads=153
thread_count=8
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467389 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f1c44000f78
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 = 0x7f1c82c27c88 thread_stack 0x49000
/usr/libexec/mysqld(my_print_stacktrace+0x41)[0x56156a72ba41]
/usr/libexec/mysqld(handle_fatal_signal+0x505)[0x56156a215dd5]
sigaction.c:0(__restore_rt)[0x7f1c8f1dbd80]
/usr/libexec/mysqld(_Z17calculate_key_lenP5TABLEjPKhm+0x7)[0x56156a0ed1b7]
/usr/libexec/mysqld(+0x60426c)[0x56156a07b26c]
/usr/libexec/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x19e)[0x56156a06a69e]
/usr/libexec/mysqld(+0x5e8ee6)[0x56156a05fee6]
/usr/libexec/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x1b7)[0x56156a06a6b7]
/usr/libexec/mysqld(_ZN4JOIN10exec_innerEv+0xaf6)[0x56156a08d1d6]
/usr/libexec/mysqld(_ZN4JOIN4execEv+0x37)[0x56156a08d407]
/usr/libexec/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_sel
ect_lex+0xf3)[0x56156a08d553]
/usr/libexec/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x155)[0x56156a08de75]
/usr/libexec/mysqld(+0x5b313c)[0x56156a02a13c]
/usr/libexec/mysqld(_Z21mysql_execute_commandP3THD+0x6530)[0x56156a037350]
/usr/libexec/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x216)[0x56156a039586]
/usr/libexec/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x1fd2)[0x56156a03c432]
/usr/libexec/mysqld(_Z10do_commandP3THD+0x178)[0x56156a03d0d8]
/usr/libexec/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x212)[0x56156a1165b2]
/usr/libexec/mysqld(handle_one_connection+0x41)[0x56156a1167c1]
pthread_create.c:0(start_thread)[0x7f1c8f1d12de]
:0(__GI___clone)[0x7f1c8d10ca63]

# coredumpctl list
TIME                            PID   UID   GID SIG COREFILE  EXE
Mon 2019-06-17 18:33:14 EEST  23106    27    27  11 present   /usr/libexec/mysqld

Core dump uploaded to
https://www.mv.helsinki.fi/home/masse/core.mysqld.27.07ff5f3194684da9901198bf3b043054.23106.1560785590000000.lz4

Mariadb log: https://www.mv.helsinki.fi/home/masse/mariadb.log
coredumpctl info 23106: https://www.mv.helsinki.fi/home/masse/coredump-info.txt

Expected results:


Additional info:
- mariadb-10.2 from scl-6 works fine
- mysql-8 from RHEL-8 works fine
Comment 1 Michal Schorm 2020-01-08 15:07:09 UTC 
MariaDB 10.3.17 has been released for RHEL-8.1
https://access.redhat.com/errata/RHSA-2019:3708

Is the issue still reproducible?
Comment 2 Mikko Hirvonen 2020-01-20 18:06:57 UTC 
Yes it is.
Comment 4 Daniel Black 2020-11-18 20:42:22 UTC 
Upstream bug: https://jira.mariadb.org/browse/MDEV-19310
Comment 6 RHEL Program Management 2021-02-01 07:41:31 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.