Pacemaker: Difference between revisions

From DWIKI
Line 49: Line 49:
  pcs property set maintenance-mode=true
  pcs property set maintenance-mode=true


==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




Line 69: Line 68:
==[Error signing on to the CIB service: Transport endpoint is not connected ]==
==[Error signing on to the CIB service: Transport endpoint is not connected ]==
  probably selinux
  probably selinux
==Show allocation scores==
crm_simulate -sL
==Show resource failcount==
pcs resource failcount show <resource>


==debug resource==
==debug resource==

Revision as of 11:59, 19 June 2018

uses Corosync or heartbeat, (it seems) corosync is the one to go for.

Links

Notes

by specifying -INFINITY, the constraint is binding.


Commands/tools

Useful commands

Dump entire crm

cibadm -Q

FAQ

show detailed resources

pcs resource --full

stop node

pcs cluster standby node-1

or

pcs node standby

on the node itself

set maintenance mode

pcs property set maintenance-mode=true


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

[Error signing on to the CIB service: Transport endpoint is not connected ]

probably selinux

Show allocation scores

crm_simulate -sL

Show resource failcount

pcs resource failcount show <resource>


debug resource

pcs resource debug-start resource

*** Resource management is DISABLED *** The cluster will not attempt to start, stop or recover services

??