我的mysql服务器停止后无法启动
命令使用:
sudo /etc/init.d/mysql restart
错误:
重新启动mysql(通过systemctl):mysql.service的作业失败,因为控制进程退出并返回错误代码。
已使用systemctl status mysql.service
和journalctl -xe
检查状态,未获得任何帮助。
错误日志:
2020-06-23T00:11:48.882919Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use
- -explicit_defaults_for_timestamp服务器选项(有关详细信息,请参见文档)。
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
已更改。请参见setpriority()的手册页。
2020-06-23T00:11:48.913543Z 0 [Note] InnoDB: The first innodb_system data file 'ibdata1' did not exist. A new tablespace will
被创造!
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
系统表空间,并且在此失败,您现在应该将my. cnf中的innodb_data_file_path编辑回原来的位置,并删除在此失败尝试中创建的新ibdata文件InnoDB。InnoDB只将这些文件写满零,但尚未以任何方式使用它们。但要小心:不要删除包含您的宝贵数据的旧数据文件!
2020-06-23T00:11:48.913903Z 0 [ERROR] InnoDB: InnoDB Database creation was aborted with error Cannot open a file. You may need to
在尝试再次启动之前删除ibdata1文件。
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)
5条答案
按热度按时间lvjbypge1#
Mysql服务器在我的新Ubuntu 18.04示例上意外停止,并在尝试启动时获得相同的错误。
运行命令
systemctl status mysql.service
时经过近6个小时的努力,在互联网上搜索终于找到了解决方案。
huus2vyu2#
我的问题是通过执行以下命令:
查看mysql:管理员/变量/日志/错误日志
日志/变量/变量/变量
chown根目录:系统日志/var/log
chown根目录:根目录/变量
chmod 0640/变量/日志/mysql/错误日志
文件/变量/日志/mysql
chmod 0775 /变量/日志
变更模块0755 /变量
系统状态mysql.service
gfttwv5a3#
向所有人致意。
感谢您发送的所有消息,这些消息对我非常有用,但在我的案例中,根本原因是/var文件系统已满(100%占用),我只是复制大小或物理分区,我可以重新启动“mysql”关系数据库管理系统。如果你不能增加/var文件系统的大小,然后评估哪些日志文件最大,您可以“接触”哪些日志文件以消除其内容并重新创建其中没有任何数据的日志文件(只是日志文件名)。我希望这对你和对我一样有帮助
行政长官
bnl4lu3b4#
已解决这些命令的问题
oiopk7p55#
在我的情况下,它是RAM。
但是如果你在一个512MB的droplet上同时运行git和一个完整的WordPress,那么它可能会耗尽内存,实际上在512MB上运行WordPress是相当困难的。
我一般会说WordPress在生产中最少需要1GB的RAM。你可能可以在512MB上运行,但如果只有几个人同时访问你的网站,WordPress正在检查更新,那么你很容易就会耗尽RAM。
Source