Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi
i just told my cluster (pacemaker 1.0.3) to stop a drbd device (crm
resource stop). DRBD version is 8.2.7
This happened:
May 28 15:10:27 cl-virt-1 kernel: drbd7: role( Primary -> Secondary )
May 28 15:10:28 cl-virt-1 kernel: drbd7: Requested state change failed
by peer: Concurrent state changes detected and aborted (-19)
May 28 15:10:28 cl-virt-1 kernel: drbd7: Requested state change failed
by peer: Concurrent state changes detected and aborted (-19)
May 28 15:10:28 cl-virt-1 kernel: drbd7: Requested state change failed
by peer: Concurrent state changes detected and aborted (-19)
May 28 15:10:28 cl-virt-1 kernel: drbd7: State change failed: State
changed was refused by peer node
------^ there's a typo btw--------------------------------------
May 28 15:10:28 cl-virt-1 kernel: drbd7: state = { cs:Connected
st:Secondary/Secondary ds:UpToDate/UpToDate r--- }
May 28 15:10:28 cl-virt-1 kernel: drbd7: wanted = { cs:Connected
st:Secondary/Secondary ds:Diskless/UpToDate r--- }
May 28 15:10:28 cl-virt-1 kernel: drbd7: peer( Secondary -> Unknown )
conn( Connected -> TearDown ) pdsk( UpToDate -> DUnknown )
May 28 15:10:28 cl-virt-1 kernel: drbd7: asender terminated
May 28 15:10:28 cl-virt-1 kernel: drbd7: Terminating asender thread
May 28 15:10:28 cl-virt-1 kernel: drbd7: Connection closed
May 28 15:10:28 cl-virt-1 kernel: drbd7: conn( TearDown -> Unconnected )
May 28 15:10:28 cl-virt-1 kernel: drbd7: receiver terminated
May 28 15:10:28 cl-virt-1 kernel: drbd7: Restarting receiver thread
May 28 15:10:28 cl-virt-1 kernel: drbd7: receiver (re)started
May 28 15:10:28 cl-virt-1 kernel: drbd7: conn( Unconnected ->
WFConnection )
May 28 15:10:28 cl-virt-1 lrmd: [21712]: info: RA output:
(drbd-micro-web01:0:stop:stderr) 2009/05/28_15:10:28 ERROR: micro-web01:
Command output: /dev/drbd7: State change failed: (-10) State changed was
refused by peer node /dev/drbd7: State change failed: (-10) State
changed was refused by peer node Command 'drbdsetup /dev/drbd7 down'
terminated with exit code 11
May 28 15:10:28 cl-virt-1 lrmd: [21712]: info: RA output:
(drbd-micro-web01:0:stop:stdout) /dev/drbd7: State change failed: (-10)
State changed was refused by peer node /dev/drbd7: State change failed:
(-10) State changed was refused by peer node Command 'drbdsetup
/dev/drbd7 down' terminated with exit code 11
This is the log from the other node:
May 28 15:10:27 cl-virt-2 kernel: drbd7: peer( Primary -> Secondary )
May 28 15:10:28 cl-virt-2 kernel: drbd7: peer( Secondary -> Unknown )
conn( Connected -> Disconnecting ) pdsk( UpToDate -> DUnknown )
May 28 15:10:28 cl-virt-2 kernel: drbd7: short read expecting header on
sock: r=-512
May 28 15:10:28 cl-virt-2 kernel: drbd7: asender terminated
May 28 15:10:28 cl-virt-2 kernel: drbd7: Terminating asender thread
May 28 15:10:28 cl-virt-2 kernel: drbd7: Connection closed
May 28 15:10:28 cl-virt-2 kernel: drbd7: conn( Disconnecting ->
StandAlone )
May 28 15:10:28 cl-virt-2 kernel: drbd7: receiver terminated
May 28 15:10:28 cl-virt-2 kernel: drbd7: Terminating receiver thread
May 28 15:10:28 cl-virt-2 kernel: drbd7: disk( UpToDate -> Diskless )
May 28 15:10:28 cl-virt-2 kernel: drbd7: drbd_bm_resize called with
capacity == 0
May 28 15:10:28 cl-virt-2 kernel: drbd7: worker terminated
May 28 15:10:28 cl-virt-2 kernel: drbd7: Terminating worker thread
What exactly happened there and how can I avoid it?
Regards
Dominik