mysql 一种crash的解决方法

No Comments Linux ,


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 = 0x0 thread_stack 0x48000
The manual page at contains
information that should help you find out what is causing the crash.————crash———–
170927 19:20:03 mysqld_safe mysqld from pid file /var/run/mariadb/ ended
[root@zabbix01 ~]# df -h
Filesystem           Size  Used Avail Use% Mounted on
/dev/mapper/cl-root   17G  2.1G   15G  13% /
devtmpfs             1.9G     0  1.9G   0% /dev
tmpfs                1.9G   12K  1.9G   1% /dev/shm
tmpfs                1.9G  8.7M  1.9G   1% /run
tmpfs                1.9G     0  1.9G   0% /sys/fs/cgroup
/dev/sda1           1014M  184M  831M  19% /boot
tmpfs                378M     0  378M   0% /run/user/0
[root@zabbix01 ~]#
[root@zabbix01 ~]#
[root@zabbix01 ~]#
[root@zabbix01 ~]#
[root@zabbix01 ~]# find / -name ibdata*     因数据损坏,导致无法重启,删掉下面文件即可.
[root@zabbix01 ~]# find / -name ib_logfile*
[root@zabbix01 ~]# rm -rf /var/lib/mysql/ibdata1
[root@zabbix01 ~]# rm -rf /var/lib/mysql/ib_logfile0
[root@zabbix01 ~]# rm -rf /var/lib/mysql/ib_logfile1
[root@zabbix01 ~]#
[root@zabbix01 ~]#
systemctl restart mariadb  重起成功
[root@zabbix01 ~]#