mysql 一種crash的解決方法

來源:本站原創 Linux 超過984 views圍觀 0條評論


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
[[email protected] ~]# 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
[[email protected] ~]#
[[email protected] ~]#
[[email protected] ~]#
[[email protected] ~]#
[[email protected] ~]# find / -name ibdata*     因數據損壞,導致無法重啟,刪掉下面文件即可.
[[email protected] ~]# find / -name ib_logfile*
[[email protected] ~]# rm -rf /var/lib/mysql/ibdata1
[[email protected] ~]# rm -rf /var/lib/mysql/ib_logfile0
[[email protected] ~]# rm -rf /var/lib/mysql/ib_logfile1
[[email protected] ~]#
[[email protected] ~]#
systemctl restart mariadb  重起成功
[[email protected] ~]#

文章出自:CCIE那點事 版權所有。本站文章除注明出處外,皆為作者原創文章,可自由引用,但請注明來源。 禁止全文轉載。