問題描述

我的mysql服務器停止后沒有啟動

命令使用:

sudo/etc/init.d/mysql restart

錯誤:

重啟mysql(通過systemctl):mysql.serviceJob for mysql.service失敗，因為控制進程退出并顯示錯誤代碼.

使用systemctl status mysql.service和journalctl -xe檢查狀態，沒有得到任何幫助.

錯誤日志:

-

2020-06-23T00:11:48.882919Z 0 [警告] 不推薦使用具有隱式 DEFAULT 值的 TIMESTAMP.請用

--explicit_defaults_for_timestamp 服務器選項(有關詳細信息，請參閱文檔).

2020-06-23T00:11:48.883135Z 0 [警告] 無法創建測試文件/u1/mysql/sad-swh.lower-test2020-06-23T00:11:48.883185Z 0 [注意]/usr/sbin/mysqld (mysqld 5.7.30-0ubuntu0.18.04.1) 從進程 28411 開始......2020-06-23T00:11:48.886131Z 0 [警告] 無法創建測試文件/u1/mysql/sad-swh.lower-test2020-06-23T00:11:48.886148Z 0 [警告] 無法創建測試文件/u1/mysql/sad-swh.lower-test2020-06-23T00:11:48.889591Z 0 [注意] InnoDB:可用打孔支持2020-06-23T00:11:48.889612Z 0 [注意] InnoDB:互斥鎖和 rw_locks 使用 GCC 原子內置函數2020-06-23T00:11:48.889616Z 0 [注意] InnoDB:使用事件互斥鎖2020-06-23T00:11:48.889620Z 0 [注意] InnoDB:GCC 內置 __atomic_thread_fence() 用于內存屏障2020-06-23T00:11:48.889623Z 0 [注意] InnoDB:壓縮表使用 zlib 1.2.112020-06-23T00:11:48.889627Z 0 [注意] InnoDB:使用 Linux 原生 AIO2020-06-23T00:11:48.889890Z 0 [注意] InnoDB:池數:12020-06-23T00:11:48.890022Z 0 [注意] InnoDB:使用 CPU crc32 指令2020-06-23T00:11:48.892207Z 0 [注意] InnoDB:初始化緩沖池，總大小=128M，實例=1，塊大小=128M2020-06-23T00:11:48.900818Z 0 [注意] InnoDB:緩沖池初始化完成2020-06-23T00:11:48.903535Z 0 [注意] InnoDB:如果mysqld執行用戶被授權，頁面清理線程優先級可以

變了.請參閱 setpriority() 的手冊頁.

2020-06-23T00:11:48.913543Z 0 [注意] InnoDB:第一個 innodb_system 數據文件 'ibdata1' 不存在.一個新的表空間將

被創造！

2020-06-23T00:11:48.913858Z 0 [ERROR] InnoDB:文件操作中的操作系統錯誤號 13.2020-06-23T00:11:48.913871Z 0 [錯誤] InnoDB:錯誤意味著 mysqld 沒有目錄的訪問權限.2020-06-23T00:11:48.913878Z 0 [錯誤] InnoDB:文件操作中的操作系統錯誤號 13.2020-06-23T00:11:48.913883Z 0 [ERROR] InnoDB:錯誤意味著 mysqld 沒有目錄的訪問權限.2020-06-23T00:11:48.913889Z 0 [錯誤] InnoDB:無法打開數據文件./ibdata1"2020-06-23T00:11:48.913896Z 0 [錯誤] InnoDB:無法打開或創建系統表空間.如果您嘗試將新數據文件添加到

系統表空間，這里失敗了，你現在應該編輯my.cnf 中的 innodb_data_file_path 恢復原狀，并刪除InnoDB 在這次失敗的嘗試中創建了新的 ibdata 文件.僅 InnoDB寫了那些滿是零的文件，但還沒有以任何方式使用它們.但要小心:不要刪除包含您的舊數據文件寶貴的數據！

2020-06-23T00:11:48.913903Z 0 [ERROR] InnoDB:InnoDB 數據庫創建因錯誤無法打開文件而中止.你可能需要

在嘗試重新啟動之前刪除 ibdata1 文件.

2020-06-23T00:11:49.514733Z 0 [ERROR] 插件InnoDB"初始化函數返回錯誤.2020-06-23T00:11:49.514763Z 0 [錯誤] 插件InnoDB"注冊為存儲引擎失敗.2020-06-23T00:11:49.514773Z 0 [錯誤] 無法初始化內置插件.2020-06-23T00:11:49.514779Z 0 [錯誤] 中止2020-06-23T00:11:49.514817Z 0 [注意] Binlog 結束2020-06-23T00:11:49.514889Z 0 [注意] 關閉插件CSV"2020-06-23T00:11:49.515486Z 0 [注意]/usr/sbin/mysqld:關閉完成

 ● mysql.service - MySQL 社區服務器已加載:已加載 (/lib/systemd/system/mysql.service;啟用；供應商預設:啟用)活動:失敗(結果:退出代碼)自周一 2020-06-22 16:07:36 CST；9 分鐘前進程:26756 ExecStart=/usr/sbin/mysqld --daemonize --pid-file=/run/mysqld/mysqld.pid (code=exited, status=1/FAILURE) 進程:26737 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS) Main PID: 18936 (code=exited, status=0/SUCCESS)

Mysql 服務器在我新的 Ubuntu 18.04 實例上意外停止，并在嘗試啟動時遇到相同的錯誤.

mysql.service 的作業失敗，因為控制進程退出并顯示錯誤代碼.參見systemctl status mysql.service"和journalctl -xe"詳情.

運行命令時systemctl status mysql.service

