| 2013-11-21 17:38:10 |
Marc Castrovinci |
description |
Yesterday I had no problems installing Percona Cluster. Today a new build would not start and the following was seen in the error logs:
131121 16:38:22 [Note] WSREP: wsrep_load(): loading provider library '/usr/lib/libgalera_smm.so'
131121 16:38:22 [ERROR] WSREP: provider interface version mismatch: need '23', found '25'
131121 16:38:22 [ERROR] WSREP: wsrep_load(): interface version mismatch: my version 23, provider version 25
16:38:22 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Please help us make Percona XtraDB Cluster better by reporting any
bugs at https://bugs.launchpad.net/percona-xtradb-cluster
Comparing yesterdays build to todays, I noticed the following change in installed packages ( located in /var/cache/apt/archives ):
The working version installed percona-xtradb-cluster-galera-2.x_162.precise_amd64.deb
while the broken one today installed percona-xtradb-cluster-galera-3.x_169.precise_amd64.deb
This change does come when PXC cluster 5.6 beta was released and uses galera 3.x
http://www.mysqlperformanceblog.com/2013/11/21/percona-xtradb-cluster-5-6-14-25-1-beta-now-available/ |
Yesterday I had no problems installing Percona Cluster. Today a new build would not start and the following was seen in the error logs:
131121 16:38:22 [Note] WSREP: wsrep_load(): loading provider library '/usr/lib/libgalera_smm.so'
131121 16:38:22 [ERROR] WSREP: provider interface version mismatch: need '23', found '25'
131121 16:38:22 [ERROR] WSREP: wsrep_load(): interface version mismatch: my version 23, provider version 25
16:38:22 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Please help us make Percona XtraDB Cluster better by reporting any
bugs at https://bugs.launchpad.net/percona-xtradb-cluster
Comparing yesterdays build to todays, I noticed the following change in installed packages ( located in /var/cache/apt/archives ):
The working version installed percona-xtradb-cluster-galera-2.x_162.precise_amd64.deb
while the broken one today installed percona-xtradb-cluster-galera-3.x_169.precise_amd64.deb
Removing the wrong galera replicator and installing 2.x fixed the problem.
Steps:
sudo dpkg --force-all -P percona-xtradb-cluster-galera-3.x
wget http://repo.percona.com/apt/pool/main/p/percona-xtradb-cluster-galera-2.x/percona-xtradb-cluster-galera-2.x_162.precise_amd64.deb
dpkg -i percona-xtradb-cluster-galera-2.x_162.precise_amd64.deb
This change does come when PXC cluster 5.6 beta was released and uses galera 3.x
http://www.mysqlperformanceblog.com/2013/11/21/percona-xtradb-cluster-5-6-14-25-1-beta-now-available/ |
|
