Pacemaker: Difference between revisions
From DWIKI
m (→FAQ) |
m (→FAQ) |
||
| Line 38: | Line 38: | ||
to identify the constraints and then | to identify the constraints and then | ||
pcs constraint remove <whatever-constraint-id> | pcs constraint remove <whatever-constraint-id> | ||
==Clear error messages== | |||
pcs resource cleanup | |||
==Call cib_replace failed (-205): Update was older than existing configuration== | ==Call cib_replace failed (-205): Update was older than existing configuration== | ||
can be run only once | |||
Revision as of 11:44, 7 March 2018
uses Corosync or heartbeat, it seems corosync is the one to go for.
Links
- Cluster Labs
- Pacemaker explained
- 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
- Cheatsheet
Commands/tools
- crm
- crmadmin
- cibadm
- pcs
Useful commands
Dump entire crm
cibadm -Q
FAQ
set maintenance mode
pcs property set maintenance-mode=true
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>
Clear error messages
pcs resource cleanup
Call cib_replace failed (-205): Update was older than existing configuration
can be run only once
