mysql因為事務日誌問題無法啟動
今天一個客戶反饋Mysql資料庫無法啟動,具體如下:
[root@testdb var]#service mysql start
Starting MySQL... ERROR! The server quit without updating PID file (/usr/local/mysql/mysql.pid).
初看,好像是許可權問題,但仔細檢查許可權,沒有發現問題,所以進入錯誤日誌看
[root@testdb var]# more testdb.err
2020-06-12T08:30:25.273479Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2020-06-12T08:30:25.273850Z 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.7.26-log) starting as process 10090 ...
2020-06-12T08:30:25.286777Z 0 [Note] InnoDB: PUNCH HOLE support available
2020-06-12T08:30:25.286827Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-06-12T08:30:25.286838Z 0 [Note] InnoDB: Uses event mutexes
2020-06-12T08:30:25.286845Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2020-06-12T08:30:25.286852Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-06-12T08:30:25.286856Z 0 [Note] InnoDB: Using Linux native AIO
2020-06-12T08:30:25.288765Z 0 [Note] InnoDB: Number of pools: 1
2020-06-12T08:30:25.288939Z 0 [Note] InnoDB: Using CPU crc32 instructions
2020-06-12T08:30:25.291804Z 0 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 8, chunk size = 128M
2020-06-12T08:30:25.552835Z 0 [Note] InnoDB: Completed initialization of buffer pool
2020-06-12T08:30:25.589770Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of se
tpriority().
2020-06-12T08:30:25.603855Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2020-06-12T08:30:25.627920Z 0 [ERROR] InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 3970243421 and the end 3970243072.
2020-06-12T08:30:25.627962Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2020-06-12T08:30:26.229118Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2020-06-12T08:30:26.229160Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2020-06-12T08:30:26.229168Z 0 [ERROR] Failed to initialize builtin plugins.
2020-06-12T08:30:26.229172Z 0 [ERROR] Aborting
檢視日誌,發現如下:
InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 3970243421 and the end 3970243072.
事務日誌有斷檔,估計也找不出來了,基於此,只能把原來的事務日誌ib_logfile0和ib_logfile1重新命名或者刪除掉,然後再重新啟動
[root@testdb var]#service mysql start
Starting MySQL...SUCCESS!
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/29371470/viewspace-2698468/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- MySQL 事務日誌MySql
- 關於XAMPP中Apache和Mysql因埠占用無法啟動的問題ApacheMySql
- MySQL無法啟動重啟竟是因為改了Linux主機名MySqlLinux
- StarRocks-FE無法啟動,日誌:
- MySQL-14.MySQL事務日誌MySql
- MySQL服務名無效或者MySQL正在啟動 MySQL無法啟動MySql
- Mysql 事務日誌(Ib_logfile)MySql
- SQLServer 2012 AG主節點無法截斷事務日誌SQLServer
- 《MySQL 進階篇》十九:事務日誌MySql
- 寶塔皮膚mysql無法啟動問題如何解決MySql
- MYSQL資料庫服務無法啟動MySql資料庫
- 解決ASM無法啟動問題ASM
- SQLServer 2008中事務日誌已滿問題處理SQLServer
- VMware DHCP Service服務無法啟動問題的解決
- 記一次 Ubuntu 服務 Nginx 無法啟動問題UbuntuNginx
- [MySQL] “MySQL 服務無法啟動”原理及解決方法MySql
- win10的mysql服務無法啟動Win10MySql
- Oracle Haip無法啟動問題學習OracleAI
- 【MySQL解惑筆記】Mysql5.7.x無法開啟二進位制日誌MySql筆記
- MySQL 事務、日誌、鎖、索引學習總結,MySql索引
- 神奇的DEBUG:因為異常導致MongoDB容器無法啟動MongoDB
- 因為跨域問題導致的無法讀取 response header跨域Header
- qt6 QtOpcUa無法正常啟動問題QT
- 【ASM】ASM啟動無法找到spfile問題原因ASM
- 無法開啟“fsevents.node”,因為無法驗證開發者。
- Elasticsearch 的事務日誌Elasticsearch
- mysql開啟慢日誌MySql
- MySql事務無法回滾的原因有哪些MySql
- mysql關於redo事務日誌ib_logfile的理解MySql
- 解決vscode安裝後無法啟動的問題VSCode
- Oracle日常問題-資料庫無法啟動(案例二)Oracle資料庫
- Oracle日常問題處理-資料庫無法啟動Oracle資料庫
- 【日誌亂碼】解決Tomcat啟動控制檯亂碼問題Tomcat
- Windows Defender無法開啟的問題Windows
- zookeeper 清理snapshot及事務日誌
- 11.日誌和事務@Transactional
- 無法啟動mysql服務”1067 程式意外終止”解決辦法【簡記】MySql
- Linux nohup 啟動服務且不輸出日誌Linux