[MDEV-10464] Unable to start bootstrap mode in Ubuntu 14.04.4 LTS & MariaDB 10.1.16 Created: 2016-07-29  Updated: 2019-05-21  Resolved: 2019-05-21

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

Type: Bug Priority: Major
Reporter: Iñigo Martinez Assignee: Jan Lindström (Inactive)
Resolution: Not a Bug Votes: 0
Labels: None


 Description   

After upgrading our Ubuntu 14.04.2 and MariaDB 10.1.5 to latest version available, we cannot start in bootstrap mode anymore. (14.04.4 LTS and MariaDB 10.1.16).
It appear that --wsrep-new-cluster is not passed to mysqld binary and so cluster does not start.

We have temporary fixed by adding manually wsrep-new-cluster to my.cnf file, but this is not the proper way.
Remember: Ubuntu 14.04 DOES NOT use systemd and so the way to start MariaDB cluster is via "service mysql start" or "service mysql bootstrap".

T



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

inigoml What command(s) did you try to execute in order to bootstrap the cluster node?
Can you share the node's configurations as well as the server logs?

Comment by Iñigo Martinez [ 2016-07-29 ]

service mysql bootstrap

Same command we used since we installed the server.

Of course, second node is shutdown.
Server do not start unless we add to my.cnf a wsrep-new-cluster directive. At syslog we only have an error saying mysql process ended with -1

Since init.d script has not changed we think this problem is due to a change at "service" command behaviour at Ubuntu. Now it doesn't accept parameters.

I cannot share logs because currently I don't have access to database server but I have found this problem in two server cluster upgraded to Ubuntu 14.04.4 LTS.

Comment by Iñigo Martinez [ 2016-08-01 ]

By the way, I've verified that galera_new_cluster script exists.

However, this script is only valid for linux distributions using systemd (for example Ubuntu 16.04 LTS), but Ubuntu 14.04 DOES NOT USE systemd.

Comment by Iñigo Martinez [ 2016-08-01 ]

It's an initclt problem. Start is never executed by /etc/init.d/mysql script and is run by initctl start command that not passes --wsrep-new-cluster parameter.

WORKAROUND: Delete or rename /etc/init/mysql.conf

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