Mark Hunting wrote:
> Dejan Muhamedagic wrote:
>
>> Hi,
>>
>> On Thu, Oct 01, 2009 at 04:45:45PM +0200, Mark Hunting wrote:
>>
>>
>>> Sorry for not mentioning I use Heartbeat 2.1.3 from the Debian Lenny
>>> repository, in crm configuration.
>>>
>>> Mark Hunting wrote:
>>>
>>>
I will be out of the office starting 10/02/2009 and will not return until
10/05/2009.
I will respond to your message when I return.
If your request requires immediate attention, Please contact the MVS
Technical Support Hotline
at 1-866-866-4488 x12000
**
Well this seems to normally work: HELP ME! :=)
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
On Wed, Sep 30, 2009 at 02:22:32PM +0200, James Brackinshaw wrote:
> Hello,
>
> I have a two node heartbeat setup on Centos 5.3.
>
> The two nodes are in separate locations and connected only via
> ethernet. Because of this we require that a human guarantee that a
> node is dead before a switchov
On Fri, Oct 2, 2009 at 10:17 AM, Lars Ellenberg
wrote:
> On Wed, Sep 30, 2009 at 02:22:32PM +0200, James Brackinshaw wrote:
>> Hello,
>>
>> I have a two node heartbeat setup on Centos 5.3.
>>
>> The two nodes are in separate locations and connected only via
>> ethernet. Because of this we require
Hi mark,
There is a hostcache file which yuo can remove located under /var/.
Stop Heartbeat, make a backup of your hostcache file then remove the
hostcache file. STart heartbeat and have a look again.
Having renamed your machine names will cause problems with heartbeat.
Tim
On Fri, Oct 2, 200
On Fri, Oct 02, 2009 at 10:21:53AM +0200, James Brackinshaw wrote:
> On Fri, Oct 2, 2009 at 10:17 AM, Lars Ellenberg
> wrote:
> > On Wed, Sep 30, 2009 at 02:22:32PM +0200, James Brackinshaw wrote:
> >> Hello,
> >>
> >> I have a two node heartbeat setup on Centos 5.3.
> >>
> >> The two nodes are in
Thank you so much! That solved the problem.
Timothy Carr wrote:
> Hi mark,
>
> There is a hostcache file which yuo can remove located under /var/.
>
> Stop Heartbeat, make a backup of your hostcache file then remove the
> hostcache file. STart heartbeat and have a look again.
>
> Having renamed yo
Hallo,
is there any experience on using Heartbeat with a N+N cluster, i.e. a
cluster with more than 2 nodes split over two fire-areas?
As far as I can gather from the documentation, this setup has the
problem that if one fire-area is offline, then the other fire-area
will either stop working imme
Am Freitag, 2. Oktober 2009 13:05:42 schrieb Colin:
> Hallo,
>
> is there any experience on using Heartbeat with a N+N cluster, i.e. a
> cluster with more than 2 nodes split over two fire-areas?
>
> As far as I can gather from the documentation, this setup has the
> problem that if one fire-area is
On Fri, Oct 2, 2009 at 1:14 PM, Michael Schwartzkopff wrote:
> Am Freitag, 2. Oktober 2009 13:05:42 schrieb Colin:
>>
>> is there any experience on using Heartbeat with a N+N cluster, i.e. a
>> cluster with more than 2 nodes split over two fire-areas?
>>
>> As far as I can gather from the document
Am Freitag, 2. Oktober 2009 14:00:20 schrieb Colin:
> On Fri, Oct 2, 2009 at 1:14 PM, Michael Schwartzkopff
wrote:
> > Am Freitag, 2. Oktober 2009 13:05:42 schrieb Colin:
> >> is there any experience on using Heartbeat with a N+N cluster, i.e. a
> >> cluster with more than 2 nodes split over two
On Fri, Oct 2, 2009 at 2:08 PM, Michael Schwartzkopff wrote:
> Am Freitag, 2. Oktober 2009 14:00:20 schrieb Colin:
>> On Fri, Oct 2, 2009 at 1:14 PM, Michael Schwartzkopff
>> wrote:
>
>> > Anyway: I would advise you not to use heartbeat any more, but to upgrade
>> > to pacemaker.
>>
>> We want t
Am Freitag, 2. Oktober 2009 15:00:09 schrieb Colin:
> On Fri, Oct 2, 2009 at 2:08 PM, Michael Schwartzkopff
wrote:
> > Am Freitag, 2. Oktober 2009 14:00:20 schrieb Colin:
> >> On Fri, Oct 2, 2009 at 1:14 PM, Michael Schwartzkopff
wrote:
> >> > Anyway: I would advise you not to use heartbeat any
Hi,
in V1 clusters, after a split-brain... is there a way to tell to
Heartbeat to keep running services on primary node (first field in
haresources) and stop them in secondary? In my current configuration,
the services are stopped on both servers by a few seconds and then the
primary node start th
15 matches
Mail list logo