Dear all,
i'm facing problem in authenticating the other nodes, using fedora20 beta,
while implementing the cluster with the pacemaker.
details attached with mail.
*[root@pcmk-1 ~]# pcs cluster auth pcmk-1 pcmk-2 *
*pcmk-1: Already authorized *
*Unable to communicate with pcmk-2 *
Thanks Andreas . Its working.
On Fri, Dec 13, 2013 at 3:53 AM, Andreas Kurz wrote:
> On 2013-12-12 18:06, ESWAR RAO wrote:
> > Hi All,
> >
> > Can someone please help me in restarting all resources of clone on
> > single node.
> >
> > On 3 node setup with HB+pacemaker.
> > I have configured all
On 2013-12-12 17:53, Michael Böhm wrote:
> Hi @all,
>
> i am new to pacemaker and currently setting up a test-environment for
> future production-use. Unfortunately i ran into a problem with using the
> mysql resource agent and i'm hoping someone here can enlighten me.
>
> Server-Distro is Debian
On 2013-12-12 18:06, ESWAR RAO wrote:
> Hi All,
>
> Can someone please help me in restarting all resources of clone on
> single node.
>
> On 3 node setup with HB+pacemaker.
> I have configured all 3 resources in clone mode with max as 2 to start
> only on node1 and node2.
> ++
Hi All,
Can someone please help me in restarting all resources of clone on single
node.
On 3 node setup with HB+pacemaker.
I have configured all 3 resources in clone mode with max as 2 to start only
on node1 and node2.
+++
+ crm configure primitive res_dummy_1
Hi @all,
i am new to pacemaker and currently setting up a test-environment for
future production-use. Unfortunately i ran into a problem with using the
mysql resource agent and i'm hoping someone here can enlighten me.
Server-Distro is Debian and the resource-agents are far from up-to-date. I
wan
- Original Message -
> From: "Diego Remolina"
> To: "The Pacemaker cluster resource manager"
> Sent: Thursday, December 12, 2013 7:39:37 AM
> Subject: [Pacemaker] 1.1.10 problems on CentOS 6.5
>
> I was successfully running 1.1.8 on a pair of CentOS 6.4 servers and
> after updating to Ce
I was successfully running 1.1.8 on a pair of CentOS 6.4 servers and
after updating to CentOS 6.5 and 1.1.10, pacemaker miss-behaves.
The first symptoms appeared with the 1.1.10-14.el6 packages. About 20
hours after the upgrade, the first drbd_monitor issues came out.
Dec 09 18:50:12 Updated:
And why not include it?
https://github.com/beekhof/pacemaker/commit/a4bdc9a
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http:
On 11/12/13 00:48, Andrew Beekhof wrote:
On 10 Dec 2013, at 11:31 pm, Brian J. Murrell wrote:
On Tue, 2013-12-10 at 10:27 +, Christine Caulfield wrote:
Sadly you're not wrong.
That's what I was afraid of.
But it's actually no worse than updating
corosync.conf manually,
I think it
10 matches
Mail list logo