● mysql.service - MySQL 社區服務器已加載:已加載(/lib/systemd/system/mysql.service；已啟用；供應商預設:已啟用)活動:自 UTC 周六 2020-08-29 17:11:53 起失敗(結果:退出代碼)；11 秒前進程:3124 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=1/FAILURE)主PID:2557(代碼=退出，狀態=0/成功)8 月 29 日 17:11:53 ip-172-26-10-122 systemd[1]:mysql.service:控制進程退出，代碼=退出狀態=18 月 29 日 17:11:53 ip-172-26-10-122 systemd[1]:mysql.service:失敗，結果為退出代碼".8 月 29 日 17:11:53 ip-172-26-10-122 systemd[1]:無法啟動 MySQL 社區服務器.

在網上搜索了將近 6 個小時后，終于找到了解決方案.

sudo chmod -R u+rwx/etc/mysql/須藤 chown -R mysql.mysql/etc/mysql/

My mysql server is not starting after stopping it

Command using:

sudo /etc/init.d/mysql restart

Error :

Restarting mysql (via systemctl): mysql.serviceJob for mysql.service failed because the control process exited with error code.

Checked status using systemctl status mysql.service and journalctl -xe, did not get any help.

Error log:

-

2020-06-23T00:11:48.882919Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use

--explicit_defaults_for_timestamp server option (see documentation for more details).

2020-06-23T00:11:48.883135Z 0 [Warning] Can't create test file /u1/mysql/sad-swh.lower-test

2020-06-23T00:11:48.883185Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.30-0ubuntu0.18.04.1) starting as process 28411 ...

2020-06-23T00:11:48.886131Z 0 [Warning] Can't create test file /u1/mysql/sad-swh.lower-test

2020-06-23T00:11:48.886148Z 0 [Warning] Can't create test file /u1/mysql/sad-swh.lower-test

2020-06-23T00:11:48.889591Z 0 [Note] InnoDB: PUNCH HOLE support available

2020-06-23T00:11:48.889612Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2020-06-23T00:11:48.889616Z 0 [Note] InnoDB: Uses event mutexes

2020-06-23T00:11:48.889620Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2020-06-23T00:11:48.889623Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11

2020-06-23T00:11:48.889627Z 0 [Note] InnoDB: Using Linux native AIO

2020-06-23T00:11:48.889890Z 0 [Note] InnoDB: Number of pools: 1

2020-06-23T00:11:48.890022Z 0 [Note] InnoDB: Using CPU crc32 instructions

2020-06-23T00:11:48.892207Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M

2020-06-23T00:11:48.900818Z 0 [Note] InnoDB: Completed initialization of buffer pool

2020-06-23T00:11:48.903535Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be

changed. See the man page of setpriority().

2020-06-23T00:11:48.913543Z 0 [Note] InnoDB: The first innodb_system data file 'ibdata1' did not exist. A new tablespace will

be created!

2020-06-23T00:11:48.913858Z 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.

2020-06-23T00:11:48.913871Z 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.

2020-06-23T00:11:48.913878Z 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.

2020-06-23T00:11:48.913883Z 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.

2020-06-23T00:11:48.913889Z 0 [ERROR] InnoDB: Cannot open datafile './ibdata1'

2020-06-23T00:11:48.913896Z 0 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to

the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!

2020-06-23T00:11:48.913903Z 0 [ERROR] InnoDB: InnoDB Database creation was aborted with error Cannot open a file. You may need to

delete the ibdata1 file before trying to start up again.

2020-06-23T00:11:49.514733Z 0 [ERROR] Plugin 'InnoDB' init function returned error.

2020-06-23T00:11:49.514763Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2020-06-23T00:11:49.514773Z 0 [ERROR] Failed to initialize builtin plugins.

2020-06-23T00:11:49.514779Z 0 [ERROR] Aborting

2020-06-23T00:11:49.514817Z 0 [Note] Binlog end

2020-06-23T00:11:49.514889Z 0 [Note] Shutting down plugin 'CSV'

2020-06-23T00:11:49.515486Z 0 [Note] /usr/sbin/mysqld: Shutdown complete

 ● mysql.service - MySQL Community Server Loaded: loaded (/lib/systemd/system/mysql.service;
 enabled;
 vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2020-06-22 16:07:36 CST;
 9min ago Process: 26756 ExecStart=/usr/sbin/mysqld --daemonize --pid-file=/run/mysqld/mysqld.pid (code=exited, status=1/FAILURE) Process: 26737 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS) Main PID: 18936 (code=exited, status=0/SUCCESS)

Mysql server stopped unexpectedly on my new on Ubuntu 18.04 instance, and getting same error while trying to start.

Job for mysql.service failed because the control process exited with error code.
See "systemctl status mysql.service" and "journalctl -xe" for details.

When running the command systemctl status mysql.service

● mysql.service - MySQL Community Server
   Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2020-08-29 17:11:53 UTC; 11s ago
  Process: 3124 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=1/FAILURE)
 Main PID: 2557 (code=exited, status=0/SUCCESS)

Aug 29 17:11:53 ip-172-26-10-122 systemd[1]: mysql.service: Control process exited, code=exited status=1
Aug 29 17:11:53 ip-172-26-10-122 systemd[1]: mysql.service: Failed with result 'exit-code'.
Aug 29 17:11:53 ip-172-26-10-122 systemd[1]: Failed to start MySQL Community Server.

After struggling almost 6 hours searching over the internet finally got the solution.

sudo chmod -R u+rwx /etc/mysql/
sudo chown -R mysql.mysql /etc/mysql/

這篇關于無法啟動 MySQL 服務器 - 控制進程退出并顯示錯誤代碼的文章就介紹到這了，希望我們推薦的答案對大家有所幫助，也希望大家多多支持html5模板網！