Unable to start first node of cluster.

MySQL & MariaDB Percona XtraDB Cluster 5.x
1

Complete Percona newbie, so have some patience :slight_smile:

I’ve installed the Percona Server software on 3 Centos nodes (version 5.6).
After that, I installed the Cluster software (version 5.5) - most of that seemed to be already included in the server software.
Next step : adapt the my.cnf file according to www.percona.com/doc/percona-xtradb-cluster/5.5/howtos/cenots_howto.html

Now, when I try to start the first node with
/etc/init.d/mysql start --wsrep_cluster_address=“gcomm://”

I get :
Starting MySQL (Percona Server)… ERROR! The server quit without updating PID file

and the mysql log file says :
…
2014-01-27 14:55:23 9723 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.15-rel63.0 started; log sequence number 1626027
2014-01-27 14:55:23 9723 [ERROR] /usr/sbin/mysqld: unknown variable ‘wsrep-cluster-address=gcomm://’
2014-01-27 14:55:23 9723 [ERROR] Aborting
…

What have I missed ?

regards
Jo

2

What do you mean by installed the Percona Server software on 3 Centos nodes (version 5.6) and then installed cluster software version 5.5 ? Did you installed both Percona Server and Percona XtraDB Cluster ?
Can you show me the output of

$ rpm -qa | grep -i “percona”

3

@holvoetj,
The error clearly says there is a typo in [COLOR=#252C2F] ‘wsrep-cluster-address=gcomm://’ the variable should be wsrep_cluster_address [COLOR=#252C2F] and not wsrep-cluster-address

4

Hi mirfan

the output is :

[root@553579-srv115 ~]# rpm -qa | grep -i “percona”
percona-release-0.0-1.x86_64
Percona-XtraDB-Cluster-galera-2-2.8-1.157.rhel6.x86_64
Percona-Server-shared-56-5.6.15-rel63.0.519.rhel6.x86_64
Percona-Server-server-56-5.6.15-rel63.0.519.rhel6.x86_64
percona-xtrabackup-2.1.7-721.rhel6.x86_64
Percona-Server-client-56-5.6.15-rel63.0.519.rhel6.x86_64

regards
Jo

5

Hi madhusudan,

my command line used underscores but the error message uses hyphens. It doesn’t work with either one.

regards
Jo

6

u should put that in correct my.cnf file, check to see which my.cnf file its using while its starting…! (usually /etc/my.cnf or /etc/mysql/my.cnf) cross check with these files.

7

Hi madhusudan,

I only have one my.cnf on the server (/etc/my.cnf)

regards
Jo

8

What’s the output of /usr/sbin/mysqld --verbose --help | grep -A 1 “Default options” ?

and also do a grep of “[COLOR=#252C2F]wsrep[COLOR=#252C2F]-cluster[COLOR=#252C2F]-address” on all .cnf files.
somewhere its present!, you have to remove it.

9

Here you go :

[root@553579-srv115 ~]# /usr/sbin/mysqld --verbose --help 2>&1 | grep -A 1 “Default options”
Default options are read from the following files in the given order:
/etc/my.cnf /etc/mysql/my.cnf /usr/etc/my.cnf ~/.my.cnf

[root@553579-srv115 ~]# ls -l /etc/my.cnf /etc/mysql/my.cnf /usr/etc/my.cnf ~/.my.cnf
ls: cannot access /etc/mysql/my.cnf: No such file or directory
ls: cannot access /usr/etc/my.cnf: No such file or directory
ls: cannot access /root/.my.cnf: No such file or directory
-rw-r–r-- 1 root root 1279 Jan 29 11:03 /etc/my.cnf

regards
Jo

10

have u looked into that /etc/my.cnf file clearly for [COLOR=#252C2F]wsrep[COLOR=#252C2F]-cluster[COLOR=#252C2F]-address…?

11

Yes :slight_smile:
only underscores …

regards
Jo

12

Strange!!, only way to find is, do a grep on entire system!.. it will take time but u will get the culprit… :slight_smile:

find / -exec grep -l “wsrep-cluster-address” {} ;

for quicker search
find / -name “*.cnf” -exec grep -l “wsrep-cluster-address” {} ;

13

Hi madhusudan,

I gave up :slight_smile: and started from scratch.

  1. I made sure “yum list” and “rpm -qa” listed nothing installed from percona or mysql
  2. then ran “yum install Percona-XtraDB-Cluster-server-56” (last time I tried version 5.5)
  3. Created the file /etc/my.cnf with the contents of [url]Percona XtraDB Cluster
  4. Started it up with /etc/init.d/mysql start --wsrep-cluster-address=“gcomm://”

output :

[root@553579-srv115 ~]# /etc/init.d/mysql start --wsrep-cluster-address=“gcomm://”
Starting MySQL (Percona XtraDB Cluster). SUCCESS!

I can only imagine I had a conflict somewhere with packages installed earlier by someone else …

Many, many thanks for all your help !

regards
Jo