Question

启动mysql超时。我不确定为什么。

我按照建议浏览了日志文件，只是得知它已超时，但不知道为什么。我什至尝试重新安装灯组，但这是相同的结果。

toor@linux:~$ sudo /etc/init.d/mysql start
[....] Starting mysql (via systemctl): mysql.service
Job for mariadb.service failed because a timeout was exceeded.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
failed!


toor@linux:~$ 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: timeout) since Thu 2019-03-28 18:52:25 IST; 1min 13s ago
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 14867 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, stat
  Process: 14790 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`
  Process: 14785 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCC
  Process: 14783 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCE
 Main PID: 14867 (code=exited, status=1/FAILURE)
   Status: "MariaDB server is down"
lines 1-11/11 (END)

我尝试粘贴journalctl -xe的结果，但由于其中包含大量代码，因此无法提交。这就是output。

Answer 1

sudo aa-status 会向您显示保镖正在做什么。

sudo apt-get install apparmor-utils 添加了一些使apparmor配置文件更容易的命令。

sudo aa-complain / usr / sbin / mysqld 将配置文件从“强制”转为投诉。

重新加载sudo服务apparmor ，然后重启apparmor，然后... sudo /etc/init.d/mysql start 重新启动服务器。

mysql服务启动时超时

1 个答案: