快捷導(dǎo)航

mysql斷電后無法啟動(dòng)的問題小結(jié)

更新時(shí)間：2024年04月13日 10:48:52 作者：bug_tan90

這篇文章主要介紹了mysql斷電后無法啟動(dòng)的問題小結(jié),本文給大家介紹的非常詳細(xì),對(duì)大家的學(xué)習(xí)或工作具有一定的參考借鑒價(jià)值,需要的朋友參考下吧

1、配置/etc/my.cnf

innodb_force_recovery=6(這個(gè)值越小越安全,最開始建議設(shè)置為1，如果也無法啟動(dòng)再改為2，以此內(nèi)推)
1 (SRV_FORCE_IGNORE_CORRUPT)：即使服務(wù)器檢測(cè)到損壞的頁(yè)仍讓它運(yùn)行。試圖使SELECT* FROM tbl_name跳過損壞的索引記錄和頁(yè)，這樣有助于轉(zhuǎn)儲(chǔ)表。
2 (SRV_FORCE_NO_BACKGROUND)：阻止主線程和任何清除線程的運(yùn)行。如果崩潰會(huì)在清除操作中發(fā)生，該恢復(fù)值會(huì)阻止它。
3 (SRV_FORCE_NO_TRX_UNDO)：不要在崩潰恢復(fù)后運(yùn)行事務(wù)回滾。
4 (SRV_FORCE_NO_IBUF_MERGE)：阻止插入緩沖合并操作。如果它們會(huì)導(dǎo)致崩潰，不要做這些。不計(jì)算表統(tǒng)計(jì)。這個(gè)值可以永久損壞數(shù)據(jù)文件。使用這個(gè)值后，準(zhǔn)備號(hào)刪除并重建所有輔助索引。在MySQL5.6.15中，設(shè)置InnoDB為只讀。
5 (SRV_FORCE_NO_UNDO_LOG_SCAN)：在啟動(dòng)數(shù)據(jù)庫(kù)時(shí)不查看撤消日志：InnoDB將即使未完成的事務(wù)也作為已提交。這個(gè)值可以永久損壞數(shù)據(jù)文件。在MySQL5.6.15中，設(shè)置InnoDB為只讀。
6 (SRV_FORCE_NO_LOG_REDO)：不要通過恢復(fù)對(duì)重做日志進(jìn)行前滾。這個(gè)值可能永久損壞數(shù)據(jù)文件。數(shù)據(jù)庫(kù)頁(yè)被留在一個(gè)陳舊的狀態(tài)，這反過來又可能帶給B-trees和其它數(shù)據(jù)庫(kù)結(jié)構(gòu)更多的損壞。在MySQL5.6.15中，設(shè)置InnoDB為只讀。

2、重啟服務(wù)

/etc/init.d/mysql start

3、異常點(diǎn)

2024-04-12T07:19:50.994404Z mysqld_safe Logging to '/usr/local/mysql/data/mysql.err'.
2024-04-12T07:19:51.048096Z mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
2024-04-12T07:19:51.063416Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2024-04-12T07:19:51.327272Z 0 [Warning] [MY-011070] [Server] 'Disabling symbolic links using --skip-symbolic-links (or equivalent) is the default. Consider not using this option as it' is deprecated and will be removed in a future release.
2024-04-12T07:19:51.327440Z 0 [System] [MY-010116] [Server] /usr/local/mysql/bin/mysqld (mysqld 8.1.0) starting as process 28354
2024-04-12T07:19:51.340376Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-04-12T07:19:52.829398Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-04-12T07:19:53.028010Z 1 [Warning] [MY-011018] [InnoDB] Skip updating information_schema metadata in InnoDB read-only mode.
2024-04-12T07:19:53.028118Z 1 [Warning] [MY-010005] [Server] Skip re-populating collations and character sets tables in InnoDB read-only mode.
2024-04-12T07:19:53.060142Z 2 [Warning] [MY-011018] [Server] Skip updating information_schema metadata in InnoDB read-only mode.
2024-04-12T07:19:53.061771Z 0 [Warning] [MY-010970] [Server] Skipped updating resource group metadata in InnoDB read only mode.
2024-04-12T07:19:53.061840Z 0 [Warning] [MY-010970] [Server] Skipped updating resource group metadata in InnoDB read only mode.
2024-04-12T07:19:53.238265Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2024-04-12T07:19:53.238343Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2024-04-12T07:19:53.256339Z 0 [ERROR] [MY-000067] [Server] unknown variable 'innodb_purge_thread=0'.
2024-04-12T07:19:53.256463Z 0 [ERROR] [MY-010119] [Server] Aborting
2024-04-12T07:19:53.896663Z 0 [System] [MY-010910] [Server] /usr/local/mysql/bin/mysqld: Shutdown complete (mysqld 8.1.0)  MySQL Community Server - GPL.
2024-04-12T07:19:53.898123Z 0 [System] [MY-015016] [Server] MySQL Server - end.
2024-04-12T07:19:54.069350Z mysqld_safe mysqld from pid file /usr/local/mysql/data/mysql.pid ended

注意error部分，my。cnf配置文件有無法解析的參數(shù)，刪掉就可以
4、恢復(fù)出錯(cuò)文件

到此這篇關(guān)于mysql斷電后無法啟動(dòng)的問題小結(jié)的文章就介紹到這了,更多相關(guān)mysql斷電后無法啟動(dòng)內(nèi)容請(qǐng)搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關(guān)文章希望大家以后多多支持腳本之家！

您可能感興趣的文章: