Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

crm_mon(8) [suse man page]

CRM_MON(8)							  [FIXME: manual]							CRM_MON(8)

NAME
crm_mon - monitor the cluster's status SYNOPSIS
crm_mon [-V] -d -pfilename -h filename crm_mon [-V] [-1|-n|-r] -h filename crm_mon [-V] [-n|-r] -X filename crm_mon [-V] [-n|-r] -c|-1 crm_mon [-V] -i interval crm_mon -? DESCRIPTION
The crm_mon command allows you to monitor your cluster's status and configuration. Its output includes the number of nodes, uname, uuid, status, the resources configured in your cluster, and the current status of each. The output of crm_mon can be displayed at the console or printed into an HTML file. When provided with a cluster configuration file without the status section, crm_mon creates an overview of nodes and resources as specified in the file. OPTIONS
--help, -? Provide help. --verbose, -V Increase the debug output. --interval seconds, -i seconds Determine the update frequency. If -i is not specified, the default of 15 seconds is assumed. --group-by-node, -n Group resources by node. --inactive, -r Display inactive resources. --as-console, -c Display the cluster status on the console. --one-shot, -1 Display the cluster status once on the console then exit (does not use ncurses). --as-html filename, -h filename Write the cluster's status to the specified file. --daemonize, -d Run in the background as a daemon. --pid-file filename, -p filename Specify the daemon's pid file. --xml-file filename, -X filename Specify an XML file containing a cluster configuration and create an overview of the cluster's configuration. EXAMPLES
Display your cluster's status and get an updated listing every 15 seconds: crm_mon Display your cluster's status and get an updated listing after an interval specified by -i. If -i is not given, the default refresh interval of 15 seconds is assumed: crm_mon -i interval[s] Display your cluster's status on the console: crm_mon -c Display your cluster's status on the console just once then exit: crm_mon -1 Display your cluster's status and group resources by node: crm_mon -n Display your cluster's status, group resources by node, and include inactive resources in the list: crm_mon -n -r Write your cluster's status to an HTML file: crm_mon -h filename Run crm_mon as a daemon in the background, specify the daemon's pid file for easier control of the daemon process, and create HTML output. This option allows you to constantly create HTML output that can be easily processed by other monitoring applications: crm_mon -d -p filename -h filename Display the cluster configuration laid out in an existing cluster configuration file (filename), group the resources by node, and include inactive resources. This command can be used for dry-runs of a cluster configuration before rolling it out to a live cluster. crm_mon -r -n -X filename FILES
/var/lib/heartbeat/crm/cib.xml--the CIB (minus status section) on disk. Editing this file directly is strongly discouraged. AUTHOR
crm_mon was written by Andrew Beekhof. [FIXME: source] 07/05/2010 CRM_MON(8)

Check Out this Related Man Page

OCF_HEARTBEAT_CLUSTE(7) 					OCF resource agents					   OCF_HEARTBEAT_CLUSTE(7)

NAME
ocf_heartbeat_ClusterMon - Runs crm_mon in the background, recording the cluster status to an HTML file SYNOPSIS
ClusterMon [start | stop | monitor | meta-data | validate-all] DESCRIPTION
This is a ClusterMon Resource Agent. It outputs current cluster status to the html. SUPPORTED PARAMETERS
user The user we want to run crm_mon as (optional, string, default root) update How frequently should we update the cluster status (optional, integer, default 15) extra_options Additional options to pass to crm_mon. Eg. -n -r (optional, string, no default) pidfile PID file location to ensure only one instance is running (unique, optional, string, default /tmp/ClusterMon_default.pid) htmlfile Location to write HTML output to. (unique, optional, string, default /tmp/ClusterMon_default.html) SUPPORTED ACTIONS
This resource agent supports the following actions (operations): start Starts the resource. Suggested minimum timeout: 20. stop Stops the resource. Suggested minimum timeout: 20. monitor Performs a detailed status check. Suggested minimum timeout: 20. Suggested interval: 10. meta-data Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5. validate-all Performs a validation of the resource configuration. Suggested minimum timeout: 30. EXAMPLE
The following is an example configuration for a ClusterMon resource using the crm(8) shell: primitive p_ClusterMon ocf:heartbeat:ClusterMon op monitor depth="0" timeout="20" interval="10" SEE ALSO
http://www.linux-ha.org/wiki/ClusterMon_(resource_agent) AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors) resource-agents UNKNOWN 03/09/2014 OCF_HEARTBEAT_CLUSTE(7)
Man Page

Featured Tech Videos