[MDEV-10446] Note] WSREP: Recovered position: - WSREP: Failed to recover position Created: 2016-07-26  Updated: 2016-08-05  Resolved: 2016-07-27

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

Type: Bug Priority: Major
Reporter: none now Assignee: Nirbhay Choubey (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Environment:

Centos 7.2


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

 Description   

I think an update from 10.1.14 to 10.1.16 might be the culprit?
I try to restart the cluster and it fails:
in logs:

2016-07-26 14:48:15 139717081184384 [Note] InnoDB: Compressed tables use zlib 1.2.7
2016-07-26 14:48:15 139717081184384 [Note] InnoDB: Using Linux native AIO
2016-07-26 14:48:15 139717081184384 [Note] InnoDB: Using SSE crc32 instructions
2016-07-26 14:48:15 139717081184384 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-07-26 14:48:15 139717081184384 [Note] InnoDB: Completed initialization of buffer pool
2016-07-26 14:48:15 139717081184384 [Note] InnoDB: Highest supported file format is Barracuda.
2016-07-26 14:48:15 139717081184384 [Note] InnoDB: 128 rollback segment(s) are active.
2016-07-26 14:48:15 139717081184384 [Note] InnoDB: Waiting for purge to start
2016-07-26 14:48:15 139717081184384 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.30-76.3 started; log sequence number 110576354
2016-07-26 14:48:15 139717081184384 [Warning] InnoDB: Skipping buffer pool dump/restore during wsrep recovery.
2016-07-26 14:48:15 139717081184384 [Note] InnoDB: Creating #1 thread id 139716292761344 total threads 4.
2016-07-26 14:48:15 139717081184384 [Note] InnoDB: Creating #2 thread id 139716275984128 total threads 4.
2016-07-26 14:48:16 139717081184384 [Note] InnoDB: Creating #3 thread id 139716267591424 total threads 4.
2016-07-26 14:48:16 139717081184384 [Note] InnoDB: Creating #4 thread id 139716259198720 total threads 4.
2016-07-26 14:48:16 139717081184384 [Note] Plugin 'FEEDBACK' is disabled.
2016-07-26 14:48:16 139717081184384 [Note] Server socket created on IP: '::'.
2016-07-26 14:48:16 139717081184384 [Note] WSREP: Recovered position: cc2ae15e-fa6b-11e5-aaba-da42ff198f35:2225

at the same time in systemctl:
16455]: WSREP: Failed to recover position: '2016-07-26 14:48:15 139717081184384 [Note] /usr/sbin/mysqld (mysqld 10.1.16-MariaDB) starting as process 16533 ...'

regards.



 Comments   
Comment by Elena Stepanova [ 2016-07-26 ]

It's the same problem as MDEV-10396, right?

Comment by Nirbhay Choubey (Inactive) [ 2016-07-27 ]

MDEV-10396

Comment by none now [ 2016-07-28 ]

the easiest, quickest fix - in my case at least - is to NOT use: log-error, log-basename in the config. If these are there then systemd fails to start mariadb service.

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