mariadb 内核崩溃导致服务无法启动

最新推荐文章于 2024-08-23 17:29:03 发布
最新推荐文章于 2024-08-23 17:29:03 发布
阅读量1.6k 收藏 2
点赞数
分类专栏： 关系型数据库 OP
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/NewRain_wang/article/details/106014259
版权

数据库宕机无法启动
通过journalctl -xeu mariadb
查看日志如下

May 03 17:19:31 zabbix mysqld[52493]: thread_count=0
May 03 17:19:31 zabbix mysqld[52493]: max_threads=2002
May 03 17:19:31 zabbix mysqld[52493]: thread_count=0
May 03 17:19:31 zabbix mysqld[52493]: It is possible that mysqld could use up to
May 03 17:19:31 zabbix mysqld[52493]: It is possible that mysqld could use up to
May 03 17:19:31 zabbix mysqld[52493]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4536823 K  bytes of memory
May 03 17:19:31 zabbix mysqld[52493]: Hope that's ok; if not, decrease some variables in the equation.
May 03 17:19:31 zabbix mysqld[52493]: Thread pointer: 0x0
May 03 17:19:31 zabbix mysqld[52493]: Attempting backtrace. You can use the following information to find out
May 03 17:19:31 zabbix mysqld[52493]: where mysqld died. If you see no messages after this, something went
May 03 17:19:31 zabbix mysqld[52493]: terribly wrong...
May 03 17:19:31 zabbix mysqld[52493]: stack_bottom = 0x0 thread_stack 0x49000
May 03 17:19:31 zabbix mysqld[52493]: 2020-05-03 17:19:31 0 [Note] InnoDB: Completed initialization of buffer pool
May 03 17:19:31 zabbix mysqld[52493]: 2020-05-03 17:19:31 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be ch
May 03 17:19:31 zabbix mysqld[52493]: 2020-05-03 17:19:31 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=252665991
May 03 17:19:31 zabbix mysqld[52493]: 2020-05-03 17:19:31 0 [Note] InnoDB: Transaction 592213 was in the XA prepared state.
May 03 17:19:31 zabbix mysqld[52493]: 2020-05-03 17:19:31 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 0 row operations
May 03 17:19:31 zabbix mysqld[52493]: 2020-05-03 17:19:31 0 [Note] InnoDB: Trx id counter is 592214
May 03 17:19:31 zabbix mysqld[52493]: 2020-05-03 17:19:31 0 [Note] InnoDB: Starting final batch to recover 7 pages from redo log.
May 03 17:19:31 zabbix mysqld[52493]: 200503 17:19:31 [ERROR] mysqld got signal 11 ;
May 03 17:19:31 zabbix mysqld[52493]: This could be because you hit a bug. It is also possible that this binary
May 03 17:19:31 zabbix mysqld[52493]: or one of the libraries it was linked against is corrupt, improperly built,
May 03 17:19:31 zabbix mysqld[52493]: or misconfigured. This error can also be caused by malfunctioning hardware.
May 03 17:19:31 zabbix mysqld[52493]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
May 03 17:19:31 zabbix mysqld[52493]: We will try our best to scrape up some info that will hopefully help
May 03 17:19:31 zabbix mysqld[52493]: diagnose the problem, but since we have already crashed,
May 03 17:19:31 zabbix mysqld[52493]: something is definitely wrong and this may fail.
May 03 17:19:31 zabbix mysqld[52493]: Server version: 10.4.12-MariaDB-log
May 03 17:19:31 zabbix mysqld[52493]: key_buffer_size=134217728
May 03 17:19:31 zabbix mysqld[52493]: read_buffer_size=131072
May 03 17:19:31 zabbix mysqld[52493]: max_used_connections=0
May 03 17:19:31 zabbix mysqld[52493]: max_threads=2002
May 03 17:19:31 zabbix mysqld[52493]: thread_count=0
May 03 17:19:31 zabbix mysqld[52493]: It is possible that mysqld could use up to
May 03 17:19:31 zabbix mysqld[52493]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4536823 K  bytes of memory
May 03 17:19:31 zabbix mysqld[52493]: Hope that's ok; if not, decrease some variables in the equation.
May 03 17:19:31 zabbix mysqld[52493]: Thread pointer: 0x0
May 03 17:19:31 zabbix mysqld[52493]: Attempting backtrace. You can use the following information to find out
May 03 17:19:31 zabbix mysqld[52493]: where mysqld died. If you see no messages after this, something went
May 03 17:19:31 zabbix mysqld[52493]: terribly wrong...
May 03 17:19:31 zabbix mysqld[52493]: stack_bottom = 0x0 thread_stack 0x49000
May 03 17:19:31 zabbix mysqld[52493]: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55c5c3a31a1e]
May 03 17:19:31 zabbix mysqld[52493]: /usr/sbin/mysqld(handle_fatal_signal+0x30f)[0x55c5c34c5d8f]
May 03 17:19:31 zabbix mysqld[52493]: sigaction.c:0(__restore_rt)[0x7f99312515d0]
May 03 17:19:31 zabbix mysqld[52493]: /usr/sbin/mysqld(+0xae4b64)[0x55c5c36ecb64]
May 03 17:19:31 zabbix mysqld[52493]: /usr/sbin/mysqld(+0xae671d)[0x55c5c36ee71d]
May 03 17:19:31 zabbix mysqld[52493]: /usr/sbin/mysqld(+0xac60f5)[0x55c5c36ce0f5]
May 03 17:19:31 zabbix mysqld[52493]: /usr/sbin/mysqld(+0xac828f)[0x55c5c36d028f]
May 03 17:19:31 zabbix mysqld[52493]: /usr/sbin/mysqld(+0x5ad337)[0x55c5c31b5337]
May 03 17:19:31 zabbix mysqld[52493]: /usr/sbin/mysqld(+0xbf7462)[0x55c5c37ff462]
May 03 17:19:31 zabbix mysqld[52493]: /usr/sbin/mysqld(+0xc5f9cf)[0x55c5c38679cf]
May 03 17:19:31 zabbix mysqld[52493]: /usr/sbin/mysqld(+0xb6ddd8)[0x55c5c3775dd8]
May 03 17:19:31 zabbix mysqld[52493]: pthread_create.c:0(start_thread)[0x7f9931249dd5]
May 03 17:19:31 zabbix mysqld[52493]: /lib64/libc.so.6(clone+0x6d)[0x7f992f5ecead]
May 03 17:19:31 zabbix mysqld[52493]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
May 03 17:19:31 zabbix mysqld[52493]: information that should help you find out what is causing the crash.
May 03 17:19:31 zabbix kernel: mysqld[52499]: segfault at 0 ip 000055c5c3a2ec28 sp 00007f98ff7faeb0 error 6 in mysqld[55c5c2c08000+1483000]
May 03 17:19:31 zabbix mysqld[52493]: Writing a core file...
May 03 17:19:31 zabbix mysqld[52493]: Working directory at /var/lib/mysql
May 03 17:19:31 zabbix mysqld[52493]: Resource Limits:
May 03 17:19:31 zabbix systemd[1]: mariadb.service: main process exited, code=killed, status=11/SEGV
May 03 17:19:31 zabbix systemd[1]: Failed to start MariaDB 10.4.12 database server.
-- Subject: Unit mariadb.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit mariadb.service has failed.
-- 
-- The result is failed.
May 03 17:19:31 zabbix systemd[1]: Unit mariadb.service entered failed state.
May 03 17:19:31 zabbix systemd[1]: mariadb.service failed.

