[DRBD-user] Parse error an option keyword expected but got fence peer

[Keith Christian]

I've searched for a solution to this error, lots of hits for "Parse
error" but couldn't find anything specific for "fence-peer."

I have checked the drbd.conf file for obvious errors like unbalanced
braces, and missing semicolons at the end of line.  Nothing found.

Using these RPM's:

    drbd82-8.2.6-1.el5.centos
    kmod-drbd82-8.2.6-2



This is on a 64 bit system, so I fixed line 31 which needed "lib64" to
find the file:

        ls -l /usr/lib64/heartbeat/drbd-peer-outdater
        -rwxr-xr-x 1 root root 15984 Feb  6  2008
/usr/lib64/heartbeat/drbd-peer-outdater



When running any DRBD command I see this error:

    drbdadm create-md drbd-resource-0
    /etc/drbd.conf:31: Parse error: 'an option keyword' expected,
            but got 'fence-peer'




I commented out line 31, tried to start DRBD again, and saw the error
on line 56, removed the comment from line 31, and the error returns to
line 31.

        service drbd start
        /etc/drbd.conf:56: Parse error: 'an option keyword' expected,
                but got 'outdated-wfc-timeout'
        Starting DRBD resources:    /etc/drbd.conf:56: Parse error:
'an option keyword' expected,
                but got 'outdated-wfc-timeout'

        53     # Wait for connection timeout if the peer node is
already outdated.
        54     # (Do not set this to 0, since that means unlimited)
        55     #
        *** 56     outdated-wfc-timeout 2;  # 2 seconds.
        57            # In case there was a split brain situation the
devices will
        58     # drop their network configuration instead of connecting. Since



Below are the first 35 lines of the file, which enclose the line
throwing the error:

	 1 global { usage-count no; }
	 2
	 3 resource drbd-resource-0 {
	 4   protocol C;
	 5
	 6 handlers {
	 7   # what should be done in case the node is primary, degraded
	 8     # (=no connection) and has inconsistent data.
	 9     pri-on-incon-degr "/usr/lib/drbd/notify-pri-on-incon-degr.sh;
/usr/lib/drbd/notify-emergency-reboot.sh; echo b > /proc/sysrq-trigger
; reboot -f";
	10
	11     # The node is currently primary, but lost the after split brain
	12     # auto recovery procedure. As as consequence it should go away.
	13     pri-lost-after-sb "/usr/lib/drbd/notify-pri-lost-after-sb.sh;
/usr/lib/drbd/notify-emergency-reboot.sh; echo b > /proc/sysrq-trigger
; reboot -f";
	14
	15     # In case you have set the on-io-error option to "call-local-io-error",
	16     # this script will get executed in case of a local IO error. It is
	17     # expected that this script will case a immediate failover in the
	18     # cluster.
	19     local-io-error "/usr/lib/drbd/notify-local-io-error.sh;
/usr/lib/drbd/notify-emergency-shutdown.sh; echo o >
/proc/sysrq-trigger ; halt -f";
	20
	21
	22     # Commands to run in case we need to downgrade the peer's disk
	23     # state to "Outdated". Should be implemented by the superior
	24     # communication possibilities of our cluster manager.
	25     # The provided script uses ssh, and is for demonstration/development
	26     # purposis.
	27     # fence-peer "/usr/lib/drbd/outdate-peer.sh on amd
192.168.22.11 192.168.23.11 on alf 192.168.22.12 192.168.23.12";
	28     #
	29     # Update: Now there is a solution that relies on heartbeat's
	30     # communication layers. You should really use this.
	*** 31     fence-peer "/usr/lib64/heartbeat/drbd-peer-outdater -t 5";
	32     # For Pacemaker you might use:
	33     # fence-peer "/usr/lib/drbd/crm-fence-peer.sh";
	34
	35 }



I'd appreciate any insight or help.


====== Keith