Description:
CentOS Linux release 7.8.2003 (AltArch)
Environment:
MySQL Version: 8.0.34
Operating System: CentOS Linux release 7.8.2003 (AltArch)
Architecture: aarch64
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 1
Core(s) per socket: 8
Socket(s): 1
NUMA node(s): 1
Model: 0
CPU max MHz: 2400.0000
CPU min MHz: 2400.0000
BogoMIPS: 200.00
NUMA node0 CPU(s): 0-7
Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma dcpop asimddp asimdfhm
Summary:
After upgrading MySQL from version 8.0.32 to 8.0.33, MySQL fails to start on a CentOS system with ARM architecture. Attempts to start MySQL, both on the existing data directory and after deleting the data directory, result in a startup error.
Detailed Description:
After upgrading MySQL from version 8.0.32 to 8.0.33, attempting to start MySQL on CentOS 7.9 system with ARM architecture results in a "Segmentation fault" error. This error occurs during the MySQL startup process, preventing MySQL from running properly. Based on the error message, this seems to be a potential software issue, although it could also be related to hardware malfunction.
Error Message:
2023-10-06T05:17:23.645550Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2023-10-06T05:17:23.809473Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.1.0) starting as process 23235
2023-10-06T05:17:23Z UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=fe507a55f0a6ace5606354f6b1e33fe7120aeba1
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 = 0 thread_stack 0x100000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x44) [0x1e36a84]
/usr/sbin/mysqld(print_fatal_signal(int)+0x33c) [0xf1ed9c]
/usr/sbin/mysqld(handle_fatal_signal+0x98) [0xf1ee78]
[0xffffa9b7066c]
/usr/sbin/mysqld(memory::Aligned_atomic<long>::Aligned_atomic()+0x70) [0x1af17d0]
/usr/sbin/mysqld(Delegate::Delegate(unsigned int)+0x5c) [0x1af1a7c]
/usr/sbin/mysqld(delegates_init()+0x40) [0x1af1be0]
/usr/sbin/mysqld() [0xce7570]
/usr/sbin/mysqld(mysqld_main(int, char**)+0x204c) [0xcee88c]
/lib64/libc.so.6(__libc_start_main+0xf0) [0xffffa9341724]
/usr/sbin/mysqld() [0xcd30c0]
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.
How to repeat:
rpm -Uvh mysql-community-common-8.1.0-1.el7.aarch64.rpm --nodeps
rpm -Uvh mysql-community-client-plugins-8.1.0-1.el7.aarch64.rpm --nodeps
rpm -Uvh mysql-community-libs-8.1.0-1.el7.aarch64.rpm
rpm -Uvh mysql-community-client-8.1.0-1.el7.aarch64.rpm
rpm -Uvh mysql-community-icu-data-files-8.1.0-1.el7.aarch64.rpm --nodeps
rpm -Uvh mysql-community-server-8.1.0-1.el7.aarch64.rpm
systemctl start mysqld
