|Main Archive Page > Month Archives > drbd-user archives|
Yes, I did it on purposed, because we are running live systems, so we want
to make that when the other server shutdown or hang without no reason, the
other server should take up the job. That's why I want drbd and heartbeat to
work that way. Maybe I will go with upgrading the kernel. Because my
configuration is still the same, I did not change anything and I did double
and even triple check.
On Sun, Mar 7, 2010 at 12:57 AM, Maros Timko <email@example.com> wrote:
> This is very interesting to me. You were happily creating Split-Brains
> with the old system. Now there is something that prevents you against
> it and you want to "fix" that?
> Do you really want to failover on disconnected replication link? What
> is the logic behind?
> If you really need it, try to check for fencing options and messages.
> > I have faced same problem.
> > issue resolved via upgrading kernel from 220.127.116.11-0.54.5(comes with
> sle10sp3 media) to 18.104.22.168-0.59.1
> > --ms
> > ----- Original Message -----
> > From: Reindy [mailto:firstname.lastname@example.org]
> > To: email@example.com
> > Sent: Fri, 5 Mar 2010 23:33:24 +0800
> > Subject: [DRBD-user] Primary/Unknown and Secondary/Unknown
> > Hi,
> > I got problem with my drbd+heartbeat.. previously it used to work but
> > somehow now.. the situation is..
> > I have 2 servers which is currently running primary/secondary and
> > secondary/primary
> > But, when I plug out the crossover cable, somehow the state become
> > pri/unknown and sec/unknown..
> > last time it used to work as pri/unknown and pri/unknown.. this is to
> > sure that the failover is working fine.. now it is not!
> > Any solution to this guys? really need help on this! Thanks in advance!
> drbd-user mailing list
drbd-user mailing list