Category Archive For "Pacemaker"
Percona Replication Manager – Renaming Cluster Hostnames
Recently I’ve had to rename a node on a production cluster – however, I did not have an experience on this yet so I decided to try on a sandbox and establish a known procedure. Without further ado, assuming we have 3 nodes and we want to rename ha3’s hostname to ha03.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
[root@ha01 ~]# crm status Last updated: Wed Jun 4 21:55:01 2014 Last change: Wed Jun 4 21:53:35 2014 via crm_attribute on ha01.localdomain Stack: classic openais (with plugin) Current DC: ha01.localdomain - partition with quorum Version: 1.1.10-14.el6_5.2-368c726 3 Nodes configured, 3 expected votes 6 Resources configured Online: [ ha01.localdomain ha02.localdomain ha3.localdomain ] Master/Slave Set: ms_MySQL [p_mysql] Masters: [ ha01.localdomain ] Slaves: [ ha02.localdomain ha3.localdomain ] Clone Set: ping_gw_clone [ping_gw] Started: [ ha01.localdomain ha02.localdomain ha3.localdomain ] |
Here we …
Pacemaker Failed Actions ‘not installed’ And ‘not configured’
Playing around with Percona Replication Manager, and being new to Pacemaker, some errors were somewhat cryptic.
|
1 2 |
May 26 09:53:39 [2181] ha01.localdomain pengine: notice: unpack_rsc_op: Preventing p_mysql from re-starting on ha02.localdomain: operation monitor failed 'not installed' (rc=5) May 26 09:53:39 [2181] ha01.localdomain pengine: notice: unpack_rsc_op: Preventing op from re-starting on ha02.localdomain: operation monitor failed 'not installed' (rc=5) |
First, it says here that I have ‘operation monitor failed’ on node ha02.localdomain. This error simply means ‘I cannot run the operation monitor because it is not installed’. Where does this operation supposed to come from, from the …