2020-05-27 06:06:01 200528 17:17:41 mysqld_safe mysqld from pid file /alidata/server/mysql/data/izwz90q83mb4gjptvvinbrz.pid ended
200528 17:18:19 mysqld_safe Starting mysqld daemon with databases from /alidata/server/mysql/data
2020-05-28 17:18:19 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2020-05-28 17:18:19 1448 [Note] Plugin 'FEDERATED' is disabled.
2020-05-28 17:18:19 1448 [Note] InnoDB: Using atomics to ref count buffer pool pages
2020-05-28 17:18:19 1448 [Note] InnoDB: The InnoDB memory heap is disabled
2020-05-28 17:18:19 1448 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-05-28 17:18:19 1448 [Note] InnoDB: Memory barrier is not used
2020-05-28 17:18:19 1448 [Note] InnoDB: Compressed tables use zlib 1.2.3
2020-05-28 17:18:19 1448 [Note] InnoDB: Using Linux native AIO
2020-05-28 17:18:19 1448 [Note] InnoDB: Using CPU crc32 instructions
2020-05-28 17:18:19 1448 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-05-28 17:18:19 1448 [Note] InnoDB: Completed initialization of buffer pool
2020-05-28 17:18:19 1448 [Note] InnoDB: Highest supported file format is Barracuda.
2020-05-28 17:18:20 1448 [Note] InnoDB: 128 rollback segment(s) are active.
2020-05-28 17:18:20 1448 [Note] InnoDB: Waiting for purge to start
2020-05-28 17:18:20 1448 [Note] InnoDB: 5.6.21 started; log sequence number 532176076
09:18:20 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
uj5u.com熱心網友回復：
1. 看下配置是否有錯誤？2. 是使用什么方式安裝的？安裝路徑在哪里？對應的庫的版本資訊查看一下是否正確？
一般情況下是配置錯誤引起的
uj5u.com熱心網友回復：
你好，網站已經運行了有一段時間配置是沒有問題的，
我之后去網站下面檢查了logs日志洗掉掉掉后，有部分頁面恢復了
然后通過Network/preview 看到的是資料庫的問題。
uj5u.com熱心網友回復：
是不是磁盤空間不足了？
uj5u.com熱心網友回復：
因為這個資料庫崩潰了導致了網站，這里有了兩個問題，一個是日志的問題沒有及時清理了，一個是資料庫的Innodb引擎有些檔案沒有執行，最后解決了
轉載請註明出處，本文鏈接：https://www.uj5u.com/shujuku/14973.html
標籤：MySQL
上一篇：對資料表中某2列的值對調