MariaDB 10.1.16 now available
The MariaDB project is pleased to announce the immediate availability of MariaDB 10.1.16. See the release notes and changelog for details on this release.
Release Notes Changelog What is MariaDB 10.1?
MariaDB APT and YUM Repository Configuration Generator
Thanks, and enjoy MariaDB!
Broke after upgrade…. on Debian, on an always up to date system
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.
See https://mariadb.com/kb/en/mariadb/upgrade-10116maria-1jessie-broke-system/
It will be fixed in 10.1.17
Hi,
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:28 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
mariadb would not start when installing as a galera cluster using clustercontrol
This upgrade completely hosed my entire cluster on Ubuntu 16.04 (completely up-to-date).
And now after wiping everything and trying to reinitialize from a clean install, none of the startup scripts will work on any server.
The only way I can get the cluster running is by executing:
sudo -u mysql mysqld –wsrep-cluster-address=’gcomm://’
On the first server, and then manually start every other node the same way except with the full cluster address. None of the following work on either the first or joining nodes:
galera_new_cluster
galera_recovery
service mysql bootstrap
service mysql start
systemctl mariadb start
Every single one of those gives the error:
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 gives the following info:
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 …’
I’ve opened a question on DBA Stack Exchange: http://dba.stackexchange.com/q/144691/23088
The fix for this issue, originally reported by MDEV-10396, has been queued for next 10.1 release (10.1.17).
Please be sure to report any issues to the MariaDB bug tracker at https://jira.mariadb.org – the devs don’t actively check blog comments.
Thanks!
Thanks! I found the JIRA later and did open a ticket. I looked on GitHub first and only found JIRA after searching the changelogs. I’ll be sure to go there first next time.
https://jira.mariadb.org/browse/MDEV-10420
Very concerning that this release may mark two botched upgrades in a row.
Also worrying that all of the documentation on this site relative to 10.1.15 claims that it was never released when in fact it was formally released and pushed to mirrors, and caused all kinds of severe issues for those (like me) that installed it and then had to manually roll back to 10.1.14 which I have apt-mark “held” on my servers.
What’s up MariaDB Foundation?
Same problem under CentOS 7 :/
I cannot download MariaDB 10.1.16 on page show 404 Not Found please check file download.
The download link is fine – if it’s a mirror reporting an error, try choosing another mirror.