我昨天用Ubuntu 16.04，nginx，php7.0，MariaDB，nextcloud和外部DynDNS设置了我的第一个Ubuntu服务器（使用本教程：https://www.rosehosting.com/blog/install-nextcloud-on-ubuntu-16-04/）。一切正常，但自从我今天重新启动服务器后，nextcloud只显示了一个空白页面。点击nginx，MariaDB和nextcloud的所有日志后，我发现mysql服务无法启动。所以运行service mysql start，一切正常（从服务器和其他工作站调用nextcloud）。我只是想知道终端没有“关闭”线路。就像它仍然在执行命令。大约5分钟后，线路“关闭”并显示消息
“mariadb.service的作业失败，因为超时超时。有关详细信息，请参阅”systemctl status mariadb.service“和”journalctl -xe“。
出现（见下文）。然后客户再次在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，但服务似乎是anabled。我看到你也可以手动启动服务。所以尝试用mysql和惊喜：nextcloud可用5分钟，而BUM只是挂起：D
我发现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>
/etc/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 $0); pwd -P)/$(basename $0)
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 -- "--$1" \
| 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 "$0: 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 ($4>4096) }'; then
log_failure_msg "$0: 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 [ "$1" = "check_alive" -a $ping_alive = 1 ] ||
[ "$1" = "check_dead" -a $ping_alive = 0 -a $ps_alive = 0 ]; then
return 0 # EXIT_SUCCESS
else
if [ "$2" = "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
不幸的是谷歌无法帮助我。我尽可能多地解释这可能会帮助你帮助我。非常感谢！
如果您被this bug咬了，解决方案将作为bug报告中的建议：
echo "/usr/sbin/mysqld { }" > /etc/apparmor.d/usr.sbin.mysqldapparmor_parser -v -R /etc/apparmor.d/usr.sbin.mysqldsystemctl restart mariadb如果您之前安装了MySQL，则会激活与MariaDB不兼容的AppArmor配置文件。 apt-get remove --purge仅删除配置文件，但不会停用/卸载它。只有手动卸载它才能让MariaDB不受AppArmor的干扰。
这最后一个选项对我有用（来自quazgar）。我安装了与MariaDB 10.3.13一起安装的Ubuntu 18.10：
$ 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”来工作。
将mysqld移动到“抱怨”组是不够的（在Ubuntu 16.04上运行的MariaDB 10.1.21）。我必须完全禁用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/中放置链接来禁用配置文件根本不起作用，我不知道为什么。
另一方面，将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，然后我可以成功地将它设置为抱怨模式。
无所事事的长期问题......从来没有听说过AppArmor，但它是reasen。答案here修复它。不关心apparmor的ERROR配置文件不存在。
sudo aa-status向您展示了apparmor正在做什么;什么实际上有一个强制执行的政策，而不是什么只是抱怨。
sudo apt-get install apparmor-utils添加了一些命令，使apparmor配置文件更容易处理，例如...
sudo aa-complain /usr/sbin/mysqld将配置文件从“强制执行”变为抱怨。 （aa-enforce将其退回。）一旦完成，
sudo service apparmor reload重启apparmor，瞧...sudo /etc/init.d/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上，你将在这个文件中使用
/礼拜/system的/system/Maria dB.service
把你自己的文件放进去
/etc/system的/system/Maria dB.service.的
记得在某处添加超时后运行systemctl守护进程重新加载（也可以检查/ var / log / syslog以查看重载是否成功），否则将忽略超时。
运行以下命令：
sudo dpkg --configure -a
sudo service mysql start
这对我有用：
纠正对我不起作用。
$ sudo aa-complain / usr / sbin / mysqld将/ usr / sbin / mysqld设置为抱怨模式。
错误：/etc/apparmor.d/usr.sbin.mysqld不包含配置文件所以我禁用了配置文件（使用aa-disable，这似乎相当于plutocrat的解决方案）
$ sudo aa-disable / usr / sbin / mysqld禁用/ usr / sbin / mysqld。我也禁用了mysqld-akonadi和mysqld-digikam。
apparmor重新加载是不够的，所以我不得不重启并且mariadb开始非常好。