Question

我尝试重新启动mysql 5.7： service mysql restart

但是它失败了，我不明白为什么：

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

我看不到日志中有什么问题：

systemctl status mariadb.service
● mariadb.service - MariaDB 10.1.37 database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2019-02-25 22:02:52 GMT; 1min 9s ago
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 15467 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=127)
 Main PID: 28679 (code=exited, status=0/SUCCESS)

Feb 25 22:02:52 stretch systemd[1]: Starting MariaDB 10.1.37 database server...
Feb 25 22:02:52 stretch systemd[1]: mariadb.service: Control process exited, code=exited status=127
Feb 25 22:02:52 stretch systemd[1]: Failed to start MariaDB 10.1.37 database server.
Feb 25 22:02:52 stretch systemd[1]: mariadb.service: Unit entered failed state.
Feb 25 22:02:52 stretch systemd[1]: mariadb.service: Failed with result 'exit-code'.

任何帮助都将受到欢迎...

我正在使用Debian 9，并且在1800Mo的内存中免费使用

这是期刊上所说的：

journalctl -xe

Feb 26 08:09:01 stretch CRON[16792]: pam_unix(cron:session): session opened for user root by (uid=0)
Feb 26 08:09:01 stretch CRON[16793]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Feb 26 08:09:01 stretch CRON[16792]: pam_unix(cron:session): session closed for user root
Feb 26 08:17:01 stretch CRON[16794]: pam_unix(cron:session): session opened for user root by (uid=0)
Feb 26 08:17:01 stretch CRON[16795]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 26 08:17:01 stretch CRON[16794]: pam_unix(cron:session): session closed for user root
Feb 26 08:25:23 stretch systemd[1]: Starting MariaDB 10.1.37 database server...
-- Subject: Unit mariadb.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit mariadb.service has begun starting up.
Feb 26 08:25:23 stretch systemd[1]: mariadb.service: Control process exited, code=exited status=127
Feb 26 08:25:23 stretch systemd[1]: Failed to start MariaDB 10.1.37 database server.
-- Subject: Unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit mariadb.service has failed.
-- 
-- The result is failed.
Feb 26 08:25:23 stretch systemd[1]: mariadb.service: Unit entered failed state.
Feb 26 08:25:23 stretch systemd[1]: mariadb.service: Failed with result 'exit-code'.

Answer 1

当升级到Debian Buster（从MariaDB 10.1到10.3）时，我也收到此错误。无论如何，自己运行val x: Long = Option(Long.unbox(timestamp())).getOrElse(1L) // Or, supposing opt is of type Option[java.lang.Long] val x: Long = opt.fold(ifEmpty = 1L)(Long.unbox)和mysqld都可以。尝试执行以下命令来立即重新启动systemd。另请参见https://unix.stackexchange.com/a/419375。

mysql_upgrade

如果您不执行此操作，则重新启动也可能会解决此问题。注释掉systemctl daemon-reexec中的ExecStartPre是不够的，因为其他/etc/systemd/system/mysql.service命令随后失败了（也有退出代码127，即“找不到命令”）。

Answer 2

在Process:下的ExecStartPre返回存在错误状态的

基于错误127，我怀疑/usr/bin/install不存在。

mysql无法重启

2 个答案: