Hi,
We have a two node cluster setup, running the following versions:
cluster-glue-1.0.6
resource-agents-1.0.4
pacemaker-1.1.8
corosync-1.4.1
libaio-devel-0.3.106
libibverbs-1.1.3
libqb-0.14.2
librdmacm-1.0.10
libtool-ltdl-1.5.22
pacemaker-cli-1.1.8
pacemaker-cluster-libs-1.1.8
pacemaker-libs-1.1.8
Lars Marowsky-Bree writes:
>
> On 2013-01-04T04:24:26, Parshvi wrote:
>
> > Hi Andrew,
> > As suggested by you in ref. to bug id:5124 we have deployed Pacemaker 1.1.8.
> > We have been facing major issues:
> >
> > 1) lrmadmin fails to work with the following error:
> > WARN: lrm_signon: can n
So we use old version of pacemaker? What version should we update to?
On 01/04/2013 11:57 AM, Andrew Beekhof wrote:
> On Fri, Jan 4, 2013 at 8:30 PM, Michal Fiala wrote:
>> Hallo,
>>
>> thanks for information. We are using corosync-1.4.4 and
>> pacemaker-1.1.6.1.
>
> Oh, thats the old lrmd. In
On Fri, Jan 4, 2013 at 8:30 PM, Michal Fiala wrote:
> Hallo,
>
> thanks for information. We are using corosync-1.4.4 and
> pacemaker-1.1.6.1.
Oh, thats the old lrmd. In which case your original assessment could
well be correct.
> Pacemaker is started as a modul by corosync.
>
> corosync loggin
On Fri, Jan 4, 2013 at 4:27 PM, Vladislav Bogdanov wrote:
> 04.01.2013 06:07, Andrew Beekhof wrote:
>> On Wed, Dec 19, 2012 at 7:33 PM, Vladislav Bogdanov
>> wrote:
>>> Hi all,
>>>
>>> I'd like to share my successful attempt to confine pacemaker.
>>>
>>> I took pacemaker module barebone found in
On 2013-01-04T04:24:26, Parshvi wrote:
> Hi Andrew,
> As suggested by you in ref. to bug id:5124 we have deployed Pacemaker 1.1.8.
> We have been facing major issues:
>
> 1) lrmadmin fails to work with the following error:
> WARN: lrm_signon: can not initiate connection
> lrmd is not running.
>
Hallo,
thanks for information. We are using corosync-1.4.4 and
pacemaker-1.1.6.1. Pacemaker is started as a modul by corosync.
corosync loggin option:
logging {
fileline: off
to_stderr: no
to_logfile: no
logfile: /var/log/corosync.log
to_syslog: yes
