Lars
Marowsky-Bree
Sent: den 14 juni 2007 09:57
To: General Linux-HA mailing list
Subject: Re: [Linux-HA] Another DC detected after power cycle
On 2007-06-14T07:48:53, "Thomas Åkerblom (HF/EBC)" <[EMAIL PROTECTED]> wrote:
> At least at the moment, we don't want to use sto
On 2007-06-14T07:48:53, "Thomas Åkerblom (HF/EBC)" <[EMAIL PROTECTED]> wrote:
> At least at the moment, we don't want to use stonith.
So you don't have shared data? That might be OK then, but it can cause
the situation you see; it should resolve itself, but it will generate
quite a bit of angry l
list
Subject: Re: [Linux-HA] Another DC detected after power cycle
On 2007-06-13T10:30:32, "Thomas Åkerblom (HF/EBC)" <[EMAIL PROTECTED]> wrote:
> At this time I can see the message 'Another DC detected' in lim2 and in limx.
> Crm_mon will in all nodes show that
On 2007-06-13T10:30:32, "Thomas Åkerblom (HF/EBC)" <[EMAIL PROTECTED]> wrote:
> At this time I can see the message 'Another DC detected' in lim2 and in limx.
> Crm_mon will in all nodes show that lim3 is OFFLINE, even on lim3 itself.
You really, really should upgrade to 2.0.8 at least, or even be
2007/6/13, Thomas Åkerblom (HF/EBC) <[EMAIL PROTECTED]>:
Hi All.
One of our tester has a system with four servers and a standby (heartbeat
2.0.7).
servers:
lab14b-ts-lim1
lab14b-ts-lim2
lab14b-ts-lim3
lab14b-ts-lim4
standby:
lab14b-ts-limx
For each server there is a group of three services (two