1fence_check(8)             fence configuration check            fence_check(8)
2
3
4

NAME

6       fence_check - fence configuration check utility
7

SYNOPSIS

9       fence_check [-h] [-V] [-d] [-v] [-e]
10

DESCRIPTION

12       The fence_check utility can be used to actively test the fence configu‐
13       ration for each node in the cluster, by issuing status commands instead
14       of "reboot" "on" "off" commands on the configured fence methods/devices
15       in cluster.conf.
16
17       fence_check can also be very useful when executed via a  cron  job  for
18       regular  monitoring  of  fence devices and to detect issues after clus‐
19       ter.conf changes.
20
21

OPTIONS

23       -h     Print help message, then exit.
24
25       -V     Print program version information, then exit.
26
27       -d     Disable    output    to    logfile    (default    /var/log/clus‐
28              ter/fence_check.log).   Useful in combination with -e that could
29              record sensitive data from cluster.conf.
30
31       -v     Enable verbose output of all  actions  taken  during  execution.
32              Useful  to  debug  issues with fence_check execution.  Use of -v
33              does not include -e.
34
35       -e     Produce detailed output, in case of failure, of the command used
36              to test the fence device. Use of -e does not include -v.  ATTEN‐
37              TION: IT MIGHT SHOW FENCE PASSWORDS IN LOG FILES! USE WITH CARE!
38
39       -f     Override checks and force execution. DO NOT  USE  ON  PRODUCTION
40              CLUSTERS!
41
42

NOTES

44       fence_check can only be executed when the following conditions are met:
45
46       - cman is running on the node
47
48       - the node is quorate
49
50       - the node has joined the fence domain
51
52       - the node is in charge of fencing for the whole cluster
53
54       - no real fencing action is in progress
55
56       - no other fence_check operations are in progress.
57
58       fence_check will perform all those checks prior starting a cluster wide
59       fence status check. When used in combination with -f, cman must be run‐
60       ning  on  the node and no other processes must be performing a check at
61       the same time.
62
63       By default every run of fence_check is logged to logfile and to stdout.
64
65       fence_check returns:
66
67       0 - if execution completes 1 - on generic execution errors (fatal) 2  -
68       if cman is not running (fatal) 3 - node is not quorate/node is not part
69       of fence domain/if node is not in  charge  of  fencing/a  real  fencing
70       operation is in progress (can be overridden) 4 - if another fence_check
71       is in progress (fatal) 5 - if any of the fence status tests failed
72
73
74
75                                September 2012                  fence_check(8)
Impressum