Another information:<br><br>If I insert the node name and resource in the drbd-peer-outdater it works well!!<br>(I insert outdate-peer "/usr/lib64/heartbeat/drbd-peer-outdater -p centos-xen2 -r r1"; in the drbd.conf of the centos-xen1 node where the resource is master).<br>
<br>Seems that the drbd-outdater doesn't find the name of the peer.<br><br>Why?<br><br><br><br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Fausto Lombardi</b> <span dir="ltr"><<a href="mailto:faulomba@gmail.com">faulomba@gmail.com</a>></span><br>
Date: 2009/9/11<br>Subject: Re: [Pacemaker] drbd outdate peer<br>To: <a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><br><br><br>This is <a href="http://ha.cf" target="_blank">ha.cf</a> file:<br>
<br>debugfile /var/log/ha-debug<br>logfile /var/log/ha-log<br>logfacility none<br>bcast eth0 eth1<br>auto_failback on<br>node centos-xen1 centos-xen2<br>
respawn root /usr/lib64/heartbeat/mgmtd -v <br>
respawn root /usr/lib64/heartbeat/dopd<br>apiauth mgmtd uid=root<br>apiauth dopd uid=root<br>crm yes<br><br><br>and this the drbd.conf file:<br><br>global { usage-count no; }<br><br>common { syncer { rate 10M; verify-alg md5; } }<br>
<br>resource r1 {<br> protocol C;<br><br> startup {wfc-timeout 60;<br> degr-wfc-timeout 50;<br> }<br><br> disk { on-io-error detach;<br> fencing resource-only; <br> }<br><br> handlers {<br> outdate-peer "/usr/lib64/heartbeat/drbd-peer-outdater";<br>
}<br><br><br> on centos-xen1 {<br> device /dev/drbd1;<br> disk /dev/sda3;<br> address <a href="http://172.16.0.1:7789" target="_blank">172.16.0.1:7789</a>;<br> meta-disk internal;<br> }<br>
<br> on centos-xen2 {<br>
device /dev/drbd1;<br> disk /dev/hda3;<br> address <a href="http://172.16.0.2:7789" target="_blank">172.16.0.2:7789</a>;<br> meta-disk internal;<br> }<br>}<br><br>And then this is what I say in the messages<br>
<br>Sep 11 18:38:23 centos-xen1 kernel: block drbd1: PingAck did not arrive in time.<br>Sep 11 18:38:23 centos-xen1 kernel: block drbd1: peer( Secondary -> Unknown ) conn( Connected -> NetworkFailure ) pdsk( UpToDate -> DUnknown )<br>
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: asender terminated<br>Sep 11 18:38:23 centos-xen1 kernel: block drbd1: Terminating asender thread<br>Sep 11 18:38:23 centos-xen1 kernel: block drbd1: short read expecting header on sock: r=-512<br>
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: Creating new current UUID<br>Sep 11 18:38:23 centos-xen1 kernel: block drbd1: Connection closed<br>Sep 11 18:38:23 centos-xen1 kernel: block drbd1: helper command: /sbin/drbdadm fence-peer minor-1<br>
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: helper command: /sbin/drbdadm fence-peer minor-1 exit code 1 (0x100)<br>Sep 11 18:38:23 centos-xen1 kernel: block drbd1: fence-peer helper broken, returned 1<br>Sep 11 18:38:23 centos-xen1 kernel: block drbd1: Considering state change from bad state. Error would be: 'Refusing to be Primary while peer is not outdated'<br>
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: old = { cs:NetworkFailure ro:Primary/Unknown ds:UpToDate/DUnknown r--- }<br>Sep 11 18:38:23 centos-xen1 kernel: block drbd1: new = { cs:Unconnected ro:Primary/Unknown ds:UpToDate/DUnknown r--- }<br>
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: conn( NetworkFailure -> Unconnected )<br>Sep 11 18:38:23 centos-xen1 kernel: block drbd1: receiver terminated<br>Sep 11 18:38:23 centos-xen1 kernel: block drbd1: Restarting receiver thread<br>
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: receiver (re)started<br>Sep 11 18:38:23 centos-xen1 kernel: block drbd1: Considering state change from bad state. Error would be: 'Refusing to be Primary while peer is not outdated'<br>
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: old = { cs:Unconnected ro:Primary/Unknown ds:UpToDate/DUnknown r--- }<br>Sep 11 18:38:23 centos-xen1 kernel: block drbd1: new = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r--- }<br>
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: conn( Unconnected -> WFConnection )<br><br><br>Why?<br><br><br><div class="gmail_quote">
2009/9/11 Raoul Bhatia [IPAX] <span dir="ltr"><<a href="mailto:r.bhatia@ipax.at" target="_blank">r.bhatia@ipax.at</a>></span><div><div></div><div class="h5"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>On 09/11/2009 04:15 PM, Fausto Lombardi wrote:<br>
> Hi of all,<br>
> I have set up two nodes with heartbeat, pacemaker and drbd with dopd and<br>
> drbd-peer-outdate handler.<br>
><br>
> All works well, but if I unplug the replication link of the drbd the<br>
> slave resource is not outdated.<br>
> Why?<br>
><br>
> I have follow the guide at<br>
> <a href="http://www.drbd.org/users-guide/s-heartbeat-dopd.html" target="_blank">http://www.drbd.org/users-guide/s-heartbeat-dopd.html</a><br>
> but it doesn't work.<br>
<br>
</div>please post your configuration. maybe you can use hb_report to create<br>
a report from such an unplug event.<br>
<br>
cheers,<br>
raoul<br>
--<br>
____________________________________________________________________<br>
DI (FH) Raoul Bhatia M.Sc. email. <a href="mailto:r.bhatia@ipax.at" target="_blank">r.bhatia@ipax.at</a><br>
Technischer Leiter<br>
<br>
IPAX - Aloy Bhatia Hava OEG web. <a href="http://www.ipax.at" target="_blank">http://www.ipax.at</a><br>
Barawitzkagasse 10/2/2/11 email. <a href="mailto:office@ipax.at" target="_blank">office@ipax.at</a><br>
1190 Wien tel. +43 1 3670030<br>
FN 277995t HG Wien fax. +43 1 3670030 15<br>
____________________________________________________________________<br>
<br>
_______________________________________________<br>
Pacemaker mailing list<br>
<a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
</blockquote></div></div></div><br>
</div><br>