Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Sat, Sep 11, 2010 at 11:12:57AM +0200, Robert @ GMail wrote: > Dear list's friends, I've noticed one strange action on two nodes with the > following listed drbd.conf setup. > > The two nodes are crossover connected with two bonded nics, set for high > availability, not for performances. > > For some reason, at the startup the bonded drbd network didn't came up > correctly (could be for the crossover connection? Forget it, it is not the > issue I'll talk about)), so it was not possible to ping 10.1.1.x each other, > no connection for drbd. > > The supposed scenario I expected to be WFConnection on both nodes, and it > was, but with Primary/Unknown on the server-1 and Secondary/Unknown on the > server-2. > > My issue is that they both were Secondary You just said server-1 was Primary? Anyways, if DRBD is told to become Primary by someone (like the init script), but cannot become Primary for some reason, it says so in the kernel logs. Find the kernel logs from the time frame where you think DRBD is misbehaving, and see if it complains about anything. Or maybe the init script did not even get that far as to try and promote whatever is configured? > and I had to manually issue the > "drbdadm primary" command on server-1. > It did work, not a big deal, but it would be better if this can work as > expected. > > Could be due to some settings in the drbd.conf? > > What follow is the drbd.con content and I thank you in advance for any kind > of tip. -- : 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