通过systemctl status mariadb 查看如下

# systemctl status mariadb
● mariadb.service - MariaDB 10.4.12 database server
   Loaded: loaded (/usr/lib/systemd/system/mariadb.service; disabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/mariadb.service.d
           └─migrated-from-my.cnf-settings.conf
   Active: activating (start) since Sun 2020-05-03 17:22:38 CST; 277ms ago
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 54301 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
  Process: 54298 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
 Main PID: 54327 (mysqld)
   Status: "Starting final batch to recover 7 pages from redo log"
   CGroup: /system.slice/mariadb.service
           └─54327 /usr/sbin/mysqld

May 03 17:22:38 zabbix mysqld[54327]: 2020-05-03 17:22:38 0 [Note] InnoDB: Number of pools: 1
May 03 17:22:38 zabbix mysqld[54327]: 2020-05-03 17:22:38 0 [Note] InnoDB: Using SSE2 crc32 instructions
May 03 17:22:38 zabbix mysqld[54327]: 2020-05-03 17:22:38 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
May 03 17:22:38 zabbix mysqld[54327]: 2020-05-03 17:22:38 0 [Note] InnoDB: Completed initialization of buffer pool
May 03 17:22:38 zabbix mysqld[54327]: 2020-05-03 17:22:38 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priori...iority().
May 03 17:22:38 zabbix mysqld[54327]: 2020-05-03 17:22:38 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=252665991
May 03 17:22:38 zabbix mysqld[54327]: 2020-05-03 17:22:38 0 [Note] InnoDB: Transaction 592213 was in the XA prepared state.
May 03 17:22:38 zabbix mysqld[54327]: 2020-05-03 17:22:38 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 0 ro...s to undo
May 03 17:22:38 zabbix mysqld[54327]: 2020-05-03 17:22:38 0 [Note] InnoDB: Trx id counter is 592214
May 03 17:22:38 zabbix mysqld[54327]: 2020-05-03 17:22:38 0 [Note] InnoDB: Starting final batch to recover 7 pages from redo log.
May 03 17:22:38 zabbix mysqld[54327]: 200503 17:22:38 [ERROR] mysqld got signal 11 ;
May 03 17:22:38 zabbix mysqld[54327]: This could be because you hit a bug. It is also possible that this binary
Hint: Some lines were ellipsized, use -l to show in full.

得到关键 信息
Starting final batch to recover 7 pages from redo log

通过百般搜索 找到下列同样案例
https://serverfault.com/questions/592793/mysql-crashed-and-wont-start-up

最终通过修改数据 [mysqld]
添加
innodb_force_recovery = 6
innodb_purge_threads = 0

启动成功

NewRain001
关注
专栏目录
fedora mysql 开机启动服务_在Fedora中启动Mysql / Mariadb失败
weixin_34835470的博客
03-04 707
无法在Fedora 17中启动mysql.我使用root帐户运行以下命令并禁用selinux.service mysqld startRedirecting to /bin/systemctl start mysqld.serviceJob for mariadb.service failed. See 'systemctl status mariadb.service' and 'journa...
阿里数据库内核月报导航
luoxn28的专栏
09-27 1319
数据库内核月报是阿里云RDS-数据库内核组维护的一个关于数据库的技术博客，上面的文章质量是有保证的。不过有一点不太友好的是，这个网站首页非常简洁，只是按照时间月份来归档文章，并没有按照...
MariaDB环境包，安装MariaDB出现错误：Failed to start mariadb.service: Unit not found。
03-18
mariadb安装依赖包 boost-program-options-1.53.0-27.el7.x86_64.rpm galera-4-26.4.2-1.rhel7.el7.centos.x86_64.rpm perl-Compress-Raw-Bzip2-2.061-3.el7.x86_64.rpm perl-Compress-Raw-Zlib-2.061-4.el7.x86_64.rpm perl-Data-Dumper-2.145-3.el7.x86_64.rpm perl-DBI-1.627-4.el7.x86_64.rpm perl-IO-Compress-2.061-2.el7.noarch.rpm perl-Net-Daemon-0.48-5.el7.noarch.rpm perl-PlRPC-0.2020-14.el7.noarch.rpm 1 yum install boost-program-options-1.53.0-27.el7.x86_64.rpm 2 yum install galera-4-26.4.2-1.rhel7.el7.centos.x86_64.rpm 3 yum install perl*
CentOS 7.4安装mariadb，启动报错
DB2_c的博客
11-30 1425
CentOS 7.4安装mariadb，启动报错 [root@iZ25b6alxstZ ~]# systemctl start mariadb Job for mariadb.service failed because the control process exited with error code. See "systemctl status mar...
【service启动mysql失败: The server quit without updating PID file】
最新发布
qq_18644663的博客
08-23 300
linux开启了selinux, selinux通过采用强制访问控制（MAC）系统，控制一个进程对具体文件系统上的文件或目录是否拥有访问权限。永久关闭：打开/etc/selinux/config，把SELINUX=enforcing改为SELINUX=disabled后存盘退出重启机器试试。使用service启动或/etc/init.d/mysql启动失败。直接执行mysqld_safe可以启动成功。查看selinux值：getenforce。临时关闭：setenforce 0。
centos7 安装mysql 解决 Failed to start mariadb.service: Unit not found.
热门推荐
Twiss的博客
04-04 4万+
涉及好多个错误。一环套一环的。 首先安装问题 首先需要安装mariadb-server systemctl start mariadb.service 会报错：Failed to start mariadb.service: Unit not found. yum install mariadb 然后使用命令systemctl start mariadb，提示如下： Failed to st...
mysql启动indb错误_关于运行mysql_install_db命令导致sudo systemctl start /restart mariadb.service启动失败问题...
weixin_29148445的博客
02-02 692
运行环境：centos 7数据库：mariadb问题描述：在yum安装mariadb数据库运行后运行了/var/lib/mysql_install_db命令,从而导致mariadb数据库启动或重启都失败。故障解决：[[emailprotected] mysql]$ sudo systemctl start mariadb.serviceJob for mariadb.service failed...
Linux内核文件系统14
weixin_46243251的博客
12-27 583
2021SC@SDUSC super.c（1） 接下来分析另一个核心部分super.c文件。 这个文件中存的是文件系统里超级块(super_block)的相关函数，对于文件系统有极大的重要性。并且这个文件代码量也很大，还是分次进行介绍。 锁排序 注意i_mmap_sem (EXT4_I(inode)->i_mmap_sem)和i_mmap_rwsem (inode->i_mmap_rwsem)之间的区别 页面错误路径: mmap_lock -> sb_start_page
CentOS7 安装后常见服务启动失败原因分析
![CentOS7 安装后常见服务启动失败原因分析]...服务启动失败是 CentOS 7 系统管理中常见的故障之一，会导致系统功能受损或无法正常运行。
企业级负载均衡集群（3）——RHCS集群配置服务
weixin_21583810的博客
06-19 278
文章目录1.配置共享磁盘2.fence节点3.配置mariadb 1.配置共享磁盘 添加vip的解析： server3增加一块共享磁盘（供server1和server4使用）： 查看添加的磁盘： 在server3上配置集群的服务端，安装软件： [root@server3 ~]# yum install -y targetcli server3这个共享磁盘的服务端配置好，然后去配置server1和server2去使用磁盘的客户端。 [root@server1 ~]# yum insta
NMAP Masscan python识别端口运行服务 常用命令速查表
浪子燕青的博客
02-27 2625
带上你的千军万马，即使最后难免孤军奋战。 阅读提要 全文约1.5W字，大致阅读完约15分钟，包含主要知识点：Nmap命令详解、Masscan命令详解、python调用Nmap、python调用Masscan、端口运行服务识别、IPY库生成相关IP段，其中关键部位文字使用橙色重点标注。 Nmap功能 端口扫描：扫描开放的端口并且识别运行服务 主机探测：Nmap可査找目标网络中的在线主机。默认情况下，Nmap通过4种方式—— ICMP echo请求（ping）、向443端口发送TCP SYN 包、向8
解决mariadb数据库服务无法开启
weixin_30847865的博客
04-21 1025
我的系统Manjaro linux，安装的数据库为mariadb 10.1 1、安装数据库 pacman -S mariadb 2、配置数据库启动环境： mysql_install_db --user=mysql --basedir=/usr --datadir=/var/lib/mysql 3、启动服务： systemctl start mariadb 4、启动数据库： my...
linux下mariadb的服务启动异常,centos7 – CentOS 7 MariaDB错误“无法启动mariadb.service：找不到单位.”...
weixin_29074409的博客
05-02 1533
我对Linux有点新手,在Windows上的Virtualbox中测试各种LAMP设置.目前我有一台Centos 7 VM,我正在尝试安装MariaDB.我在这里遵循指示：http://www.tecmint.com/install-lamp-in-centos-7我跑了# yum install mariadb-server mariadb根据终端输出安装成功,但是当我运行时：# systemc...
记一次mariadb安装后无法启动的解决方法
hf_peace_l的博客
04-25 5114
配置mariadb.service后，通过systemctl start mariadb，提示异常。操作系统：CentOS Linux release 7.6.1810 (Core)1、检查/usr/local/mysql/bin/mariadbd 权限。执行 journalctl -xe 后提示 没有权限。发现/opt/ 下 soft 目录没有其他人的权限。若提示没有mysql，检查下mysql环境变量。给 /opt/soft添加 其他人权限。查看mariadb的服务状态已正常。mariadb安装目录。
mysql mariadb不能启动原因_CentOS7安装mariaDB以及无法启动的问题
weixin_39722563的博客
02-17 2572
安装mariadb1. 搜索安装包cmd：yum search mariadbmariadb-bench.x86_64mariadb-embedded-devel.i686mariadb-embedded.x86_64mariadb-server.x86_64mariadb-devel.i686mariadb-embedded-devel.x86_64 mariadb-libs.i686mari...
mysql begun_个人笔记：centos环境mysql mariadb无法启动的处置（关键还是要细看mysql日志）...
weixin_39844284的博客
01-27 637
故障现象：无法正常启动[root@VM_0_3_centos ~]# systemctl start mariadbJob for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe"...
CentOS7 mariadb重启报错
2302_77302329的博客
05-22 505
环境：CentOS7 命令： systemctl restart mariadb错误信息： 使用journalctl -xe查看： 原因 1、本机本身就安装了MySQL，当然和mariadb是冲突的 2、安装了Docker，Docker里面运行了MySQL并且映射了主机的3306端口，挂载了主机的配置和数据文件。 所以无法停止和启动mariadb。netstat -an|grep 3306 ps -ef|grep mysql whereis mysql 如果端口监听、有进程、有文件，肯定是已经安装
mariadb崩溃后如何恢复
weixin_36808034的博客
08-05 1085
项目场景： X厦项目，物联网平台 问题描述： 实际生产环境mariadb数据库突然崩溃 原因分析： 查看mariadb.log堆栈信息，崩溃前未执行过任何sql语句，莫名奇妙就崩溃了，因此怀疑服务器突然断电导致的。之所以未执行sql，因为恰巧客户平台使用授权到期，Java程序死掉，所以不会有sql执行。 解决方案： （1）修改数据库配置文件my.cnf中增加 [mysqld] innodb_force_recovery = 6 //注意此值范围0~6，值越大，限制越大 innodb_pur
centos7安装初次mariadb启动错误解决思路
weixin_42507504的博客
08-10 3801
【注意】叙述的是第一次安装mariadb时候出现systemctl start mariadb时启动失败。 [root@db01 ~]# systemctl status mariadb ● mariadb.service - MariaDB database server Loaded: loaded (/usr/lib/systemd/system/mariadb.service; disabled; vendor preset: disabled) Active: failed (Resu
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值