Thanks Andrew.
On Wed, Oct 21, 2009 at 1:45 PM, Andrew Beekhof wrote:
> On Wed, Oct 21, 2009 at 5:13 PM, Shravan Mishra
> wrote:
>> Hello guys,
>>
>> We are running
>>
>> corosync-1.0.0
>> heartbeat-2.99.1
>> pacemaker-1.0.4
>
> You need at least corosync 1.1.1 and the latest pacemaker from
> me
On Wed, Oct 21, 2009 at 5:13 PM, Shravan Mishra
wrote:
> Hello guys,
>
> We are running
>
> corosync-1.0.0
> heartbeat-2.99.1
> pacemaker-1.0.4
You need at least corosync 1.1.1 and the latest pacemaker from
mercurial (even 1.0.5 is still too old)
___
P
Ya your missing the pacemaker lcrso file. Either you didn't build
pacemaker with corosync support or pacemaker didn't install that binary
in the proper place.
try:
updatedb
locate lcrso
Regards
-steve
On Wed, 2009-10-21 at 12:28 -0400, Shravan Mishra wrote:
> Steve, this is what my installatio
Steve, this is what my installation shows--
ls -l /usr/libexec/lcrso
-rwxr-xr-x 1 root root 101243 Jul 29 11:21 coroparse.lcrso
-rwxr-xr-x 1 root root 117688 Jul 29 11:21 objdb.lcrso
-rwxr-xr-x 1 root root 92702 Jul 29 11:54 openaisserviceenable.lcrso
-rwxr-xr-x 1 root root 110808 Jul 29
I recommend using corosync 1.1.1 - several bug fixes one critical for
proper pacemaker operation. It won't fix this particular problem
however.
Corosync loads pacemaker by searching for a pacemaker lcrso file. These
files are default installed in /usr/libexec/lcrso but may be in a
different loca
Hello guys,
We are running
corosync-1.0.0
heartbeat-2.99.1
pacemaker-1.0.4
the corosync.conf under /etc/corosync/ is
# Please read the corosync.conf.5 manual page
compatibility: whitetank
aisexec {
user: root
group: root
}
totem {
version: 2
secauth: o
