Setting up mariadb-server-10.1 (10.1.16+maria-1~jessie) … Job for mariadb.service failed. See ‘systemctl status mariadb.service’ and ‘journalctl -xn’ for details. invoke-rc.d: initscript mysql, action “start” failed. dpkg: error processing package mariadb-server-10.1 (–configure) subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of mariadb-server mariadb-server depends on mariadb-server-10.1 (= 10.1.16+maria-1~jessie); however Package mariadb-server-10.1 is not configured yet.
dpkg: error processing package mariadb-server (–configure) dependency problems – leaving unconfigured Errors were encountered while processing mariadb-server-10.1 mariadb-server E: Sub-process /usr/bin/dpkg returned an error code (1)
galera_new_cluster galera_recovery service mysql bootstrap service mysql start systemctl mariadb start
所有这些命令都给出以下错误
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 给出以下信息
WSREP: Failed to recover position: ‘2016-07-22 12:09:58 139742628583680 [Note] /usr/sbin/mysqld (mysqld 10.1.16-MariaDB-1~xenial) starting as process 10182 …’
升级后崩溃了……在 Debian 上，一个始终保持最新的系统
Setting up mariadb-server-10.1 (10.1.16+maria-1~jessie) …
Job for mariadb.service failed. See ‘systemctl status mariadb.service’ and ‘journalctl -xn’ for details.
invoke-rc.d: initscript mysql, action “start” failed.
dpkg: error processing package mariadb-server-10.1 (–configure)
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of mariadb-server
mariadb-server depends on mariadb-server-10.1 (= 10.1.16+maria-1~jessie); however
Package mariadb-server-10.1 is not configured yet.
dpkg: error processing package mariadb-server (–configure)
dependency problems – leaving unconfigured
Errors were encountered while processing
mariadb-server-10.1
mariadb-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
————————-
systemctl status mariadb.service
● mariadb.service – MariaDB database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: failed (Result: exit-code) since Thu 2016-07-21 07:44:01 UTC; 3min 11s ago
Process: 4441 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=227/NO_NEW _PRIVILEGES)
Process: 4438 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Process: 4279 ExecStartPre=/bin/sh -c VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_P OSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 4275 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Main PID: 4441 (code=exited, status=227/NO_NEW_PRIVILEGES)
Jul 21 07:44:01 systemd[4441]: Failed at step NO_NEW_PRIVILEGES spawning /usr/sbin/mysqld: …ment
Jul 21 07:44:01 : mariadb.service: main process exited, code=exited, status=227/N…EGES
Jul 21 07:44:01: Failed to start MariaDB database server.
Jul 21 07:44:01: Unit mariadb.service entered failed state.
请参阅 https://mariadb.com/kb/en/mariadb/upgrade-10116maria-1jessie-broke-system/
它将在 10.1.17 中修复
你好，
2016-07-22 15:12:27 140310078306560 [Note] WSREP: Read nil XID from storage engines, skipping position init
2016-07-22 15:12:27 140310078306560 [Note] WSREP: wsrep_load(): loading provider library ‘none’
2016-07-22 15:12:27 140310078306560 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-07-22 15:12:27 140310078306560 [Note] InnoDB: The InnoDB memory heap is disabled
2016-07-22 15:12:27 140310078306560 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-07-22 15:12:27 140310078306560 [Note] InnoDB: Memory barrier is not used
2016-07-22 15:12:27 140310078306560 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-07-22 15:12:27 140310078306560 [Note] InnoDB: Using Linux native AIO
2016-07-22 15:12:27 140310078306560 [Note] InnoDB: Using SSE crc32 instructions
2016-07-22 15:12:27 140310078306560 [Note] InnoDB: Initializing buffer pool, size = 185.0M
2016-07-22 15:12:27 140310078306560 [Note] InnoDB: Completed initialization of buffer pool
2016-07-22 15:12:27 140310078306560 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2016-07-22 15:12:27 140310078306560 [Note] InnoDB: Setting file ./ibdata1 size to 100 MB
2016-07-22 15:12:27 140310078306560 [Note] InnoDB: Database physically writes the file full: wait…
InnoDB: Progress in MB: 100
2016-07-22 15:12:27 140310078306560 [Note] InnoDB: Setting log file ./ib_logfile101 size to 64 MB
2016-07-22 15:12:27 140310078306560 [Note] InnoDB: Setting log file ./ib_logfile1 size to 64 MB
2016-07-22 15:12:28 140310078306560 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2016-07-22 15:12:28 140310078306560 [Warning] InnoDB: New log files created, LSN=45883
2016-07-22 15:12:28 140310078306560 [Note] InnoDB: Doublewrite buffer not found: creating new
2016-07-22 15:12:28 140310078306560 [Note] InnoDB: Doublewrite buffer created
2016-07-22 15:12:28 140310078306560 [Note] InnoDB: 128 rollback segment(s) are active.
2016-07-22 15:12:28 140310078306560 [Warning] InnoDB: Creating foreign key constraint system tables.
2016-07-22 15:12:28 140310078306560 [Note] InnoDB: Foreign key constraint system tables created
2016-07-22 15:12:28 140310078306560 [Note] InnoDB: Creating tablespace and datafile system tables.
2016-07-22 15:12:28 140310078306560 [Note] InnoDB: Tablespace and datafile system tables created.
2016-07-22 15:12:28 140310078306560 [Note] InnoDB: Waiting for purge to start
2016-07-22 15:12:28 140310078306560 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.30-76.3 started; log sequence number 0
2016-07-22 15:12:31 140309417658112 [Note] InnoDB: Dumping buffer pool(s) not yet started
2016-07-22 15:12:31 140007385413888 [Note] WSREP: Read nil XID from storage engines, skipping position init
2016-07-22 15:12:31 140007385413888 [Note] WSREP: wsrep_load(): loading provider library ‘none’
2016-07-22 15:12:31 140007385413888 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-07-22 15:12:31 140007385413888 [Note] InnoDB: The InnoDB memory heap is disabled
2016-07-22 15:12:31 140007385413888 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-07-22 15:12:31 140007385413888 [Note] InnoDB: Memory barrier is not used
2016-07-22 15:12:31 140007385413888 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-07-22 15:12:31 140007385413888 [Note] InnoDB: Using Linux native AIO
2016-07-22 15:12:31 140007385413888 [Note] InnoDB: Using SSE crc32 instructions
2016-07-22 15:12:31 140007385413888 [Note] InnoDB: Initializing buffer pool, size = 185.0M
2016-07-22 15:12:31 140007385413888 [Note] InnoDB: Completed initialization of buffer pool
2016-07-22 15:12:31 140007385413888 [Note] InnoDB: Highest supported file format is Barracuda.
2016-07-22 15:12:31 140007385413888 [Note] InnoDB: 128 rollback segment(s) are active.
2016-07-22 15:12:31 140007385413888 [Note] InnoDB: Waiting for purge to start
2016-07-22 15:12:31 140007385413888 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.30-76.3 started; log sequence number 1616799
2016-07-22 15:12:31 140006727321344 [Note] InnoDB: Dumping buffer pool(s) not yet started
2016-07-22 15:12:35 140187125606656 [Note] WSREP: Read nil XID from storage engines, skipping position init
2016-07-22 15:12:35 140187125606656 [Note] WSREP: wsrep_load(): loading provider library ‘none’
2016-07-22 15:12:35 140187125606656 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-07-22 15:12:35 140187125606656 [Note] InnoDB: The InnoDB memory heap is disabled
2016-07-22 15:12:35 140187125606656 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-07-22 15:12:35 140187125606656 [Note] InnoDB: Memory barrier is not used
2016-07-22 15:12:35 140187125606656 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-07-22 15:12:35 140187125606656 [Note] InnoDB: Using Linux native AIO
2016-07-22 15:12:35 140187125606656 [Note] InnoDB: Using SSE crc32 instructions
2016-07-22 15:12:35 140187125606656 [Note] InnoDB: Initializing buffer pool, size = 185.0M
2016-07-22 15:12:35 140187125606656 [Note] InnoDB: Completed initialization of buffer pool
2016-07-22 15:12:35 140187125606656 [Note] InnoDB: Highest supported file format is Barracuda.
2016-07-22 15:12:35 140187125606656 [Note] InnoDB: 128 rollback segment(s) are active.
2016-07-22 15:12:35 140187125606656 [Note] InnoDB: Waiting for purge to start
2016-07-22 15:12:35 140187125606656 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.30-76.3 started; log sequence number 1616809
2016-07-22 15:12:35 140186465830656 [Note] InnoDB: Dumping buffer pool(s) not yet started
ERROR: 1049 Unknown database ‘test’
2016-07-22 15:12:35 140187125606656 [ERROR] Aborting
2016-07-22 15:12:39 139869885348096 [Note] WSREP: Read nil XID from storage engines, skipping position init
2016-07-22 15:12:39 139869885348096 [Note] WSREP: wsrep_load(): loading provider library ‘none’
2016-07-22 15:12:39 139869885348096 [Warning] option ‘innodb-buffer-pool-instances’: signed value -1 adjusted to 0
2016-07-22 15:12:39 139869885348096 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-07-22 15:12:39 139869885348096 [Note] InnoDB: The InnoDB memory heap is disabled
2016-07-22 15:12:39 139869885348096 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-07-22 15:12:39 139869885348096 [Note] InnoDB: Memory barrier is not used
2016-07-22 15:12:39 139869885348096 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-07-22 15:12:39 139869885348096 [Note] InnoDB: Using Linux native AIO
2016-07-22 15:12:39 139869885348096 [Note] InnoDB: Using SSE crc32 instructions
2016-07-22 15:12:39 139869885348096 [Note] InnoDB: Initializing buffer pool, size = 185.0M
2016-07-22 15:12:39 139869885348096 [Note] InnoDB: Completed initialization of buffer pool
2016-07-22 15:12:39 139869885348096 [Note] InnoDB: Highest supported file format is Barracuda.
2016-07-22 15:12:39 139869885348096 [Note] InnoDB: 128 rollback segment(s) are active.
2016-07-22 15:12:39 139869885348096 [Note] InnoDB: Waiting for purge to start
2016-07-22 15:12:39 139869885348096 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.30-76.3 started; log sequence number 1616819
2016-07-22 15:12:39 139869885348096 [Note] Plugin ‘FEEDBACK’ is disabled.
2016-07-22 15:12:39 139869225453312 [Note] InnoDB: Dumping buffer pool(s) not yet started
2016-07-22 15:12:43 140629636262144 [Warning] option ‘innodb-buffer-pool-instances’: signed value -1 adjusted to 0
2016-07-22 15:12:43 140629636262144 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-07-22 15:12:43 140629636262144 [Note] InnoDB: The InnoDB memory heap is disabled
2016-07-22 15:12:43 140629636262144 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-07-22 15:12:43 140629636262144 [Note] InnoDB: Memory barrier is not used
2016-07-22 15:12:43 140629636262144 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-07-22 15:12:43 140629636262144 [Note] InnoDB: Using Linux native AIO
2016-07-22 15:12:43 140629636262144 [Note] InnoDB: Using SSE crc32 instructions
2016-07-22 15:12:43 140629636262144 [Note] InnoDB: Initializing buffer pool, size = 185.0M
2016-07-22 15:12:43 140629636262144 [Note] InnoDB: Completed initialization of buffer pool
2016-07-22 15:12:43 140629636262144 [Note] InnoDB: Highest supported file format is Barracuda.
2016-07-22 15:12:43 140629636262144 [Note] InnoDB: 128 rollback segment(s) are active.
2016-07-22 15:12:43 140629636262144 [Note] InnoDB: Waiting for purge to start
2016-07-22 15:12:43 140629636262144 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.30-76.3 started; log sequence number 1616829
2016-07-22 15:12:43 140629636262144 [Warning] InnoDB: Skipping buffer pool dump/restore during wsrep recovery.
2016-07-22 15:12:43 140629636262144 [Note] Plugin ‘FEEDBACK’ is disabled.
2016-07-22 15:12:43 140629636262144 [Note] Server socket created on IP: ‘::’.
2016-07-22 15:12:43 140629636262144 [Note] WSREP: Recovered position: 00000000-0000-0000-0000-000000000000:-1
当使用 clustercontrol 作为 galera 集群安装时，mariadb 无法启动
这次升级彻底破坏了我在 Ubuntu 16.04 上（完全最新）的整个集群。
现在擦除一切并尝试从全新安装重新初始化后，任何服务器上的任何启动脚本都无法工作。
唯一能让集群运行的方法是执行
sudo -u mysql mysqld –wsrep-cluster-address=’gcomm://’
在第一台服务器上，然后以同样的方式手动启动所有其他节点，只是带有完整的集群地址。以下任何命令在第一台节点或加入节点上都无法工作
galera_new_cluster
galera_recovery
service mysql bootstrap
service mysql start
systemctl mariadb start
所有这些命令都给出以下错误
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 给出以下信息
WSREP: Failed to recover position: ‘2016-07-22 12:09:58 139742628583680 [Note] /usr/sbin/mysqld (mysqld 10.1.16-MariaDB-1~xenial) starting as process 10182 …’
我在 DBA Stack Exchange 上提出了一个问题：http://dba.stackexchange.com/q/144691/23088
此问题的修复（最初由 MDEV-10396 报告）已排入下一个 10.1 版本 (10.1.17)。
请务必将任何问题报告到 MariaDB 错误跟踪系统 https://jira.mariadb.org – 开发人员不会主动查看博客评论。
谢谢！
谢谢！我后来找到了 JIRA 并提交了一个问题。我先在 GitHub 上找，然后在查看更新日志后才找到 JIRA。下次我会确保先去那里。
https://jira.mariadb.org/browse/MDEV-10420
令人非常担忧的是，此版本可能是连续两次升级失败。
同样令人担忧的是，此站点上关于 10.1.15 的所有文档都声称它从未发布过，而实际上它已正式发布并推送到镜像，并给那些安装它然后不得不手动回滚到 10.1.14（我在服务器上 apt-mark “held”）的人（比如我）造成了各种严重问题。
MariaDB 基金会怎么了？
在 CentOS 7 下也有同样的问题：/
我无法在页面上下载 MariaDB 10.1.16，显示 404 Not Found，请检查下载文件。
下载链接没问题 – 如果是镜像报告错误，请尝试选择其他镜像。