Details
-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 10.0.16-galera
-
Fix Version/s: 10.1
-
Component/s: Admin statements, Galera
-
Environment:CentOS 7
Description
After installing MariaDB Galera from YUM repo, could not find bootstrap command option for starting cluster:
[root@node1 ~]# systemctl start mysql --wsrep_new_cluster systemctl: unrecognized option '--wsrep_new_cluster'
As with PXC:
[root@node1 ~]# systemctl start mysql@bootstrap.service Failed to issue method call: Unit mysql@bootstrap.service failed to load: No such file or directory. [root@node1 ~]# systemctl bootstrap mysql.service Unknown operation 'bootstrap'.
Gliffy Diagrams
Attachments
Issue Links
- is blocked by
-
MDEV-427 Provide a systemd script for MariaDB
-
- In Review
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
I have installed it from CentOS 7 repo:
[root@node1 ~]# cat /etc/yum.repos.d/MariaDB.repo [mariadb] name = MariaDB baseurl = http://yum.mariadb.org/10.0/centos7-amd64 gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB gpgcheck=1
There is still /etc/init.d/mysql bootstrap
As I understand, MariaDB doesn't actually install a unit file, apparently it's some default magic that allows to start/stop the service with systemctl, and this magic only covers basic operations like start/stop.
Percona, on the other hand, does install mysql.service and mysql@.service.
Assigned to Sergei Golubchik for now, in case we want to do something about it in the server package as well. If it's only Galera cluster that needs the service, please reassign.
As a workaround use:
service mysql bootstrap
Because it is still supported for backward compatibility, but surely it will be removed with upcoming releases.
Also must note that,
[root@node1 ~]# systemctl status mysql.service mysql.service - LSB: start and stop MySQL Loaded: loaded (/etc/rc.d/init.d/mysql) Active: inactive (dead) since Tue 2015-03-10 22:29:31 AZT; 14h ago Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
But in fact it is up and running:
[root@node1 ~]# service mysql status MySQL running (9610) [ OK ] [root@node1 ~]# mysql -u root -p Enter password: Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 349 Server version: 10.0.17-MariaDB-wsrep-log MariaDB Server, wsrep_25.10.r4144 Copyright (c) 2000, 2015, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]> show databases; +--------------------+ | Database | +--------------------+ | information_schema | | mysql | | performance_schema | | test | +--------------------+ 4 rows in set (0.03 sec)
Should adding "_SYSTEMCTL_SKIP_REDIRECT=true" in init script be a potential solution?
https://github.com/codership/mysql-wsrep/commit/a0ba0d7e176551c7e13daa2ef8974d8aade2dfc7.patch
Did you install mariadb from yum.mariadb.org or from the CentOS 7 repository?