Pacemaker: Difference between revisions
From DWIKI
m (→FAQ) |
m (→FAQ) |
||
| Line 21: | Line 21: | ||
=FAQ= | =FAQ= | ||
==show virtual ip== | |||
pcs resource show IPv4_BIND | |||
==Error: cluster is not currently running on this node== | ==Error: cluster is not currently running on this node== | ||
pcs cluster start | pcs cluster start | ||
Revision as of 13:34, 12 August 2016
uses Corosync or heartbeat, it seems corosync is the one to go for.
Links
- Cluster Labs
- Building a high-available failover cluster with Pacemaker, Corosync & PCS
- HIGH AVAILABILITY ADD-ON ADMINISTRATION
- How To Create a High Availability Setup with Corosync, Pacemaker, and Floating IPs on Ubuntu 14.04
- http://fibrevillage.com/sysadmin/304-pcs-command-reference
Commands/tools
- crm
- crmadmin
- cibadm
- pcs
Useful commands
Dump entire crm
cibadm -Q
FAQ
show virtual ip
pcs resource show IPv4_BIND
Error: cluster is not currently running on this node
pcs cluster start
Remove a constraint
pcs constraint list --full
to identify the constraints and then
pcs constraint remove <whatever-constraint-id>
