auth 2
#1 crc
2 sha1 passwordhere
#3 md5 Hello!

#just.linux-ha.org	135.9.216.110 httpa

#vs1.foo.com vip.foo.com http # <-- put actual IP down instead of vip.foo.com
vs1.foo.com IPaddr::10.10.10.10 ldirectord::ldirectord.cf # <-- if you use ldirector like this
# multiple VIP example follows
# vs1.so.com IPaddr::10.10.10.10 IPaddr::10.10.10.254 ldirectord::ldirectord.cf

#       File to wirte debug messages to debugfile /var/log/ha-debug
#       File to write other messages to logfile /var/log/ha-log
#       Facility to use for syslog()/logger logfacility     local0
#       keepalive: how many seconds between heartbeats
keepalive 1
#       deadtime: seconds-to-declare-host-dead
deadtime 20
#       hopfudge maximum hop count minus number of nodes in config
#hopfudge 1
#       serial  serialportname ...
serial  /dev/ttyS0
#       Only for serial ports.  It applies to both PPP/UDP and "raw" ports
#       This means run PPP over ports ttyS1 and ttyS2
#       Their respective IP addresses are as listed.
#       Note that I enforce that these are local addresses.
#	Other addresses are almost certainly a mistake.
#ppp-udp        /dev/ttyS1 10.0.0.1 /dev/ttyS2 10.0.0.2
#       Baud rate for both serial and ppp-udp ports...
baud    19200
#       What UDP port to use for udp or ppp-udp communication?
udpport 694
#       What interfaces to heartbeat over?
udp     eth0
#       Watchdog is the watchdog timer.
#	If our own heart doesn't beat for
#       a minute, then our machine will reboot.
#watchdog /dev/watchdog
#       Nice_failback sets the behavior when performing a failback:
#
#       - if it's on, when the primary node starts or comes back from any
#         failure and the cluster is already active, i.e. the secondary
#         server performed a failover, the primary stays quiet, acting as a
#         secondary.  This way some operations like syncing disks can be
#         easily done.
#       - if it's off (default), the primary node will always be the primary,
#         whenever it's powered on.
nice_failback off		# <-- might want to turn this on after you get things working
#       Tell what machines are in the cluster
#       node    nodename ...    -- must match uname -n
node    vs1.foo.com	# <-- must match uname -n !
node    vs2.foo.com	# <-- must match uname -n !

mon             2583/tcp                        # MON
mon             2583/udp                        # MON traps

cd /usr/include
h2ph *.h sys/*.h asm/*.h

#!/bin/bash
# example heartbeat.alert from Juri
# Script to start/stop heartbeat daemon
# Put a line like
# alert heartbeat.alert
# or
# upalert heartbeat.alert
# in your mon config file

HEARTBEAT="/etc/rc.d/init.d/heartbeat"
if [ $9 = "-u" ]; then
	$HEARTBEAT start
else
	$HEARTBEAT stop
fi

#!/bin/sh
# example pid.mon from Juri
# Script for mon to check wether a process is running or not.
# Invoke with
# monitor pid.monitor process

/sbin/pidof -s $1 > /dev/null 2>&1

if [ $? -eq "0" ]; then
	echo "$1 running"
	exit 0
else
	echo "$1 not running"
	exit 1
fi

# Sample mon.cf configuration file for mon, originally from Juri
#
# You have to restart mon after editing this file in order for your
# changes to take effect.

authtype	=	userfile
userfile	=	/etc/mon/monusers.cf
cfbasedir	=	/etc/mon
alertdir	=	/usr/src/mon/alert.d
mondir		=	/usr/src/mon/mon.d
logdir		=	/var/log/mon
dtlogfile	=	/var/log/mon/downtime
dtlogging	=	yes
historicfile	=	/var/log/mon/history
maxprocs	=	20
histlength	=	100
monerrfile	=	/var/log/mon/errfile

# Hostgroup entries
#hostgroup node1 stage-monitor
#
#hostgroup node2 vs1
#
hostgroup gateway 10.0.1.2

#hostgroup heartbeat localhost


###########
# Gateway #
###########

watch gateway
	service fping
		interval 10s
		monitor fping.monitor
		#comp_alerts	<-- default starting in mon 0.99.1
		period NORMAL: wd {Sun-Sat}
			numalerts 1
			alertafter 3
			alert heartbeat.alert
			upalert restartheartbeat.alert # read mon file

#############
# Heartbeat #
#############

#watch heartbeat
#	service heartbeat
#		interval 15s
#		monitor pid.monitor /usr/lib/heartbeat/heartbeat
#		depend gateway:fping
#		dep_behavior m
#		period NORMAL: wd {Sun-Sat}
#			#alert restartheartbeat.alert
#			upalert heartbeat.alert

##############
# First node #
##############
#
#watch node1
#	service http
#		interval 10s
#		monitor http.monitor
#		period NORMAL: wd {Sun-Sat}
#			alert restart.alert httpd ;;
#		period ADVANCED: wd {Sun-Sat}
#                       alert mail.alert root
#			alert reboot.alert
#			alertafter 3
#			alertevery 1m
# Example for testing disk operations
#	service disk
#		interval 10s
#		monitor nfs.monitor /vol/shared/0/ ;;
#		period wd {Sun-Sat}
#                        alert mail.alert -s 'REBOOT: Disk not responding!' root
#			alert hardreboot.alert
#			alertafter 2
#			alertevery 1m
# Example for testing rpc based services such as nfs, nis etc.
#	service rpc
#		interval 10s
#		monitor rpc.monitor -r mountd -r nfs
#		period wd {Sun-Sat}
#                        alert mail.alert root
#			alertafter 2
#                        alertevery 1m
###############
# Second node #
###############
#
#watch node2
# Example for testing disk operations
#	service disk
#		interval 10s
#		monitor nfs.monitor /tmp ;;
#		period wd {Sun-Sat}
#                       alert mail.alert root
#			alert hardreboot.alert
#			alertafter 2
#			alertevery 1m
# Example for testing samba
#	service samba
#		interval 15s
#		monitor tcp.monitor -p 139 localhost
#		period wd {Sun-Sat}
#                        alert restart.alert smb
#		period ADVANCED: wd {Sun-Sat}
#                        alert mail.alert root
#			alert reboot.alert
#			alertafter 3
#			alertevery 1m