mysql 服务无法 start/hangs 启动 - 超时（Ubuntu，MariaDB）
mysql service fails to start/hangs up - timeout (Ubuntu, MariaDB)
我用 Ubuntu 16.04、nginx、php7.0、MariaDB、nextcloud 和外部 DynDNS 使用这里的教程设置了我的第一个 Ubuntu 服务器：Install Nextcloud 9 on Ubuntu 16.04
一切正常，但自从我第二天重新启动服务器后，nextcloud 只显示一个空白页面。点开nginx、MariaDB和nextcloud的所有日志，发现mysql服务就是不启动。所以 运行 service mysql start 一切又恢复正常了（从服务器和其他工作站调用 nextcloud）。我只是想知道终端没有 "close" 线路。就像它仍在执行命令一样。大约 5 分钟后，行 "closes" 和以下消息出现：
"Job for mariadb.service failed because a timeout was exceeded. See
"systemctl status mariadb.service" and "journalctl -xe" for details."
然后客户端再次在 nextcloud 中得到一个空白页面。当我 运行 命令并立即关闭终端时，客户端也获得了访问权限，但 5 分钟后仍然失去了访问权限。
我尝试备份 nextcloud、sql 和 运行 apt-get purge --auto-remove mariadb-server。然后再次 运行 MariaDB 安装退出教程，导入备份 sql 而不是创建新备份。没有改变一切。
下一次尝试是 update-rc.d mysql defaults 和 update-rc.d mysql enable。但是重启后又是空白页。启动服务手册只能访问 5 分钟。
我也尝试了BUM - BootUpManager，但该服务似乎已启用。我看到您也可以手动启动服务。所以尝试使用 mysql 并惊喜：nextcloud 可用 5 分钟，而 BUM 只是挂断。
我也找到了 mariadb.com/kb/en/mariadb/starting-and-stopping-mariadb-automatically/ 但没有尝试任何东西，因为似乎还有其他问题。
root@s1:~# systemctl status mariadb.service:
\u25cf mariadb.service - MariaDB database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset:
Drop-In: /etc/systemd/system/mariadb.service.d
\u2514\u2500migrated-from-my.cnf-settings.conf
Active: failed (Result: timeout) since Di 2016-12-06 14:52:51 CET; 55s ago
Process: 3565 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WS
Process: 3415 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR
Process: 3409 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START
Process: 3405 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/ru
Main PID: 3565 (code=exited, status=0/SUCCESS)
Dez 06 14:52:48 s1 mysqld[3565]: 2016-12-06 14:52:48 3067387712 [Note] /usr/sbin
Dez 06 14:52:48 s1 mysqld[3565]: 2016-12-06 14:52:48 3067387712 [Note] Event Sch
Dez 06 14:52:48 s1 mysqld[3565]: 2016-12-06 14:52:48 2147785536 [Note] InnoDB: F
Dez 06 14:52:48 s1 mysqld[3565]: 2016-12-06 14:52:48 3067387712 [Note] InnoDB: S
Dez 06 14:52:49 s1 mysqld[3565]: 2016-12-06 14:52:49 3067387712 [Note] InnoDB: W
Dez 06 14:52:50 s1 mysqld[3565]: 2016-12-06 14:52:50 3067387712 [Note] InnoDB: S
Dez 06 14:52:50 s1 mysqld[3565]: 2016-12-06 14:52:50 3067387712 [Note] /usr/sbin
Dez 06 14:52:51 s1 systemd[1]: Failed to start MariaDB database server.
Dez 06 14:52:51 s1 systemd[1]: mariadb.service: Unit entered failed state.
Dez 06 14:52:51 s1 systemd[1]: mariadb.service: Failed with result 'timeout'.
root@s1:~# journalctl -xe:
Dez 06 14:52:48 s1 mysqld[3565]: 2016-12-06 14:52:48 3067387712 [Note] Event Scheduler: Purging the queue. 0 events
Dez 06 14:52:48 s1 mysqld[3565]: 2016-12-06 14:52:48 2147785536 [Note] InnoDB: FTS optimize thread exiting.
Dez 06 14:52:48 s1 mysqld[3565]: 2016-12-06 14:52:48 3067387712 [Note] InnoDB: Starting shutdown...
Dez 06 14:52:49 s1 mysqld[3565]: 2016-12-06 14:52:49 3067387712 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer po
Dez 06 14:52:50 s1 mysqld[3565]: 2016-12-06 14:52:50 3067387712 [Note] InnoDB: Shutdown completed; log sequence number 111890806
Dez 06 14:52:50 s1 mysqld[3565]: 2016-12-06 14:52:50 3067387712 [Note] /usr/sbin/mysqld: Shutdown complete
Dez 06 14:52:50 s1 audit[3648]: AVC apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profi
Dez 06 14:52:50 s1 kernel: audit: type=1400 audit(1481032370.973:29): apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
Dez 06 14:52:50 s1 audit[3565]: AVC apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profi
Dez 06 14:52:50 s1 kernel: audit: type=1400 audit(1481032370.973:30): apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
Dez 06 14:52:51 s1 systemd[1]: Failed to start MariaDB database server.
-- Subject: Unit mariadb.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mariadb.service has failed.
--
-- The result is failed.
Dez 06 14:52:51 s1 systemd[1]: mariadb.service: Unit entered failed state.
Dez 06 14:52:51 s1 systemd[1]: mariadb.service: Failed with result 'timeout'.
Dez 06 14:54:54 s1 x11vnc[2665]: 06/12/2016 14:54:54 cursor_noshape_updates_clients: 1
Dez 06 14:55:16 s1 ntpd[1244]: 46.4.1.155 local addr 192.168.178.50 -> <null>
Dez 06 14:57:30 s1 ntpd[1244]: 89.238.66.98 local addr 192.168.178.50 -> <null>
/ect/init.d 中的内容（如果有用）：
#!/bin/bash
#
### BEGIN INIT INFO
# Provides: mysql
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Should-Start: $network $named $time
# Should-Stop: $network $named $time
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start and stop the mysql database server daemon
# Description: Controls the main MariaDB database server daemon "mysqld"
# and its wrapper script "mysqld_safe".
### END INIT INFO
#
set -e
set -u
${DEBIAN_SCRIPT_DEBUG:+ set -v -x}
test -x /usr/sbin/mysqld || exit 0
. /lib/lsb/init-functions
SELF=$(cd $(dirname [=15=]); pwd -P)/$(basename [=15=])
CONF=/etc/mysql/my.cnf
MYADMIN="/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf"
# priority can be overriden and "-s" adds output to stderr
ERR_LOGGER="logger -p daemon.err -t /etc/init.d/mysql -i"
# Safeguard (relative paths, core dumps..)
cd /
umask 077
# mysqladmin likes to read /root/.my.cnf. This is usually not what I want
# as many admins e.g. only store a password without a username there and
# so break my scripts.
export HOME=/etc/mysql/
# Source default config file.
[ -r /etc/default/mariadb ] && . /etc/default/mariadb
## Fetch a particular option from mysql's invocation.
#
# Usage: void mysqld_get_param option
mysqld_get_param() {
/usr/sbin/mysqld --print-defaults \
| tr " " "\n" \
| grep -- "--" \
| tail -n 1 \
| cut -d= -f2
}
## Do some sanity checks before even trying to start mysqld.
sanity_checks() {
# check for config file
if [ ! -r /etc/mysql/my.cnf ]; then
log_warning_msg "[=15=]: WARNING: /etc/mysql/my.cnf cannot be read. See README.Debian.gz"
echo "WARNING: /etc/mysql/my.cnf cannot be read. See README.Debian.gz" | $ERR_LOGGER
fi
# check for diskspace shortage
datadir=`mysqld_get_param datadir`
if LC_ALL=C BLOCKSIZE= df --portability $datadir/. | tail -n 1 | awk '{ exit (>4096) }'; then
log_failure_msg "[=15=]: ERROR: The partition with $datadir is too full!"
echo "ERROR: The partition with $datadir is too full!" | $ERR_LOGGER
exit 1
fi
}
## Checks if there is a server running and if so if it is accessible.
#
# check_alive insists on a pingable server
# check_dead also fails if there is a lost mysqld in the process list
#
# Usage: boolean mysqld_status [check_alive|check_dead] [warn|nowarn]
mysqld_status () {
ping_output=`$MYADMIN ping 2>&1`; ping_alive=$(( ! $? ))
ps_alive=0
pidfile=`mysqld_get_param pid-file`
if [ -f "$pidfile" ] && ps `cat $pidfile` >/dev/null 2>&1; then ps_alive=1; fi
if [ "" = "check_alive" -a $ping_alive = 1 ] ||
[ "" = "check_dead" -a $ping_alive = 0 -a $ps_alive = 0 ]; then
return 0 # EXIT_SUCCESS
else
if [ "" = "warn" ]; then
echo -e "$ps_alive processes alive and '$MYADMIN ping' resulted in\n$ping_output\n" | $ERR_LOGGER -p daemon.debug
fi
return 1 # EXIT_FAILURE
fi
}
#
# main()
#
case "${1:-''}" in
'start')
sanity_checks;
# Start daemon
log_daemon_msg "Starting MariaDB database server" "mysqld"
if mysqld_status check_alive nowarn; then
log_progress_msg "already running"
log_end_msg 0
else
# Could be removed during boot
test -e /var/run/mysqld || install -m 755 -o mysql -g root -d /var/run/mysqld
# Start MariaDB!
/usr/bin/mysqld_safe "${@:2}" > /dev/null 2>&1 &
# 6s was reported in #352070 to be too little
for i in $(seq 1 "${MYSQLD_STARTUP_TIMEOUT:-60}"); do
sleep 1
if mysqld_status check_alive nowarn ; then break; fi
log_progress_msg "."
done
if mysqld_status check_alive warn; then
log_end_msg 0
# Now start mysqlcheck or whatever the admin wants.
output=$(/etc/mysql/debian-start)
[ -n "$output" ] && log_action_msg "$output"
else
log_end_msg 1
log_failure_msg "Please take a look at the syslog"
fi
fi
;;
'stop')
# * As a passwordless mysqladmin (e.g. via ~/.my.cnf) must be possible
# at least for cron, we can rely on it here, too. (although we have
# to specify it explicit as e.g. sudo environments points to the normal
# users home and not /root)
log_daemon_msg "Stopping MariaDB database server" "mysqld"
if ! mysqld_status check_dead nowarn; then
set +e
shutdown_out=`$MYADMIN shutdown 2>&1`; r=$?
set -e
if [ "$r" -ne 0 ]; then
log_end_msg 1
[ "$VERBOSE" != "no" ] && log_failure_msg "Error: $shutdown_out"
log_daemon_msg "Killing MariaDB database server by signal" "mysqld"
killall -15 mysqld
server_down=
for i in `seq 1 600`; do
sleep 1
if mysqld_status check_dead nowarn; then server_down=1; break; fi
done
if test -z "$server_down"; then killall -9 mysqld; fi
fi
fi
if ! mysqld_status check_dead warn; then
log_end_msg 1
log_failure_msg "Please stop MariaDB manually and read /usr/share/doc/mariadb-server-10.1/README.Debian.gz!"
exit -1
else
log_end_msg 0
fi
;;
'restart')
set +e; $SELF stop; set -e
$SELF start
;;
'reload'|'force-reload')
log_daemon_msg "Reloading MariaDB database server" "mysqld"
$MYADMIN reload
log_end_msg 0
;;
'status')
if mysqld_status check_alive nowarn; then
log_action_msg "$($MYADMIN version)"
else
log_action_msg "MariaDB is stopped."
exit 3
fi
;;
'bootstrap')
# Bootstrap the cluster, start the first node
# that initiates the cluster
log_daemon_msg "Bootstrapping the cluster" "mysqld"
$SELF start "${@:2}" --wsrep-new-cluster
;;
*)
echo "Usage: $SELF start|stop|restart|reload|force-reload|status|bootstrap"
exit 1
;;
esac
很遗憾，Google 帮不了我。我试着尽可能多地解释，也许这有助于你帮助我。非常感谢！
一个很长的问题……从没听说过 AppArmor，但这就是原因。答案 here 修复了它。不关心 apparmor ERROR 配置文件不存在。
sudo aa-status shows you what apparmor is doing; what actually has an
enforced policy, versus what's just set to complain.
sudo apt-get install apparmor-utils adds a few commands that make the
apparmor profiles easier to deal with, such as...
sudo aa-complain /usr/sbin/mysqld turns the profile from "enforce" to
complain. (aa-enforce turns it back.)
Once that's done, sudo service apparmor reload restarts apparmor, and
voila... sudo /etc/init.d/mysql start works, and the server stays up.
将 mysqld 移动到 "complain" 组对我来说还不够（MariaDB 10.1.21 运行 on Ubuntu 16.04）。
我必须完全禁用 mysqld 的 apparmor:
sudo ln -s /etc/apparmor.d/usr.sbin.mysqld /etc/apparmor.d/disable/
sudo service apparmor reload
sudo service mysql restart
现在一切正常。
仅供参考：
在我的例子中，Vincent 或 Lw Bi 的解决方案都没有完全奏效，我需要采取一些进一步的措施。
通过在 /etc/apparmor.d/disable/ 中放置 link 来禁用配置文件根本不起作用，我不知道为什么。
另一方面，将 MySQL 设置为投诉模式也没有立即起作用。
:~$ sudo aa-complain /usr/sbin/mysqld
设置 /usr/sbin/mysqld 为投诉模式。
ERROR: /etc/apparmor.d/usr.sbin.mysqld contains no profile
我需要添加以下行：
/usr/sbin/mysqld {
}
到/etc/apparmor.d/usr.sbin.mysqld，然后就可以设置成投诉模式成功了
运行 以下命令：
sudo dpkg --configure -a
sudo service mysql start
请注意，从 10.1.10 开始，MariaDB 使用 systemd 启动服务。如果您已尝试 MYSQLD_STARTUP_TIMEOUT 但没有奏效，则您可能正在使用此版本或更高版本。 /etc/init.d/mysql脚本不再使用，所以MYSQLD_STARTUP_TIMEOUT没有效果。
您需要找到您的 mariadb.service 文件。在我们的例子中，它不包含超时，因此使用了 MariaDB 默认值。只需添加：
TimeoutStartSec = 0
在[服务]部分，永不超时。
创建您自己的包含此配置文件是个好主意，这样它就不会被以后的重新安装覆盖。
在 ubuntu 18.04，您将在
中罚款此文件
/lib/systemd/system/mariadb.服务
将自己的文件放入
/etc/systemd/system/mariadb.service.d
记得在某处添加超时后 运行 systemctl daemon-reload（也许检查 /var/log/syslog 以查看重新加载是否成功），否则您的超时将被忽略。
这对我有用：
The correction didn't work for me.
$ sudo aa-complain /usr/sbin/mysqld Setting /usr/sbin/mysqld to
complain mode.
ERROR: /etc/apparmor.d/usr.sbin.mysqld contains no profile So I
disabled the profile (with aa-disable which seems to be equivalent to
plutocrat's solution)
$ sudo aa-disable /usr/sbin/mysqld Disabling /usr/sbin/mysqld. I
disabled mysqld-akonadi and mysqld-digikam as well.
An apparmor reload was not enough, so I had to reboot and mariadb
started perfectly well.
万一你被 this bug 咬住，解决方案作为错误报告中的建议给出（所有这些都必须以 root 身份完成，所以要么以 sudo -i 作为第零个命令或带有 sudo 前缀）：
echo "/usr/sbin/mysqld { }" > /etc/apparmor.d/usr.sbin.mysqld（带sudo的第二部分是... | sudo tee /etc/apparmor.d/usr.sbin.mysqld，谢谢@dvlcube）apparmor_parser -v -R /etc/apparmor.d/usr.sbin.mysqldsystemctl restart mariadb
背景
如果您之前安装了 MySQL，它会激活一个与 MariaDB 不兼容的 AppArmor 配置文件。 apt-get remove --purge 仅删除配置文件，但不会 deactivate/unload 它。只有手动卸载它才能让 MariaDB 不受 AppArmor 的阻碍。
最后一个选项对我有用（来自 quazgar）。我安装了 Ubuntu 18.10 和 MariaDB 10.3.13:
$ echo "/usr/sbin/mysqld { }" > /etc/apparmor.d/usr.sbin.mysqld
$ apparmor_parser -v -R /etc/apparmor.d/usr.sbin.mysqld
$ systemctl restart mariadb
我必须使用 "sudo su" 才能正常工作。
我也遇到了同样的问题。您需要在 mariadb 服务的 systemd 配置中设置适当的超时时间。下面为我解决了同样的问题。例如。当系统需要 SST 时，mariadb 服务可能需要很长时间才能启动，导致 systemd 超时。
如果您使用的是 systemd 228 或更早版本，那么您可以执行以下命令来设置无限超时。
sudo tee /etc/systemd/system/mariadb.service.d/timeoutsec.conf <<EOF
[Service]
TimeoutStartSec=0
TimeoutStopSec=0
EOF
sudo systemctl daemon-reload
我的解决方案是 运行 以下内容：
sudo killall mysqld
如果您仍然遇到此问题，运行 命令 ps -aux | grep 'mysql'。如果有什么出现，就把它也杀掉。
终于运行:
sudo systemctl restart mysql.service
我有同样的问题。 /etc/mysql/mariadb.conf.d/50-server.cnf 中链接到的证书文件丢失
这不见了：
/etc/mysql/ssl/server-key.pem
必须通过 ctrl+c 将其从另一个节点复制到 nano 中。使用 scp 复制时出现权限错误。
我用 Ubuntu 16.04、nginx、php7.0、MariaDB、nextcloud 和外部 DynDNS 使用这里的教程设置了我的第一个 Ubuntu 服务器：Install Nextcloud 9 on Ubuntu 16.04
一切正常，但自从我第二天重新启动服务器后，nextcloud 只显示一个空白页面。点开nginx、MariaDB和nextcloud的所有日志，发现mysql服务就是不启动。所以 运行 service mysql start 一切又恢复正常了（从服务器和其他工作站调用 nextcloud）。我只是想知道终端没有 "close" 线路。就像它仍在执行命令一样。大约 5 分钟后，行 "closes" 和以下消息出现：
"Job for mariadb.service failed because a timeout was exceeded. See "systemctl status mariadb.service" and "journalctl -xe" for details."
然后客户端再次在 nextcloud 中得到一个空白页面。当我 运行 命令并立即关闭终端时，客户端也获得了访问权限，但 5 分钟后仍然失去了访问权限。
我尝试备份 nextcloud、sql 和 运行 apt-get purge --auto-remove mariadb-server。然后再次 运行 MariaDB 安装退出教程，导入备份 sql 而不是创建新备份。没有改变一切。
下一次尝试是 update-rc.d mysql defaults 和 update-rc.d mysql enable。但是重启后又是空白页。启动服务手册只能访问 5 分钟。
我也尝试了BUM - BootUpManager，但该服务似乎已启用。我看到您也可以手动启动服务。所以尝试使用 mysql 并惊喜：nextcloud 可用 5 分钟，而 BUM 只是挂断。
我也找到了 mariadb.com/kb/en/mariadb/starting-and-stopping-mariadb-automatically/ 但没有尝试任何东西，因为似乎还有其他问题。
root@s1:~# systemctl status mariadb.service:
\u25cf mariadb.service - MariaDB database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset:
Drop-In: /etc/systemd/system/mariadb.service.d
\u2514\u2500migrated-from-my.cnf-settings.conf
Active: failed (Result: timeout) since Di 2016-12-06 14:52:51 CET; 55s ago
Process: 3565 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WS
Process: 3415 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR
Process: 3409 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START
Process: 3405 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/ru
Main PID: 3565 (code=exited, status=0/SUCCESS)
Dez 06 14:52:48 s1 mysqld[3565]: 2016-12-06 14:52:48 3067387712 [Note] /usr/sbin
Dez 06 14:52:48 s1 mysqld[3565]: 2016-12-06 14:52:48 3067387712 [Note] Event Sch
Dez 06 14:52:48 s1 mysqld[3565]: 2016-12-06 14:52:48 2147785536 [Note] InnoDB: F
Dez 06 14:52:48 s1 mysqld[3565]: 2016-12-06 14:52:48 3067387712 [Note] InnoDB: S
Dez 06 14:52:49 s1 mysqld[3565]: 2016-12-06 14:52:49 3067387712 [Note] InnoDB: W
Dez 06 14:52:50 s1 mysqld[3565]: 2016-12-06 14:52:50 3067387712 [Note] InnoDB: S
Dez 06 14:52:50 s1 mysqld[3565]: 2016-12-06 14:52:50 3067387712 [Note] /usr/sbin
Dez 06 14:52:51 s1 systemd[1]: Failed to start MariaDB database server.
Dez 06 14:52:51 s1 systemd[1]: mariadb.service: Unit entered failed state.
Dez 06 14:52:51 s1 systemd[1]: mariadb.service: Failed with result 'timeout'.
root@s1:~# journalctl -xe:
Dez 06 14:52:48 s1 mysqld[3565]: 2016-12-06 14:52:48 3067387712 [Note] Event Scheduler: Purging the queue. 0 events
Dez 06 14:52:48 s1 mysqld[3565]: 2016-12-06 14:52:48 2147785536 [Note] InnoDB: FTS optimize thread exiting.
Dez 06 14:52:48 s1 mysqld[3565]: 2016-12-06 14:52:48 3067387712 [Note] InnoDB: Starting shutdown...
Dez 06 14:52:49 s1 mysqld[3565]: 2016-12-06 14:52:49 3067387712 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer po
Dez 06 14:52:50 s1 mysqld[3565]: 2016-12-06 14:52:50 3067387712 [Note] InnoDB: Shutdown completed; log sequence number 111890806
Dez 06 14:52:50 s1 mysqld[3565]: 2016-12-06 14:52:50 3067387712 [Note] /usr/sbin/mysqld: Shutdown complete
Dez 06 14:52:50 s1 audit[3648]: AVC apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profi
Dez 06 14:52:50 s1 kernel: audit: type=1400 audit(1481032370.973:29): apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
Dez 06 14:52:50 s1 audit[3565]: AVC apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profi
Dez 06 14:52:50 s1 kernel: audit: type=1400 audit(1481032370.973:30): apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
Dez 06 14:52:51 s1 systemd[1]: Failed to start MariaDB database server.
-- Subject: Unit mariadb.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mariadb.service has failed.
--
-- The result is failed.
Dez 06 14:52:51 s1 systemd[1]: mariadb.service: Unit entered failed state.
Dez 06 14:52:51 s1 systemd[1]: mariadb.service: Failed with result 'timeout'.
Dez 06 14:54:54 s1 x11vnc[2665]: 06/12/2016 14:54:54 cursor_noshape_updates_clients: 1
Dez 06 14:55:16 s1 ntpd[1244]: 46.4.1.155 local addr 192.168.178.50 -> <null>
Dez 06 14:57:30 s1 ntpd[1244]: 89.238.66.98 local addr 192.168.178.50 -> <null>
/ect/init.d 中的内容（如果有用）：
#!/bin/bash
#
### BEGIN INIT INFO
# Provides: mysql
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Should-Start: $network $named $time
# Should-Stop: $network $named $time
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start and stop the mysql database server daemon
# Description: Controls the main MariaDB database server daemon "mysqld"
# and its wrapper script "mysqld_safe".
### END INIT INFO
#
set -e
set -u
${DEBIAN_SCRIPT_DEBUG:+ set -v -x}
test -x /usr/sbin/mysqld || exit 0
. /lib/lsb/init-functions
SELF=$(cd $(dirname [=15=]); pwd -P)/$(basename [=15=])
CONF=/etc/mysql/my.cnf
MYADMIN="/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf"
# priority can be overriden and "-s" adds output to stderr
ERR_LOGGER="logger -p daemon.err -t /etc/init.d/mysql -i"
# Safeguard (relative paths, core dumps..)
cd /
umask 077
# mysqladmin likes to read /root/.my.cnf. This is usually not what I want
# as many admins e.g. only store a password without a username there and
# so break my scripts.
export HOME=/etc/mysql/
# Source default config file.
[ -r /etc/default/mariadb ] && . /etc/default/mariadb
## Fetch a particular option from mysql's invocation.
#
# Usage: void mysqld_get_param option
mysqld_get_param() {
/usr/sbin/mysqld --print-defaults \
| tr " " "\n" \
| grep -- "--" \
| tail -n 1 \
| cut -d= -f2
}
## Do some sanity checks before even trying to start mysqld.
sanity_checks() {
# check for config file
if [ ! -r /etc/mysql/my.cnf ]; then
log_warning_msg "[=15=]: WARNING: /etc/mysql/my.cnf cannot be read. See README.Debian.gz"
echo "WARNING: /etc/mysql/my.cnf cannot be read. See README.Debian.gz" | $ERR_LOGGER
fi
# check for diskspace shortage
datadir=`mysqld_get_param datadir`
if LC_ALL=C BLOCKSIZE= df --portability $datadir/. | tail -n 1 | awk '{ exit (>4096) }'; then
log_failure_msg "[=15=]: ERROR: The partition with $datadir is too full!"
echo "ERROR: The partition with $datadir is too full!" | $ERR_LOGGER
exit 1
fi
}
## Checks if there is a server running and if so if it is accessible.
#
# check_alive insists on a pingable server
# check_dead also fails if there is a lost mysqld in the process list
#
# Usage: boolean mysqld_status [check_alive|check_dead] [warn|nowarn]
mysqld_status () {
ping_output=`$MYADMIN ping 2>&1`; ping_alive=$(( ! $? ))
ps_alive=0
pidfile=`mysqld_get_param pid-file`
if [ -f "$pidfile" ] && ps `cat $pidfile` >/dev/null 2>&1; then ps_alive=1; fi
if [ "" = "check_alive" -a $ping_alive = 1 ] ||
[ "" = "check_dead" -a $ping_alive = 0 -a $ps_alive = 0 ]; then
return 0 # EXIT_SUCCESS
else
if [ "" = "warn" ]; then
echo -e "$ps_alive processes alive and '$MYADMIN ping' resulted in\n$ping_output\n" | $ERR_LOGGER -p daemon.debug
fi
return 1 # EXIT_FAILURE
fi
}
#
# main()
#
case "${1:-''}" in
'start')
sanity_checks;
# Start daemon
log_daemon_msg "Starting MariaDB database server" "mysqld"
if mysqld_status check_alive nowarn; then
log_progress_msg "already running"
log_end_msg 0
else
# Could be removed during boot
test -e /var/run/mysqld || install -m 755 -o mysql -g root -d /var/run/mysqld
# Start MariaDB!
/usr/bin/mysqld_safe "${@:2}" > /dev/null 2>&1 &
# 6s was reported in #352070 to be too little
for i in $(seq 1 "${MYSQLD_STARTUP_TIMEOUT:-60}"); do
sleep 1
if mysqld_status check_alive nowarn ; then break; fi
log_progress_msg "."
done
if mysqld_status check_alive warn; then
log_end_msg 0
# Now start mysqlcheck or whatever the admin wants.
output=$(/etc/mysql/debian-start)
[ -n "$output" ] && log_action_msg "$output"
else
log_end_msg 1
log_failure_msg "Please take a look at the syslog"
fi
fi
;;
'stop')
# * As a passwordless mysqladmin (e.g. via ~/.my.cnf) must be possible
# at least for cron, we can rely on it here, too. (although we have
# to specify it explicit as e.g. sudo environments points to the normal
# users home and not /root)
log_daemon_msg "Stopping MariaDB database server" "mysqld"
if ! mysqld_status check_dead nowarn; then
set +e
shutdown_out=`$MYADMIN shutdown 2>&1`; r=$?
set -e
if [ "$r" -ne 0 ]; then
log_end_msg 1
[ "$VERBOSE" != "no" ] && log_failure_msg "Error: $shutdown_out"
log_daemon_msg "Killing MariaDB database server by signal" "mysqld"
killall -15 mysqld
server_down=
for i in `seq 1 600`; do
sleep 1
if mysqld_status check_dead nowarn; then server_down=1; break; fi
done
if test -z "$server_down"; then killall -9 mysqld; fi
fi
fi
if ! mysqld_status check_dead warn; then
log_end_msg 1
log_failure_msg "Please stop MariaDB manually and read /usr/share/doc/mariadb-server-10.1/README.Debian.gz!"
exit -1
else
log_end_msg 0
fi
;;
'restart')
set +e; $SELF stop; set -e
$SELF start
;;
'reload'|'force-reload')
log_daemon_msg "Reloading MariaDB database server" "mysqld"
$MYADMIN reload
log_end_msg 0
;;
'status')
if mysqld_status check_alive nowarn; then
log_action_msg "$($MYADMIN version)"
else
log_action_msg "MariaDB is stopped."
exit 3
fi
;;
'bootstrap')
# Bootstrap the cluster, start the first node
# that initiates the cluster
log_daemon_msg "Bootstrapping the cluster" "mysqld"
$SELF start "${@:2}" --wsrep-new-cluster
;;
*)
echo "Usage: $SELF start|stop|restart|reload|force-reload|status|bootstrap"
exit 1
;;
esac
很遗憾，Google 帮不了我。我试着尽可能多地解释，也许这有助于你帮助我。非常感谢！
一个很长的问题……从没听说过 AppArmor，但这就是原因。答案 here 修复了它。不关心 apparmor ERROR 配置文件不存在。
sudo aa-statusshows you what apparmor is doing; what actually has an enforced policy, versus what's just set to complain.
sudo apt-get install apparmor-utilsadds a few commands that make the apparmor profiles easier to deal with, such as...
sudo aa-complain /usr/sbin/mysqldturns the profile from "enforce" to complain. (aa-enforce turns it back.)Once that's done,
sudo service apparmor reloadrestarts apparmor, and voila...sudo /etc/init.d/mysql startworks, and the server stays up.
将 mysqld 移动到 "complain" 组对我来说还不够（MariaDB 10.1.21 运行 on Ubuntu 16.04）。 我必须完全禁用 mysqld 的 apparmor:
sudo ln -s /etc/apparmor.d/usr.sbin.mysqld /etc/apparmor.d/disable/
sudo service apparmor reload
sudo service mysql restart
现在一切正常。
仅供参考：
在我的例子中，Vincent 或 Lw Bi 的解决方案都没有完全奏效，我需要采取一些进一步的措施。
通过在 /etc/apparmor.d/disable/ 中放置 link 来禁用配置文件根本不起作用，我不知道为什么。
另一方面，将 MySQL 设置为投诉模式也没有立即起作用。
:~$ sudo aa-complain /usr/sbin/mysqld
设置 /usr/sbin/mysqld 为投诉模式。
ERROR: /etc/apparmor.d/usr.sbin.mysqld contains no profile
我需要添加以下行：
/usr/sbin/mysqld {
}
到/etc/apparmor.d/usr.sbin.mysqld，然后就可以设置成投诉模式成功了
运行 以下命令：
sudo dpkg --configure -a
sudo service mysql start
请注意，从 10.1.10 开始，MariaDB 使用 systemd 启动服务。如果您已尝试 MYSQLD_STARTUP_TIMEOUT 但没有奏效，则您可能正在使用此版本或更高版本。 /etc/init.d/mysql脚本不再使用，所以MYSQLD_STARTUP_TIMEOUT没有效果。
您需要找到您的 mariadb.service 文件。在我们的例子中，它不包含超时，因此使用了 MariaDB 默认值。只需添加：
TimeoutStartSec = 0
在[服务]部分，永不超时。
创建您自己的包含此配置文件是个好主意，这样它就不会被以后的重新安装覆盖。
在 ubuntu 18.04，您将在
中罚款此文件/lib/systemd/system/mariadb.服务
将自己的文件放入
/etc/systemd/system/mariadb.service.d
记得在某处添加超时后 运行 systemctl daemon-reload（也许检查 /var/log/syslog 以查看重新加载是否成功），否则您的超时将被忽略。
这对我有用：
The correction didn't work for me.
$ sudo aa-complain /usr/sbin/mysqld Setting /usr/sbin/mysqld to complain mode.
ERROR: /etc/apparmor.d/usr.sbin.mysqld contains no profile So I disabled the profile (with aa-disable which seems to be equivalent to plutocrat's solution)
$ sudo aa-disable /usr/sbin/mysqld Disabling /usr/sbin/mysqld. I disabled mysqld-akonadi and mysqld-digikam as well.
An apparmor reload was not enough, so I had to reboot and mariadb started perfectly well.
万一你被 this bug 咬住，解决方案作为错误报告中的建议给出（所有这些都必须以 root 身份完成，所以要么以 sudo -i 作为第零个命令或带有 sudo 前缀）：
echo "/usr/sbin/mysqld { }" > /etc/apparmor.d/usr.sbin.mysqld（带sudo的第二部分是... | sudo tee /etc/apparmor.d/usr.sbin.mysqld，谢谢@dvlcube）apparmor_parser -v -R /etc/apparmor.d/usr.sbin.mysqldsystemctl restart mariadb
背景
如果您之前安装了 MySQL，它会激活一个与 MariaDB 不兼容的 AppArmor 配置文件。 apt-get remove --purge 仅删除配置文件，但不会 deactivate/unload 它。只有手动卸载它才能让 MariaDB 不受 AppArmor 的阻碍。
最后一个选项对我有用（来自 quazgar）。我安装了 Ubuntu 18.10 和 MariaDB 10.3.13:
$ echo "/usr/sbin/mysqld { }" > /etc/apparmor.d/usr.sbin.mysqld
$ apparmor_parser -v -R /etc/apparmor.d/usr.sbin.mysqld
$ systemctl restart mariadb
我必须使用 "sudo su" 才能正常工作。
我也遇到了同样的问题。您需要在 mariadb 服务的 systemd 配置中设置适当的超时时间。下面为我解决了同样的问题。例如。当系统需要 SST 时，mariadb 服务可能需要很长时间才能启动，导致 systemd 超时。
如果您使用的是 systemd 228 或更早版本，那么您可以执行以下命令来设置无限超时。
sudo tee /etc/systemd/system/mariadb.service.d/timeoutsec.conf <<EOF
[Service]
TimeoutStartSec=0
TimeoutStopSec=0
EOF
sudo systemctl daemon-reload
我的解决方案是 运行 以下内容：
sudo killall mysqld
如果您仍然遇到此问题，运行 命令 ps -aux | grep 'mysql'。如果有什么出现，就把它也杀掉。
终于运行:
sudo systemctl restart mysql.service
我有同样的问题。 /etc/mysql/mariadb.conf.d/50-server.cnf 中链接到的证书文件丢失 这不见了： /etc/mysql/ssl/server-key.pem
必须通过 ctrl+c 将其从另一个节点复制到 nano 中。使用 scp 复制时出现权限错误。