无法启动 MySQL 服务器 - 控制进程退出并显示错误

问题描述

我的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模板网！