On 10/04/2013, at 9:22 AM, David Coulson wrote:
>
> On 4/9/13 7:18 PM, Andrew Beekhof wrote:
>> Pacemaker is not supported in 6.3 and all I am allowed to say at this
>> point[1] is that your configuration isn't supportable for 6.4
>> Not because you've configured anything wrong/badly, but beca
On 4/9/13 7:18 PM, Andrew Beekhof wrote:
Pacemaker is not supported in 6.3 and all I am allowed to say at this point[1]
is that your configuration isn't supportable for 6.4
Not because you've configured anything wrong/badly, but because a specific
application is not present.
However, if I can
On 10/04/2013, at 8:51 AM, David Coulson wrote:
>
> On 4/7/13 10:29 PM, Andrew Beekhof wrote:
>>
>> Really really weird, I've got nothing :(
> We've added SPANs on the switches for the two boxes in the cluster, so we can
> hopefully at least identify that the ARP frame didn't come from them.
On 4/7/13 10:29 PM, Andrew Beekhof wrote:
Really really weird, I've got nothing :(
We've added SPANs on the switches for the two boxes in the cluster, so
we can hopefully at least identify that the ARP frame didn't come from
them. Of course, we've not had an occurrence of it in almost a month
On 19/03/2013, at 9:08 AM, David Coulson wrote:
>
> On 3/18/13 5:24 PM, Andrew Beekhof wrote:
>> So:
>>
>> 1. the IP moved from 01 to 02
>> 2. 01 was then rebooted
>> 3. a long time passes
>> 4. 01 starts arping for the IP
>>
>> Is that what you're saying?
>> Is the problem transient or does
On 3/18/13 5:24 PM, Andrew Beekhof wrote:
So:
1. the IP moved from 01 to 02
2. 01 was then rebooted
3. a long time passes
4. 01 starts arping for the IP
Is that what you're saying?
Is the problem transient or does it persist?
Went like this - IP movements are all by Pacemaker/IPaddr resource
On Mon, Mar 18, 2013 at 1:00 PM, David Coulson wrote:
> Last movement of the ip was six days before issue when we patched and
> rebooted one of the nodes.
>
> Resource is a simple ipaddr (not ipaddr2) with an ip and net mask. Like I
> said, really simple config so confused :)
So:
1. the IP mov
Last movement of the ip was six days before issue when we patched and rebooted
one of the nodes.
Resource is a simple ipaddr (not ipaddr2) with an ip and net mask. Like I said,
really simple config so confused :)
Sent from my iPhone
On Mar 17, 2013, at 9:01 PM, Andrew Beekhof wrote:
> On Mo
On Mon, Mar 18, 2013 at 3:17 AM, David Coulson wrote:
> First off, I'm going to preface this with the realization that what I am
> explaining makes no sense, doesn't follow normal logic and I'm not a
> complete idiot. I've beaten my head against a wall with this issue for two
> days, and have made
First off, I'm going to preface this with the realization that what I am
explaining makes no sense, doesn't follow normal logic and I'm not a
complete idiot. I've beaten my head against a wall with this issue for
two days, and have made no progress, yet we've had a couple of
production system o
10 matches
Mail list logo
