crm_report(8) [debian man page]

1.1.7(8)						  System Administration Utilities						  1.1.7(8)

NAME

       1.1.7 - Part of the Pacemaker cluster resource manager

SYNOPSIS

       crm_report -f "YYYY-M-D H:M:S" [-t "YYYY-M-D H:M:S"] [additional options] [dest]

DESCRIPTION

       crm_report - Create a tarball containing everything needed when reporting cluster problems

OPTIONS

       -V     increase verbosity

       -v,--version
	      software version

       --features
	      software features

       -f, --from time
	      time to start from: "YYYY-M-D H:M:S"  (do not forget the quotes)

       -t, --to time
	      time to finish at (default: now)

       -T, --cts test
	      CTS test or set of tests to extract

       --cts-log
	      CTS master logfile

       -n, --nodes nodes
	      node names for this cluster only needed if the cluster is not active on the current machine accepts both -n "a b" and -n a -n b

       -l, --logfile file
	      log file to collect, normally this will be determined automatically

       -p patt
	      additional regular expression to match variables to be removed (default: "passw.*")

       -L patt
	      additional regular expression to match in log files for analysis (default: CRIT: ERROR:)

       -M     collect only the logs specified by -l

       -S, --single-node
	      single node operation; don't try to start report collectors on other nodes

       -c, --cluster type
	      force the cluster type (corosync,openais,heartbeat,logmaster)

       -A, --openais
	      force the cluster type to be OpenAIS

       -C, --corosync
	      force the cluster type to be CoroSync

       -H, --heartbeat
	      force the cluster type to be Heartbeat

       -u, --user user
	      ssh username for cluster nodes (default: root)

       --dest a custom destination directory/file

       dest   a custom destination directory/file

EXAMPLES

	      crm_report  -f  "2011-12-14 13:05:00" unexplained-apache-failure crm_report -f 2011-12-14 -t 2011-12-15 something-that-took-multiple
	      days crm_report -f 13:05:00   -t 13:12:00   brief-outage

1.1.7 - ee0730e13d124c3d58f00016c3376a1de5323cff		    April 2012								  1.1.7(8)

COROSYNC-NOTIFYD(8)					      System Manager's Manual					       COROSYNC-NOTIFYD(8)

NAME

       corosync-notifyd - Listen for important corosync events and send dbus and/or snmp traps.

SYNOPSIS

       corosync-notifyd [-f] [-l] [-o] [-s] [-m] [manager] [-d] [-h]

DESCRIPTION

       corosync-notifyd uses corosync API to listen for important cluster events and can log them, generate dbus signals or genterate snmp traps.

OPTIONS

       -f     Start application in foreground.

       -l     Log all events.

       -o     Print events to stdout (turns on -l).

       -s     Send SNMP traps on all events.

       -m     Set the SNMP manager address.

       -d     Send DBUS signals on all events.

       -h     Print this help

EXAMPLES

       $ corosync-notifyd -o
       corosync-notifyd[18505]: troll[23374016] corosync-notify:18505:12 is now connected to corosync
       corosync-notifyd[18505]: troll[23374016] corosync-notify:18505:13 is now disconnected from corosync
       corosync-notifyd[18505]: troll[23374016] is now quorate
       corosync-notifyd[18505]: r2[1550100672] ip:192.168.100.92 joined
       corosync-notifyd[18505]: r2[1550100672] ip:192.168.100.92 left

       $ corosync-notifyd -o

       Note this output below is from "dbus-monitor --system"

       signal sender=:1.216 -> dest=(null destination) serial=2 path=/com/redhat/cluster/corosync;
	interface=com.redhat.cluster.corosync; member=ConnectionStateChange
	  string "troll"
	  uint32 23374016
	  string "corosync-notify:18900:12"
	  string "connected"
       signal sender=:1.216 -> dest=(null destination) serial=3 path=/com/redhat/cluster/corosync;
	interface=com.redhat.cluster.corosync; member=ConnectionStateChange
	  string "troll"
	  uint32 23374016
	  string "corosync-notify:18900:13"
	  string "disconnected"
       signal sender=:1.216 -> dest=(null destination) serial=4 path=/com/redhat/cluster/corosync;
	interface=com.redhat.cluster.corosync; member=QorumStateChange
	  string "troll"
	  uint32 23374016
	  string "quorate"
       signal sender=:1.216 -> dest=(null destination) serial=5 path=/com/redhat/cluster/corosync;
	interface=com.redhat.cluster.corosync; member=NodeStateChange
	  string "r2"
	  uint32 1550100672
	  string "192.168.100.92"
	  string "joined"
       signal sender=:1.216 -> dest=(null destination) serial=6 path=/com/redhat/cluster/corosync;
	interface=com.redhat.cluster.corosync; member=NodeStateChange
	  string "r2"
	  uint32 1550100672
	  string "192.168.100.92"
	  string "left"

SEE ALSO

       corosync(8), corosync-objctl(8), dbus-monitor(1),

AUTHOR

       Angus Salkeld

								    2011-01-14						       COROSYNC-NOTIFYD(8)