Pacemaker: Difference between revisions
From DWIKI
mNo edit summary |
mNo edit summary |
||
| Line 4: | Line 4: | ||
*[http://clusterlabs.org/ Cluster Labs] | *[http://clusterlabs.org/ Cluster Labs] | ||
*[http://jensd.be/156/linux/building-a-high-available-failover-cluster-with-pacemaker-corosync-pcs Building a high-available failover cluster with Pacemaker, Corosync & PCS] | *[http://jensd.be/156/linux/building-a-high-available-failover-cluster-with-pacemaker-corosync-pcs Building a high-available failover cluster with Pacemaker, Corosync & PCS] | ||
*[https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/High_Availability_Add-On_Administration/index.html HIGH AVAILABILITY ADD-ON ADMINISTRATION] | |||
=Commands/tools= | =Commands/tools= | ||
| Line 16: | Line 17: | ||
==Dump entire crm== | ==Dump entire crm== | ||
cibadm -Q | cibadm -Q | ||
=FAQ= | |||
==Error: cluster is not currently running on this node== | |||
pcs cluster start | |||
Revision as of 08:20, 8 July 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
Commands/tools
- crm
- crmadmin
- cibadm
- pcs
Useful commands
Dump entire crm
cibadm -Q
FAQ
Error: cluster is not currently running on this node
pcs cluster start
