Bug 7897 - [Anolis23.1][RC1][loongarch64]mysql服务开启失败
Summary: [Anolis23.1][RC1][loongarch64]mysql服务开启失败
Status: RESOLVED FIXED
Alias: None
Product: Anolis OS 23
Classification: Anolis OS
Component: BaseOS Packages (show other bugs) BaseOS Packages
Version: 23.1
Hardware: loongarch Linux
: P3-Medium S3-normal
Target Milestone: ---
Assignee: happy_orange
QA Contact: bolong_tbl
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-12 17:53 UTC by liqianwen
Modified: 2024-03-29 09:55 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description liqianwen loongson_group 2024-01-12 17:53:22 UTC
Description of problem:
mysql服务开启失败

软件环境:
#内核版本:
# uname -r
5.10.134-16.2_rc1.an23.loongarch64

#系统版本
# cat /etc/os-release 
NAME="Anolis OS"
VERSION="23"
ID="anolis"
VERSION_ID="23"
PLATFORM_ID="platform:an23"
PRETTY_NAME="Anolis OS 23"
ANSI_COLOR="0;31"
HOME_URL="https://openanolis.cn/"
BUG_REPORT_URL="https://bugzilla.openanolis.cn/"


Steps to Reproduce:
1.yum install mysql mysql-server
2.systemctl start mysqld
3.systemctl status mysqld

Actual results:
mysql服务开启失败
# systemctl status mysqld
× mysqld.service - MySQL 8.0 database server
     Loaded: loaded (/usr/lib/systemd/system/mysqld.service; disabled; preset: disabled)
     Active: failed (Result: exit-code) since Thu 2024-01-11 15:42:54 CST; 1 day 2h ago
        CPU: 181ms

Jan 11 15:42:54 bogon systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 5.
Jan 11 15:42:54 bogon systemd[1]: Stopped mysqld.service - MySQL 8.0 database server.
Jan 11 15:42:54 bogon systemd[1]: mysqld.service: Start request repeated too quickly.
Jan 11 15:42:54 bogon systemd[1]: mysqld.service: Failed with result 'exit-code'.
Jan 11 15:42:54 bogon systemd[1]: Failed to start mysqld.service - MySQL 8.0 database server.


Expected results:
mysql服务启动正常

Additional info:
Comment 1 wenlong loongson_group 2024-01-12 17:58:23 UTC
配置mysql日志文件后,重启mysql
[root@bogon loongarch64]# cat /etc/my.cnf.d/mysql-server.cnf 
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
log-error=/var/log/mysql/error.log
pid-file=/run/mysqld/mysqld.pid

报错信息如下
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=1ab14881feb3664df39c537cd0e261ae73711df2
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/libexec/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x4c) [0xaaafdd1f0c]
/usr/libexec/mysqld(print_fatal_signal(int)+0x33c) [0xaaaf3b92fc]
/usr/libexec/mysqld(handle_fatal_signal+0xb0) [0xaaaf3b95b0]
linux-vdso.so.1(__vdso_rt_sigreturn+0) [0xfffe854648]
/usr/libexec/mysqld(Delegate::Delegate(unsigned int)+0x37c) [0xaaafb8197c]
/usr/libexec/mysqld(delegates_init()+0x40) [0xaaafb8be20]
/usr/libexec/mysqld(+0x971960) [0xaaaf175960]
/usr/libexec/mysqld(mysqld_main(int, char**)+0x1a7c) [0xaaaf17d2bc]
/lib64/libc.so.6(+0x244a8) [0xffeffa84a8]
/lib64/libc.so.6(__libc_start_main+0xac) [0xffeffa85ac]
/usr/libexec/mysqld(_start+0x48) [0xaaaf14e078]
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.
2024-01-11T12:17:05.739618Z 0 [System] [MY-013951] [Server] 2024-01-11T12:17:05Z UTC - mysqld got signal 11 ; 
2024-01-11T12:17:05.739619Z 0 [System] [MY-013951] [Server] Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
2024-01-11T12:17:05.739620Z 0 [System] [MY-013951] [Server] BuildID[sha1]=1ab14881feb3664df39c537cd0e261ae73711df2
2024-01-11T12:17:05.739621Z 0 [System] [MY-013951] [Server] Thread pointer: 0x0
2024-01-11T12:17:05.739622Z 0 [System] [MY-013951] [Server] Attempting backtrace. You can use the following information to find out
2024-01-11T12:17:05.739623Z 0 [System] [MY-013951] [Server] where mysqld died. If you see no messages after this, something went
2024-01-11T12:17:05.739624Z 0 [System] [MY-013951] [Server] terribly wrong...
2024-01-11T12:17:05.739625Z 0 [System] [MY-013951] [Server] stack_bottom = 0 thread_stack 0x100000
2024-01-11T12:17:05.739626Z 0 [System] [MY-013951] [Server] /usr/libexec/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x4c) [0xaaafdd1f0c]
2024-01-11T12:17:05.739627Z 0 [System] [MY-013951] [Server] /usr/libexec/mysqld(print_fatal_signal(int)+0x33c) [0xaaaf3b92fc]
2024-01-11T12:17:05.739628Z 0 [System] [MY-013951] [Server] /usr/libexec/mysqld(handle_fatal_signal+0xb0) [0xaaaf3b95b0]
2024-01-11T12:17:05.739629Z 0 [System] [MY-013951] [Server] linux-vdso.so.1(__vdso_rt_sigreturn+0) [0xfffe854648]
2024-01-11T12:17:05.739630Z 0 [System] [MY-013951] [Server] /usr/libexec/mysqld(Delegate::Delegate(unsigned int)+0x37c) [0xaaafb8197c]
2024-01-11T12:17:05.739631Z 0 [System] [MY-013951] [Server] /usr/libexec/mysqld(delegates_init()+0x40) [0xaaafb8be20]
Comment 2 wenlong loongson_group 2024-01-12 17:59:17 UTC
上游在优化补丁BUG#34849343合入后,导致mysql-8.0.33在启动时崩溃,该提交只是提升性能,并不是修复mysql相关功能缺陷,回退后解决
https://github.com/mysql/mysql-server/commit/be8348a7c3e8510b998a063065b626a459631b32


修复链接:https://gitee.com/src-anolis-os/mysql/pulls/13