On Tue, Jan 19, 2010 at 4:59 PM, Shravan Mishra
wrote:
> cibadmin 1.0.5 for OpenAIS and Heartbeat (Build:
> 9e9faaab40f3f97e3c0d623e4a4c47ed83fa1601)
That version is too old to support corosync.
I'm surprised it even compiles.
You need at least Pacemaker 1.0.6 and Corosync 1.1.2
http://theclu
Corosync Cluster Engine, version '1.1.1' SVN revision '2534'
Copyright (c) 2006-2009 Red Hat, Inc.
Shravan
On Tue, Jan 19, 2010 at 10:59 AM, Shravan Mishra
wrote:
> cibadmin 1.0.5 for OpenAIS and Heartbeat (Build:
> 9e9faaab40f3f97e3c0d623e4a4c47ed83fa1601)
>
> -Shravan
>
> On Tue, Jan 19, 2010
cibadmin 1.0.5 for OpenAIS and Heartbeat (Build:
9e9faaab40f3f97e3c0d623e4a4c47ed83fa1601)
-Shravan
On Tue, Jan 19, 2010 at 8:29 AM, Andrew Beekhof wrote:
> On Sat, Jan 16, 2010 at 9:20 PM, Shravan Mishra
> wrote:
>> Hi Guys,
>>
>> I'm running the following version of pacemaker and corosync
>>
On Sat, Jan 16, 2010 at 9:20 PM, Shravan Mishra
wrote:
> Hi Guys,
>
> I'm running the following version of pacemaker and corosync
> corosync=1.1.1-1-2
> pacemaker=1.0.9-2-1
That pacemaker version doesn't exist.
What does cibadmin --version say?
And are you sure about the corosync version, it doe
One possibility is you have a different cluster in your network on the
same multicast address and port.
Regards
-steve
On Sat, 2010-01-16 at 15:20 -0500, Shravan Mishra wrote:
> Hi Guys,
>
> I'm running the following version of pacemaker and corosync
> corosync=1.1.1-1-2
> pacemaker=1.0.9-2-1
>
Hi,
I'm seeing following messages in corosync.log
=
Jan 18 09:50:41 corosync [pcmk ] ERROR: check_message_sanity: Message
payload is corrupted: expected 1929 bytes, got 669
Jan 18 09:50:41 corosync [pcmk ] ERROR: check_message_sanity: Child
28857 spawned to record non-fatal assertion
Hi ,
Since the interfaces on the two nodes are connected via cross over
cable so there is no chance of that happening and since I'm using rrp:
passive, which means that the other ring i.e. ring 1 will come into
play only when ring 0 fails,I assume. I say this because ring 1
interface is on the ne
On Sat, Jan 16, 2010 at 9:20 PM, Shravan Mishra
wrote:
> Hi Guys,
>
> I'm running the following version of pacemaker and corosync
> corosync=1.1.1-1-2
> pacemaker=1.0.9-2-1
>
> Every thing had been running fine for quite some time now but then I
> started seeing following errors in the corosync lo
Hi Guys,
I'm running the following version of pacemaker and corosync
corosync=1.1.1-1-2
pacemaker=1.0.9-2-1
Every thing had been running fine for quite some time now but then I
started seeing following errors in the corosync logs,
=
Jan 16 15:08:39 corosync [TOTEM ] Received message has
