[MDEV-10528] Upgrade to 10.1.16 fails in Ubuntu 16.04 Created: 2016-08-10  Updated: 2016-08-23  Resolved: 2016-08-23

Status: Closed
Project: MariaDB Server
Component/s: Platform Debian
Affects Version/s: 10.1.16
Fix Version/s: 10.1.17

Type: Bug Priority: Critical
Reporter: Jorge Ferrando Assignee: Nirbhay Choubey (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Environment:

Ubuntu 16.04. Cluster of 3 nodes


Issue Links:
Duplicate
is duplicated by MDEV-10396 MariaDB does not restart after upgrad... Closed

 Description   

When I try to upgrade to 10.1.16 it fails with this error and mysql doesn't start:

  1. apt-get upgrade
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    Calculating upgrade... Done
    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    2 not fully installed or removed.
    After this operation, 0 B of additional disk space will be used.
    Do you want to continue? [Y/n]
    Setting up mariadb-server-10.1 (10.1.16+maria-1~xenial) ...
    Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" 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~xenial); however:
    Package mariadb-server-10.1 is not configured yet.

dpkg: error processing package mariadb-server (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Errors were encountered while processing:
mariadb-server-10.1
mariadb-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

This is the output in /var/log/mysql/error.log:

2016-08-10 11:03:19 140200122566912 [Note] WSREP: Read nil XID from storage engines, skipping position init
2016-08-10 11:03:19 140200122566912 [Note] WSREP: wsrep_load(): loading provider library 'none'
2016-08-10 11:03:19 140200122566912 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-08-10 11:03:19 140200122566912 [Note] InnoDB: The InnoDB memory heap is disabled
2016-08-10 11:03:19 140200122566912 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-08-10 11:03:19 140200122566912 [Note] InnoDB: Memory barrier is not used
2016-08-10 11:03:19 140200122566912 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-08-10 11:03:19 140200122566912 [Note] InnoDB: Using Linux native AIO
2016-08-10 11:03:19 140200122566912 [Note] InnoDB: Using generic crc32 instructions
2016-08-10 11:03:19 140200122566912 [Note] InnoDB: Initializing buffer pool, size = 2.0G
2016-08-10 11:03:19 140200122566912 [Note] InnoDB: Completed initialization of buffer pool
2016-08-10 11:03:19 140200122566912 [Note] InnoDB: Highest supported file format is Barracuda.
2016-08-10 11:03:36 140200122566912 [Note] InnoDB: 128 rollback segment(s) are active.
2016-08-10 11:03:36 140200122566912 [Note] InnoDB: Waiting for purge to start
2016-08-10 11:03:36 140200122566912 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.30-76.3 started; log sequence number 249787949691
2016-08-10 11:03:36 140197240997632 [Note] InnoDB: Dumping buffer pool(s) not yet started
2016-08-10 11:03:39 140163580336384 [Note] WSREP: Read nil XID from storage engines, skipping position init
2016-08-10 11:03:39 140163580336384 [Note] WSREP: wsrep_load(): loading provider library 'none'
2016-08-10 11:03:39 140163580336384 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-08-10 11:03:39 140163580336384 [Note] InnoDB: The InnoDB memory heap is disabled
2016-08-10 11:03:39 140163580336384 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-08-10 11:03:39 140163580336384 [Note] InnoDB: Memory barrier is not used
2016-08-10 11:03:39 140163580336384 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-08-10 11:03:39 140163580336384 [Note] InnoDB: Using Linux native AIO
2016-08-10 11:03:39 140163580336384 [Note] InnoDB: Using generic crc32 instructions
2016-08-10 11:03:39 140163580336384 [Note] InnoDB: Initializing buffer pool, size = 2.0G
2016-08-10 11:03:39 140163580336384 [Note] InnoDB: Completed initialization of buffer pool
2016-08-10 11:03:39 140163580336384 [Note] InnoDB: Highest supported file format is Barracuda.
2016-08-10 11:03:58 140163580336384 [Note] InnoDB: 128 rollback segment(s) are active.
2016-08-10 11:03:58 140163580336384 [Note] InnoDB: Waiting for purge to start
2016-08-10 11:03:58 140163580336384 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.30-76.3 started; log sequence number 249787949701
2016-08-10 11:03:58 140160696026880 [Note] InnoDB: Dumping buffer pool(s) not yet started
2016-08-10 11:04:02 140239163091200 [Note] WSREP: Read nil XID from storage engines, skipping position init
2016-08-10 11:04:02 140239163091200 [Note] WSREP: wsrep_load(): loading provider library 'none'
2016-08-10 11:04:02 140239163091200 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-08-10 11:04:02 140239163091200 [Note] InnoDB: The InnoDB memory heap is disabled
2016-08-10 11:04:02 140239163091200 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-08-10 11:04:02 140239163091200 [Note] InnoDB: Memory barrier is not used
2016-08-10 11:04:02 140239163091200 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-08-10 11:04:02 140239163091200 [Note] InnoDB: Using Linux native AIO
2016-08-10 11:04:02 140239163091200 [Note] InnoDB: Using generic crc32 instructions
2016-08-10 11:04:02 140239163091200 [Note] InnoDB: Initializing buffer pool, size = 2.0G
2016-08-10 11:04:02 140239163091200 [Note] InnoDB: Completed initialization of buffer pool
2016-08-10 11:04:02 140239163091200 [Note] InnoDB: Highest supported file format is Barracuda.
2016-08-10 11:04:20 140239163091200 [Note] InnoDB: 128 rollback segment(s) are active.
2016-08-10 11:04:20 140239163091200 [Note] InnoDB: Waiting for purge to start
2016-08-10 11:04:20 140239163091200 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.30-76.3 started; log sequence number 249787949711
2016-08-10 11:04:20 140236281579264 [Note] InnoDB: Dumping buffer pool(s) not yet started
2016-08-10 11:04:23 140637551601920 [Note] WSREP: Read nil XID from storage engines, skipping position init
2016-08-10 11:04:23 140637551601920 [Note] WSREP: wsrep_load(): loading provider library 'none'
2016-08-10 11:04:24 140637551601920 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-08-10 11:04:24 140637551601920 [Note] InnoDB: The InnoDB memory heap is disabled
2016-08-10 11:04:24 140637551601920 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-08-10 11:04:24 140637551601920 [Note] InnoDB: Memory barrier is not used
2016-08-10 11:04:24 140637551601920 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-08-10 11:04:24 140637551601920 [Note] InnoDB: Using Linux native AIO
2016-08-10 11:04:24 140637551601920 [Note] InnoDB: Using generic crc32 instructions
2016-08-10 11:04:24 140637551601920 [Note] InnoDB: Initializing buffer pool, size = 2.0G
2016-08-10 11:04:24 140637551601920 [Note] InnoDB: Completed initialization of buffer pool
2016-08-10 11:04:24 140637551601920 [Note] InnoDB: Highest supported file format is Barracuda.
2016-08-10 11:04:40 140637551601920 [Note] InnoDB: 128 rollback segment(s) are active.
2016-08-10 11:04:40 140637551601920 [Note] InnoDB: Waiting for purge to start
2016-08-10 11:04:40 140637551601920 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.30-76.3 started; log sequence number 249787949721
2016-08-10 11:04:40 140634669156096 [Note] InnoDB: Dumping buffer pool(s) not yet started
2016-08-10 11:04:40 140637551601920 [Note] Plugin 'FEEDBACK' is disabled.
2016-08-10 11:04:44 140017536481536 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-08-10 11:04:44 140017536481536 [Note] InnoDB: The InnoDB memory heap is disabled
2016-08-10 11:04:44 140017536481536 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-08-10 11:04:44 140017536481536 [Note] InnoDB: Memory barrier is not used
2016-08-10 11:04:44 140017536481536 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-08-10 11:04:44 140017536481536 [Note] InnoDB: Using Linux native AIO
2016-08-10 11:04:44 140017536481536 [Note] InnoDB: Using generic crc32 instructions
2016-08-10 11:04:44 140017536481536 [Note] InnoDB: Initializing buffer pool, size = 2.0G
2016-08-10 11:04:45 140017536481536 [Note] InnoDB: Completed initialization of buffer pool
2016-08-10 11:04:45 140017536481536 [Note] InnoDB: Highest supported file format is Barracuda.
2016-08-10 11:05:03 140017536481536 [Note] InnoDB: 128 rollback segment(s) are active.
2016-08-10 11:05:03 140017536481536 [Note] InnoDB: Waiting for purge to start
2016-08-10 11:05:03 140017536481536 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.30-76.3 started; log sequence number 249787949731
2016-08-10 11:05:03 140017536481536 [Warning] InnoDB: Skipping buffer pool dump/restore during wsrep recovery.
2016-08-10 11:05:03 140017536481536 [Note] Plugin 'FEEDBACK' is disabled.
2016-08-10 11:05:03 140017536481536 [Note] Server socket created on IP: '0.0.0.0'.
2016-08-10 11:05:03 140017536481536 [Note] WSREP: Recovered position: 0b0379b3-a949-11e5-b414-ab8a34af3e6e:22655598

If I try to restart the service I get this errors:

  1. service mysql restart
    Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.

Aug 10 11:06:15 dbmysql3 mysqld[19746]: WSREP: Failed to recover position: '2016-08-10 11:05:55 139731192588544 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
Aug 10 11:06:15 dbmysql3 mysqld[19746]: 2016-08-10 11:05:55 139731192588544 [Note] /usr/sbin/mysqld (mysqld 10.1.16-MariaDB-1~xenial) starting as process 19943 ...'

If I manually run "mysqld &" mysql starts and joins the cluster successfully


Generated at Thu Feb 08 07:42:54 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.