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

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

NAME

       crm_verify - check the CIB for consistency

SYNOPSIS

	   crm_verify [-V] -x file

	   crm_verify [-V] -X string

	   crm_verify [-V] -L|-p

	   crm_verify [-?]

DESCRIPTION

       crm_verify checks the configuration database (CIB) for consistency and other problems. It can be used to check a file containing the
       configuration or can it can connect to a running cluster. It reports two classes of problems, errors and warnings. Errors must be fixed
       before Heartbeat can work properly. However, it is left up to the administrator to decide if the warnings should also be fixed.

       crm_verify assists in creating new or modified configurations. You can take a local copy of a CIB in the running cluster, edit it, validate
       it using crm_verify, then put the new configuration into effect using cibadmin.

OPTIONS

       --help, -h
	   Print a help message.

       --verbose, -V
	   Turn on debug information.

	       Note
	       Increase the level of verbosity by providing additional instances.

       --live-check, -L
	   Connect to the running cluster and check the CIB.

       --crm_xml string, -X string
	   Check the configuration in the supplied string. Pass complete CIBs only.

       --xml-file file, -x file
	   Check the configuration in the named file.

       --xml-pipe, -p
	   Use the configuration piped in via stdin. Pass complete CIBs only.

EXAMPLES

       Check the consistency of the configuration in the running cluster and produce verbose output:

	       crm_verify -VL

       Check the consistency of the configuration in a given file and produce verbose output:

	       crm_verify -Vx file1

       Pipe a configuration into crm_verify and produce verbose output:

	       cat file1.xml | crm_verify -Vp

FILES

       /var/lib/heartbeat/crm/cib.xml--the CIB (minus status section) on disk. Editing this file directly is strongly discouraged.

SEE ALSO

       ???

AUTHOR

       crm_verify was written by Andrew Beekhof.

[FIXME: source] 						    07/05/2010							     CRM_VERIFY(8)

Linux and UNIX Man Pages

crm_mon(8) [suse man page]

Check Out this Related Man Page