On Fri, Apr 16, 2010 at 04:07:10PM -0500, Patrick Cotner wrote:
>
> > > On 04/16/2010 07:04 PM, Patrick Cotner wrote:
> > > > cl_status hblinkstatus san02 eth2 reports 'dead' from san01.
But later you show
> > > > cl_status hblinkstatus san02 eth1 >> dead << this is the problem
So which on
On Fri, Apr 16, 2010 at 03:53:11PM -0500, Patrick Cotner wrote:
>
>
> > On 04/16/2010 07:04 PM, Patrick Cotner wrote:
> > > cl_status hblinkstatus san02 eth2 reports 'dead' from san01.
> > > The interface is up and I can ping from either side.
> > > I can't figure out why heartbeat thinks this
> > On 04/16/2010 07:04 PM, Patrick Cotner wrote:
> > > cl_status hblinkstatus san02 eth2 reports 'dead' from san01.
> > > The interface is up and I can ping from either side.
> > > I can't figure out why heartbeat thinks this interface is
> > dead and I'm
> > > not sure what I need to do next
> On 04/16/2010 07:04 PM, Patrick Cotner wrote:
> > cl_status hblinkstatus san02 eth2 reports 'dead' from san01.
> > The interface is up and I can ping from either side.
> > I can't figure out why heartbeat thinks this interface is
> dead and I'm
> > not sure what I need to do next inorder to
On 04/16/2010 07:04 PM, Patrick Cotner wrote:
> cl_status hblinkstatus san02 eth2 reports 'dead' from san01.
> The interface is up and I can ping from either side.
> I can't figure out why heartbeat thinks this interface is dead and I'm
> not sure what I need to do next inorder to resolve it.
>
cl_status hblinkstatus san02 eth2 reports 'dead' from san01.
The interface is up and I can ping from either side.
I can't figure out why heartbeat thinks this interface is dead and I'm
not sure what I need to do next inorder to resolve it.
Basic setup:
Heartbeat 3.0.2 on debian lenny, two nodes:
On Fri, Apr 16, 2010 at 5:51 PM, Alessandra Giovanardi
wrote:
> Andrew Beekhof wrote:
>> On Fri, Apr 16, 2010 at 9:49 AM, Alessandra Giovanardi
>> wrote:
>>
>>> Hi,
>>> I'm using heartbeat-2.1.4-0.16.2 on a SUSE Linux Enterprise Server 10 SP3
>>> (x86_64).
>>>
>>> My cluster is composed by two n
Andrew Beekhof wrote:
> On Fri, Apr 16, 2010 at 9:49 AM, Alessandra Giovanardi
> wrote:
>
>> Hi,
>> I'm using heartbeat-2.1.4-0.16.2 on a SUSE Linux Enterprise Server 10 SP3
>> (x86_64).
>>
>> My cluster is composed by two nodes: mdm01-mdm02, with two Resource Group:
>>
>> .
>>
>>
>> Recen
On Fri, Apr 16, 2010 at 9:49 AM, Alessandra Giovanardi
wrote:
> Hi,
> I'm using heartbeat-2.1.4-0.16.2 on a SUSE Linux Enterprise Server 10 SP3
> (x86_64).
>
> My cluster is composed by two nodes: mdm01-mdm02, with two Resource Group:
>
> mdm01:~ # crm_mon -1
>
> Last updated: Fri Ap
At a guess, I think this might be related to the auto-nodeid code.
If you set a fixed value in corosync.conf, this possibly wouldn't happen.
On Fri, Apr 16, 2010 at 10:21 AM, Alain.Moulle wrote:
> Hi,
>
> Sorry but this was not due to new releases, but only to the fact that
> one subnet for
> the
Hi,
Sorry but this was not due to new releases, but only to the fact that
one subnet for
the redundant heartbeat was no more available on the node, whereas I
always had it in
corosync.conf, I was not aware of this "de-configuration" of IF, and it
takes me a
while to identify the problem ... So
Hi,
I'm using heartbeat-2.1.4-0.16.2 on a SUSE Linux Enterprise Server 10 SP3
(x86_64).
My cluster is composed by two nodes: mdm01-mdm02, with two Resource Group:
mdm01:~ # crm_mon -1
Last updated: Fri Apr 16 09:47:50 2010
Current DC: mdm01 (21dff8de-ac45-43bd-9592-73f68711e38d)
2
12 matches
Mail list logo
