On Wed, Jul 14, 2010 at 03:41:11PM +1000, Jai wrote:
> Hi,
>
> I'm not sure if this is the right place to ask as it could be a drdb issue.
>
> I have a Centos 5.2 with heartbeat-2.1.4-2.1 and drbd82-8.2.6-1.el5.centos.
> After having tested various scenarios during construction, one being a reboot
> on a primary server, I have found that it failed to successfully failover now
> that it's in production.
>
> The problem was drdb failed to promote to primary
> According to the logs after the primary was rebooted
> - slave heartbeat received shutdown notice from peer, then
> drbd1: role( Secondary -> Primary )
Um. There it does promote to Primary just fine.
> drbd1: Writing meta data super block now.
> drbd1: State change failed: Refusing to be Primary while peer is not outdated
> drbd1: state = { cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate
> r--- }
> drbd1: wanted = { cs:TearDown st:Primary/Unknown ds:UpToDate/DUnknown r--- }
> drbd1: peer( Secondary -> Unknown ) conn( Connected -> TearDown ) pdsk(
> UpToDate -> Outdated )
That's just noise telling you that it outdated the other node.
> drbd1: Writing meta data super block now.
> drbd1: Creating new current UUID
> drbd1: Writing meta data super block now.
> drbd1: asender terminated
> drbd1: Terminating asender thread
> drbd1: tl_clear()
> drbd1: Connection closed
> drbd1: conn( TearDown -> Unconnected )
> drbd1: receiver terminated
> drbd1: receiver (re)started
> drbd1: conn( Unconnected -> WFConnection )
>
> I'm thinking dopd might have had something to do with the failure of the drbd
> resource takeover.
> Anyone know what might have happened?
Did you want to show us something else?
--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
