On 2008-02-04T17:39:22, Mike Toler <[EMAIL PROTECTED]> wrote:

> Feb  4 15:46:11 nfs_server1 lrmd: [4570]: info: rsc:drbd0:0: start
> Feb  4 15:46:11 nfs_server1 drbd[4850]: INFO: r0: Using hostname node_0
> Feb  4 15:46:11 nfs_server1 lrmd: [4570]: info: RA output:
> (drbd0:0:start:stdout) /etc/drbd.conf:395: in resource r0, on
> nfs_server1.prodea.local.lab { ... } ... on nfs_server2.prodea.local.lab
> { ... }: There are multiple host sections for the peer. Maybe misspelled
> local host name 'node_0'? /etc/drbd.conf:395: in resource r0, there is
> no host section for this host. Missing 'on node_0 {...}' ?

You set the clone_overrides_hostname attribute:

>                <nvpair id="ia-drbd0-2" name="clone_overrides_hostname"
> value="yes"/>

... while apparently using the real hostnames in drbd.conf. One or the
other is wrong.


>                <nvpair id="drbd0:0_target_role" name="target_role"
> value="started"/>

(How did that get in here? You already have target_role set on the clone
itself, no need to duplicate it here.)

>        </rsc_location>
>        <rsc_order id="order_drbd0_ip0" to="ip0" from="ms-drbd0"/>
>        <rsc_colocation id="colo_drbd0_ip0" to="ip0" from="drbd0:0"
> score="infinity"/>
>      </constraints>

That's a weird bit as well. You're only collocating one IP address with
drbd, not two.

Your setup is a mix between one with floating peers (where each drbd
peer would be tied to a specific IP explicitly, clone_overrides_hostname
would be set, etc) and a regular drbd setup (where peers are statically
assigned to nodes).

That won't work.


> This message is confidential to Prodea Systems, Inc unless otherwise 
> indicated 
> or apparent from its nature. This message is directed to the intended 
> recipient 
> only, who may be readily determined by the sender of this message and its 
> contents. If the reader of this message is not the intended recipient, or an 
> employee or agent responsible for delivering this message to the intended 
> recipient:(a)any dissemination or copying of this message is strictly 
> prohibited; and(b)immediately notify the sender by return message and destroy 
> any copies of this message in any form(electronic, paper or otherwise) that 
> you 
> have.The delivery of this message and its information is neither intended to 
> be 
> nor constitutes a disclosure or waiver of any trade secrets, intellectual 
> property, attorney work product, or attorney-client communications. The 
> authority of the individual sending this message to legally bind Prodea 
> Systems  
> is neither apparent nor implied,and must be independently verified.

BTW, this footer is rather inappropriate for a public mailing list, and
has no legal implications at all ;-)


Regards,
    Lars

-- 
Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde

_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to