[MDEV-27102] MariaDB Crash (Signal 11) when running mysql_upgrade Created: 2021-11-21  Updated: 2021-11-21  Resolved: 2021-11-21

Status: Closed
Project: MariaDB Server
Component/s: SSL
Affects Version/s: 10.6.5
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Reuben Farrelly Assignee: Sergei Golubchik
Resolution: Duplicate Votes: 0
Labels: None
Environment:

thunderstorm ~ # emerge --info
Portage 3.0.28 (python 3.9.9-final-0, default/linux/amd64/17.1/no-multilib, gcc-11.2.0, glibc-2.34-r2, 5.15.3-gentoo x86_64)
=================================================================
System uname: Linux-5.15.3-gentoo-x86_64-Intel-R-Core-TM-_i7-10710U_CPU@_1.10GHz-with-glibc2.34
KiB Mem: 8175352 total, 390060 free
KiB Swap: 2096104 total, 2094312 free
Head commit of repository gentoo: 0718427ea68c16bb7091984e4829ece307d4e138

sh bash 5.1_p12
ld GNU ld (Gentoo 2.37_p1 p1) 2.37
app-shells/bash: 5.1_p12::gentoo
dev-lang/perl: 5.34.0-r5::gentoo
dev-lang/python: 2.7.18_p13::gentoo, 3.9.9::gentoo, 3.10.0_p1::gentoo, 3.11.0_alpha2::gentoo
dev-lang/rust: 1.56.1::gentoo
dev-util/cmake: 3.22.0::gentoo
sys-apps/baselayout: 2.8::gentoo
sys-apps/openrc: 0.44.8::gentoo
sys-apps/sandbox: 2.29::gentoo
sys-devel/autoconf: 2.71-r1::gentoo
sys-devel/automake: 1.16.5::gentoo
sys-devel/binutils: 2.37_p1-r1::gentoo
sys-devel/gcc: 11.2.0::gentoo
sys-devel/gcc-config: 2.5::gentoo
sys-devel/libtool: 2.4.6-r6::gentoo
sys-devel/make: 4.3::gentoo
sys-kernel/linux-headers: 5.15::gentoo (virtual/os-headers)
sys-libs/glibc: 2.34-r2::gentoo


Attachments: Text File mariadb-error-log.txt    
Issue Links:
Duplicate
is duplicated by MDEV-26950 mysqld got signal 6 Closed

 Description   

I have just upgraded from 10.5.12 to 10.6.5 (using the Gentoo ebuild) and upon upgrade am attempting to run mysql_upgrade. However it repeatably and reliably crashes out with a Signal 11 message. The output looks like this:

thunderstorm # mysql_upgrade 
Phase 1/7: Checking and upgrading mysql database
Processing databases
mysql
mysql.column_stats                                 OK
mysql.columns_priv                                 OK
mysql.db                                           OK
mysql.event                                        OK
mysql.func                                         OK
mysql.global_priv                                  OK
mysql.gtid_slave_pos                               OK
mysql.help_category                                OK
mysql.help_keyword                                 OK
mysql.help_relation                                OK
mysql.help_topic                                   OK
mysql.index_stats                                  OK
mysql.innodb_index_stats                           OK
mysql.innodb_table_stats                           OK
mysql.plugin                                       OK
mysql.proc                                         OK
mysql.procs_priv                                   OK
mysql.proxies_priv                                 OK
mysql.roles_mapping                                OK
mysql.servers                                      OK
mysql.table_stats                                  OK
mysql.tables_priv                                  OK
mysql.time_zone                                    OK
mysql.time_zone_leap_second                        OK
mysql.time_zone_name                               OK
mysql.time_zone_transition                         OK
mysql.time_zone_transition_type                    OK
mysql.transaction_registry                         OK
Phase 2/7: Installing used storage engines... Skipped
Phase 3/7: Fixing views
mysqlcheck: Got error: 2013: Lost connection to server during query when executing 'REPAIR NO_WRITE_TO_BINLOG VIEW ... '
FATAL ERROR: Upgrade failed
thunderstorm #

I can then restart mysqld just fine and it seems to work however the event scheduler is disabled from that point on.

The error log is attached which had lots more information in it.



 Comments   
Comment by Sergei Golubchik [ 2021-11-21 ]

What OpenSSL version do you have?

Comment by Reuben Farrelly [ 2021-11-21 ]

OpenSSL-3.0. Do you think it could be caused by that?

Comment by Sergei Golubchik [ 2021-11-21 ]

Yes, it absolutely is. See a very similar stack trace in MDEV-26950.

OpenSSL 3.0 support is work in progress at the moment, you can follow MDEV-25785/

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