cmannotifyd(8) [debian man page]
cmannotifyd(8) CMAN Notification Daemon cmannotifyd(8) NAME
cmannotifyd - CMAN Notification Daemon SYNOPSIS
cmannotifyd [-f] [-d] DESCRIPTION
The cmannotifyd daemon talks to CMAN and provides a mechanism to notify external entities about cluster changes. CMAN dispatches 3 kind of notifications: - CMAN_REASON_TRY_SHUTDOWN when cman requests to all clients if it is allowed to shutdown. - CMAN_REASON_STATECHANGE when cman detects a node joining or leaving the cluster. - CMAN_REASON_CONFIG_UPDATE when a configuration change event has been detected/requested. These notifications are then dispatched to the shell script cman_notify in the environment variable CMAN_NOTIFICATION. cman_notify will then execute all the scripts in the configured notification directory (default: /etc/cluster/cman-notify.d) passing a very minimal set of envvars including, of course, the CMAN_NOTIFICATION= type. The execution order is set by the filename as shown by "LC_ALL=C ls -las". cmannotifyd logs are stored in the default log file (/var/log/cluster/cmannotifyd.log). cman_notify logs are stored in the default log file (/var/log/cluster/cman_notify.log). By default the output from the scripts executed by cman_notify is redirected to /dev/null. Users can either set CMAN_NOTIFICATION_DEBUG=1 in their environment or set proper debug configura- tion in cluster.conf to redirect scripts output to the cman_notify log file. NOTES
cmannotifyd does not block on cman_notify nor check the exit status of the script. Notifications are dispatched in the same order as they arrive, one by one. CMAN_REASON_TRY_SHUTDOWN is passed to scripts for information only, they can not influence cman's decsion about whether or not to shut down. CMAN_REASON_STATECHANGE also implies CMAN_NOTIFICATION_QUORUM exported in the environment. CMAN_NOTIFICATION_QUORUM will be set to 1 (when the node is part of a quorate cluster) or 0 (otherwise). A template for cman_notify scripts can be found in the doc/ directory. OPTIONS
-f Run in the foreground (do not fork / daemonize). -d Enable debug output. November 2008 cmannotifyd(8)
Check Out this Related Man Page
CLVMD(8) System Manager's Manual CLVMD(8) NAME
clvmd - cluster LVM daemon SYNOPSIS
clvmd [-d[<value>]] [-C] [-h] [-E <lock uuid>] [-R] [-S] [-t <timeout>] [-T <start timeout>] [-V] DESCRIPTION
clvmd is the daemon that distributes LVM metadata updates around a cluster. It must be running on all nodes in the cluster and will give an error if a node in the cluster does not have this daemon running. OPTIONS
-d[<value>] Enable debug logging. Value can be 0, 1 or 2. 0 disables debug logging 1 sends debug logs to stderr (implies -f option) 2 sends debug logs to syslog If -d is specified without a value then 1 is assumed. -C Only valid if -d is also specified. Tells all clvmds in a cluster to enable/disable debug logging. Without this switch, only the local clvmd will change its debug level to that given with -d. This does not work correctly if specified on the command-line that starts clvmd. If you want to start clvmd and enable cluster-wide logging then the command needs to be issued twice, eg: clvmd clvmd -d2 -t <timeout> Specifies the timeout for commands to run around the cluster. This should not be so small that commands with many disk updates to do will fail, so you may need to increase this on systems with very large disk farms. The default is 30 seconds. -T <start timeout> Specifies the timeout for clvmd daemon startup. If the daemon does not report that it has started up within this time then the par- ent command will exit with status of 5. This does NOT mean that clvmd has not started! What it means is that the startup of clvmd has been delayed for some reason; the most likely cause of this is an inquorate cluster though it could be due to locking latencies on a cluster with large numbers of logical volumes. If you get the return code of 5 it is usually not necessary to restart clvmd - it will start as soon as that blockage has cleared. This flag is to allow startup scripts to exit in a timely fashion even if the cluster is stalled for some reason. The default is 0 (no timeout) and the value is in seconds. Don't set this too small or you will experience spurious errors. 10 or 20 seconds might be sensible. This timeout will be ignored if you start clvmd with the -d switch. -E <lock uuid> Pass lock uuid to be reacquired exclusively when clvmd is restarted. -R Tells all the running clvmds in the cluster to reload their device cache and re-read the lvm configuration file. This command should be run whenever the devices on a cluster system are changed. -S Tells the running clvmd to exit and reexecute itself, for example at the end of a package upgrade. The new instance is instructed to reacquire any locks in the same state as they were previously held. (Alternative methods of restarting the daemon have the side effect of changing exclusive LV locks into shared locks.) -I Selects the cluster manager to use for locking and internal communications, the available managers will be listed as part of the 'clvmd -h' output. clvmd will use the first cluster manager that succeeds, and it checks them in the order cman,corosync,openais. As it is quite possible to have (eg) corosync and cman available on the same system you might have to manually specify this option to override the search. -V Display the version of the cluster LVM daemon. ENVIRONMENT VARIABLES
LVM_CLVMD_BINARY The CLVMD binary to use when clmvd restart is requested. Defaults to /usr/sbin/clvmd. LVM_BINARY The LVM2 binary to use. Defaults to /sbin/lvm. SEE ALSO
lvm(8) Red Hat Inc LVM TOOLS 2.02.95(2) (2012-03-06) CLVMD(8)