On Wed, 2010-10-06 at 21:30 -0700, AR wrote:
Solved.
the issue was that the 10.8.64.140 address was sticking to node1. I
dont know why this was happening? But once I removed the address all is
working well.
On Wed, 2010-10-06 at 20:45 -0300, mike wrote:
On 10-10-06 07:09 PM, AR wrote:
I'm curious - is that 10.8.64.140 address the VIP address for the cluster?
On 10-10-07 01:21 PM, AR wrote:
On Wed, 2010-10-06 at 21:30 -0700, AR wrote:
Solved.
the issue was that the 10.8.64.140 address was sticking to node1. I
dont know why this was happening? But once I removed the
No, not for the cluster. It is for the socks proxy listening adapter.
On Thu, 2010-10-07 at 13:52 -0300, mike wrote:
I'm curious - is that 10.8.64.140 address the VIP address for the cluster?
On 10-10-07 01:21 PM, AR wrote:
On Wed, 2010-10-06 at 21:30 -0700, AR wrote:
Solved.
the
Hi, First let me say thank you to those of you that support the project.
It appears that there are orphan processes running? How do I get rid of
these?
# crm_verify -LVV
crm_verify[31892]: 2010/10/06_14:55:10 WARN: process_orphan_resource:
Nothing known about resource vip_0:1 running on node2
On 10-10-06 07:09 PM, AR wrote:
Hi, First let me say thank you to those of you that support the project.
It appears that there are orphan processes running? How do I get rid of
these?
# crm_verify -LVV
crm_verify[31892]: 2010/10/06_14:55:10 WARN: process_orphan_resource:
Nothing known
On Wed, 2010-10-06 at 20:45 -0300, mike wrote:
On 10-10-06 07:09 PM, AR wrote:
Hi, First let me say thank you to those of you that support the project.
It appears that there are orphan processes running? How do I get rid of
these?
# crm_verify -LVV
crm_verify[31892]:
