Re: [DRBD-user] Dual Primary Mode: Shared Directory blocked after node crash until reboot

DRBD User Wed, 27 May 2015 01:34:08 -0700

for the DEBUG part i found a solution: adding a function for the nop ':' does the trick

:()
{
echo $@
}

Gesendet: Mittwoch, 27. Mai 2015 um 08:37 Uhr
Von: "DRBD User" <[email protected]>
An: [email protected]
Betreff: [DRBD-user] Dual Primary Mode: Shared Directory blocked after node crash until reboot

Finally i got fencing working !

BUT now i see a gap of about 30sec between the invocation of crm-fence-peer.sh and the stonith-ng 'reboot':

from var/log/messages:

...
May 26 15:42:00 node1 kernel: drbd r0: conn( Unconnected -> WFConnection )
May 26 15:42:00 node1 kernel: drbd r0: helper command: /sbin/drbdadm fence-peer r0
May 26 15:42:00 node1 crm-fence-peer.sh[16214]: invoked for r0
...
May 26 15:42:27 node1 stonith-ng[3204]: notice: log_operation: Operation 'reboot' [16191] (call 2 from stonith-api.16190) for host 'node2' with device 'fencing-node2' returned: 0 (OK)
...

is this a pacemaker/corosync timeout ? how can i adjust this timing ?

BTW: how can i switch on debug mode for script /usr/lib/crm-fence-peer.sh ?
for eg.
: == DEBUG == $cibadmin_invocations cibadmin calls ==

thx
_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user

_______________________________________________
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user

Re: [DRBD-user] Dual Primary Mode: Shared Directory blocked after node crash until reboot

Reply via email to