[DRBD-user] DRBD+Heartbeat: Secondary node Refusing to be Primary

Lars Ellenberg lars.ellenberg at linbit.com
Thu Jul 15 10:03:00 CEST 2010

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.

On Thu, Jul 15, 2010 at 12:01:28PM +0530, Deepak Pal wrote:
> Hello All,
> As I have already told you in my previous mail that my drbd was not
> working  with Heartbeat. Now after making some changes in the
> configuration files It's running on the primary master automatically
> with heartbeat .
> Thanks to u guys for that...!
> But when primary node goes down then secondary node refuses to be
> primary and consequences drive is not mounted automatically to the
> mount point on secondary node.
> my message log in /var/log on secondary node when Primary node goes
> down(I manually detach the network cables for testing) are:
> */var/log/messages:*
> Jul 15 10:55:03 sec kernel: block drbd1: PingAck did not arrive in time.
> Jul 15 10:55:03 sec kernel: block drbd1: peer( Primary -> Unknown )
> conn( SyncTarget -> NetworkFailure ) pdsk( UpToDate -> DUnknown )

Your cluster state was
  Primary, UpToDate, SyncSource <-> Secondary, Inconsistent, SyncTarget

You lose the Primary, UpToDate data set.
You do no longer have access to valid data.
DRBD correctly refuses to go online with Inconsistent data.

If it helps, you can think of it as losing the single good disk
of a two disk degraded RAID1 while it is rebuilding.

You want to avoid that.

: 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.
please don't Cc me, but send to list   --   I'm subscribed

More information about the drbd-user mailing list