# "Unknow variable wsrep\_cluster\_address" (actually wsrep\_\*) after upgrade 5.5 -\> 5.6

**URL:** <https://forums.percona.com/t/unknow-variable-wsrep-cluster-address-actually-wsrep-after-upgrade-5-5-5-6/3738>\
**Category:** Percona XtraDB Cluster 5.x\
**Created:** [September 15, 2014, 6:02am UTC](https://forums.percona.com/t/unknow-variable-wsrep-cluster-address-actually-wsrep-after-upgrade-5-5-5-6/3738 "2014-09-15T06:02:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![joepmeloen12](https://avatars.discourse-cdn.com/v4/letter/j/bcef8e/32.png) [@joepmeloen12](https://forums.percona.com/u/joepmeloen12)\
**Post date:** [September 15, 2014, 6:02am UTC](https://forums.percona.com/t/unknow-variable-wsrep-cluster-address-actually-wsrep-after-upgrade-5-5-5-6/3738/1 "2014-09-15T06:02:57Z")

</div>

Following [url][Percona Server for MySQL 8.0 - Documentation — Percona Server 8.0 Documentation](http://www.percona.com/doc/percona-server/5.6/upgrading_guide_55_56.html%5B/url%5D) I just upgrade a 3-node PXC (test) cluster tot 5.6 All fine, though after upgrading the 1st node (rest of cluster is down) and starting it, I get the following (started with --wsrep\_cluster\_address=gcomm://)

014-09-15 13:22:30 1413 [Warning] Using unique option prefix myisam\_recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.  
2014-09-15 13:22:30 1413 [Note] Plugin ‘FEDERATED’ is disabled.  
2014-09-15 13:22:30 1413 [Note] InnoDB: Using atomics to ref count buffer pool pages  
2014-09-15 13:22:30 1413 [Note] InnoDB: The InnoDB memory heap is disabled  
2014-09-15 13:22:30 1413 [Note] InnoDB: Mutexes and rw\_locks use GCC atomic builtins  
2014-09-15 13:22:30 1413 [Note] InnoDB: Memory barrier is not used  
2014-09-15 13:22:30 1413 [Note] InnoDB: Compressed tables use zlib 1.2.8  
2014-09-15 13:22:30 1413 [Note] InnoDB: Using Linux native AIO  
2014-09-15 13:22:30 1413 [Note] InnoDB: Using CPU crc32 instructions  
2014-09-15 13:22:30 1413 [Note] InnoDB: Initializing buffer pool, size = 500.0M  
2014-09-15 13:22:30 1413 [Note] InnoDB: Completed initialization of buffer pool  
2014-09-15 13:22:30 1413 [Note] InnoDB: Highest supported file format is Barracuda.  
2014-09-15 13:22:30 1413 [Note] InnoDB: 128 rollback segment(s) are active.  
2014-09-15 13:22:30 1413 [Note] InnoDB: Waiting for purge to start  
2014-09-15 13:22:30 1413 [Note] InnoDB: Percona XtraDB ([http://www.percona.com](http://www.percona.com)) 5.6.20-68.0 started; log sequence number 15578194093  
2014-09-15 13:22:30 1413 [ERROR] mysqld: unknown variable ‘wsrep\_cluster\_address=gcomm://node2,node3’  
2014-09-15 13:22:30 1413 [ERROR] Aborting

When I remove wsrep\_cluster\_address, the next wsrep\_\* will appear as being unknown. They all fail. AFAICS all packages were installed correctly :

root@vtestnode1:~# dpkg --get-selections | grep -v deinstall| grep -i percona  
libperconaserverclient18.1 install  
percona-server-client-5.6 install  
percona-server-common-5.6 install  
percona-server-server-5.6 install

Ubuntu information:

root@vtestnode1:~# lsb\_release -a  
No LSB modules are available.  
Distributor ID: Ubuntu  
Description: Ubuntu 14.04.1 LTS  
Release: 14.04  
Codename: trusty

Anyone have a clue what I’m doing wrong here?

---

<div class="post-metadata">

**Author:** ![joepmeloen12](https://avatars.discourse-cdn.com/v4/letter/j/bcef8e/32.png) [@joepmeloen12](https://forums.percona.com/u/joepmeloen12)\
**Post date:** [September 16, 2014, 4:35am UTC](https://forums.percona.com/t/unknow-variable-wsrep-cluster-address-actually-wsrep-after-upgrade-5-5-5-6/3738/2 "2014-09-16T04:35:41Z")

</div>

Well, in case somebody has the same: turns out that de-installing _all_ percona related software and re-installing 5.6 fixed this. Probably it’s wise to deinstall 5.5 before installing 5.6.

---

<div class="post-metadata">

**Author:** ![joepmeloen12](https://avatars.discourse-cdn.com/v4/letter/j/bcef8e/32.png) [@joepmeloen12](https://forums.percona.com/u/joepmeloen12)\
**Post date:** [September 16, 2014, 9:28am UTC](https://forums.percona.com/t/unknow-variable-wsrep-cluster-address-actually-wsrep-after-upgrade-5-5-5-6/3738/3 "2014-09-16T09:28:15Z")

</div>

Another update: per the manual I used

sudo apt-get install percona-server-server-5.6

… to install the new version. That part didn’t work (for me, at last). I did succeed by using

sudo apt-get install percona-xtradb-cluster-56

A clear case of RTRFM… read the RIGHT fine manual. Leaving this post here anyway in case somebody reads the wrong manual like I did.
