SUSE Linux Enterprise Server 10 SP2

Chapter 6. Managing a Cluster / crm_verify
	crm_uuid		Chapter 7. Creating Resources

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.

--dtd-file string, -D string

Use the given DTD file instead of /usr/share/heartbeat/crm.dtd.

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.

Author

crm_verify was written by Andrew Beekhof.