[MDEV-10445] galera_new_cluster does not work on new cluster Created: 2016-07-26  Updated: 2016-08-05  Resolved: 2016-07-27

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

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

Centos 7.x


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

 Description   

Trying to start the first node if the cluster has never been created before with galera_new_cluster does not work.

The unique way to make it work is comming out the "pre":

#ExecStartPre=/bin/sh -c "systemctl unset-environment _WSREP_START_POSITION"
#ExecStartPre=/bin/sh -c "VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && \

  1. systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1"
log
Jul 26 11:37:28 web01.tribuna.inc mysqld[13373]: WSREP: Failed to recover position: '2016-07-26 11:37:26 140709822269568 [Note] /usr/sbin/mysqld (mysqld 10.1.16-MariaDB) starting as process 13609 ...'
Jul 26 11:37:28 web01.tribuna.inc systemd[1]: mariadb.service: control process exited, code=exited status=1
Jul 26 11:37:28 web01.tribuna.inc systemd[1]: Failed to start MariaDB database server.
Jul 26 11:37:28 web01.tribuna.inc systemd[1]: Unit mariadb.service entered failed state.
Jul 26 11:37:28 web01.tribuna.inc systemd[1]: mariadb.service failed.


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

MDEV-10396

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