This is ha.cf file:
debugfile /var/log/ha-debug
logfile /var/log/ha-log
logfacility none
bcast eth0 eth1
auto_failback on
node centos-xen1 centos-xen2
respawn root /usr/lib64/heartbeat/mgmtd -v
respawn root /usr/lib64/heartbeat/dopd
apiauth mgmtd uid=root
apiauth dopd uid=root
crm yes
and this the drbd.conf file:
global { usage-count no; }
common { syncer { rate 10M; verify-alg md5; } }
resource r1 {
protocol C;
startup {wfc-timeout 60;
degr-wfc-timeout 50;
}
disk { on-io-error detach;
fencing resource-only;
}
handlers {
outdate-peer "/usr/lib64/heartbeat/drbd-peer-outdater";
}
on centos-xen1 {
device /dev/drbd1;
disk /dev/sda3;
address 172.16.0.1:7789;
meta-disk internal;
}
on centos-xen2 {
device /dev/drbd1;
disk /dev/hda3;
address 172.16.0.2:7789;
meta-disk internal;
}
}
And then this is what I say in the messages
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: PingAck did not arrive in
time.
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: peer( Secondary -> Unknown
) conn( Connected -> NetworkFailure ) pdsk( UpToDate -> DUnknown )
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: asender terminated
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: Terminating asender thread
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: short read expecting header
on sock: r=-512
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: Creating new current UUID
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: Connection closed
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: helper command:
/sbin/drbdadm fence-peer minor-1
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: helper command:
/sbin/drbdadm fence-peer minor-1 exit code 1 (0x100)
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: fence-peer helper broken,
returned 1
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'
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: old = { cs:NetworkFailure
ro:Primary/Unknown ds:UpToDate/DUnknown r--- }
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: new = { cs:Unconnected
ro:Primary/Unknown ds:UpToDate/DUnknown r--- }
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: conn( NetworkFailure ->
Unconnected )
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: receiver terminated
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: Restarting receiver thread
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: receiver (re)started
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'
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: old = { cs:Unconnected
ro:Primary/Unknown ds:UpToDate/DUnknown r--- }
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: new = { cs:WFConnection
ro:Primary/Unknown ds:UpToDate/DUnknown r--- }
Sep 11 18:38:23 centos-xen1 kernel: block drbd1: conn( Unconnected ->
WFConnection )
Why?
2009/9/11 Raoul Bhatia [IPAX] <r.bha...@ipax.at>
> On 09/11/2009 04:15 PM, Fausto Lombardi wrote:
> > Hi of all,
> > I have set up two nodes with heartbeat, pacemaker and drbd with dopd and
> > drbd-peer-outdate handler.
> >
> > All works well, but if I unplug the replication link of the drbd the
> > slave resource is not outdated.
> > Why?
> >
> > I have follow the guide at
> > http://www.drbd.org/users-guide/s-heartbeat-dopd.html
> > but it doesn't work.
>
> please post your configuration. maybe you can use hb_report to create
> a report from such an unplug event.
>
> cheers,
> raoul
> --
> ____________________________________________________________________
> DI (FH) Raoul Bhatia M.Sc. email. r.bha...@ipax.at
> Technischer Leiter
>
> IPAX - Aloy Bhatia Hava OEG web. http://www.ipax.at
> Barawitzkagasse 10/2/2/11 email. off...@ipax.at
> 1190 Wien tel. +43 1 3670030
> FN 277995t HG Wien fax. +43 1 3670030 15
> ____________________________________________________________________
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
_______________________________________________
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
