On 30/07/13 02:51, Andrew Beekhof wrote:
>> [k.proskurin@video-build libqb]$ ./autogen.sh
>> > autoreconf: Entering directory `.'
>> > autoreconf: configure.ac: not using Gettext
>> > autoreconf: running: aclocal -I m4
>> > configure.ac:4: error: Autoconf version 2.61 or higher is required
>> >
>>
On 29/07/2013, at 10:37 PM, Kirill Proskurin wrote:
> On 7/29/13 03:50 , Andrew Beekhof wrote:
>>
>> On 26/07/2013, at 8:20 PM, Kirill Proskurin wrote:
>>
>>> Hi!
>>>
>>> Is it RHEL5.x friendly?
>>
>> I'm assuming yes, as no-one complained during the 3 month release candidate
>> phase ;-)
Hi,
There is a bug already open:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697357
Kind regards,
Oriol
On 29/07/13 21:41, Jelle de Jong wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29/07/13 20:58, Arnold Krille wrote:
So further testing show that the bonded interfaces below
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29/07/13 20:58, Arnold Krille wrote:
> So further testing show that the bonded interfaces below seem to
> eat all broadcasts and all forwards (for the virtual machines).
> Don't know why yet. But as soon as I switched my network-config to
> use the
Am 2013-07-29 18:46, schrieb Arnold Krille:
Hi all,
I have a little problem here and would like to get some help:
I have (had?) a working three-node cluster of two active nodes
(nebel1 and nebel2) and one standby-node (nebel3) running debian
squeeze + backports. That is pacemaker 1.1.7-1~bpo60+
On 07/28/2013 08:12 PM, Andrew Beekhof wrote:
> On 28/07/2013, at 2:12 PM, Matthew O'Connor wrote:
>
>> On 07/23/2013 07:04 PM, Andrew Beekhof wrote:
>>> On 23/07/2013, at 12:32 AM, Matthew O'Connor wrote:
>>>
Hi Andrew,
On 07/19/2013 12:22 AM, Andrew Beekhof wrote:
>> I've ad
Hi all,
I have a little problem here and would like to get some help:
I have (had?) a working three-node cluster of two active nodes (nebel1
and nebel2) and one standby-node (nebel3) running debian squeeze +
backports. That is pacemaker 1.1.7-1~bpo60+1 and corosync
1.4.2-1~bpo60+1.
Now I up
On 7/29/13 03:50 , Andrew Beekhof wrote:
On 26/07/2013, at 8:20 PM, Kirill Proskurin wrote:
Hi!
Is it RHEL5.x friendly?
I'm assuming yes, as no-one complained during the 3 month release candidate
phase ;-)
Look like it's not.
[k.proskurin@video-build pacemaker]$ make release
sort: inva
Hello
That would say you have problem with your multicast :)
2013/7/29 Enric Muñoz
> Using unicast it is working well. Thank you very much.
>
> ** **
>
> *De:* Michael Schwartzkopff [mailto:mi...@clusterbau.com]
> *Enviado el:* lunes, 29 de julio de 2013 13:17
> *Para:* The Pacemaker cl
Using unicast it is working well. Thank you very much.
De: Michael Schwartzkopff [mailto:mi...@clusterbau.com]
Enviado el: lunes, 29 de julio de 2013 13:17
Para: The Pacemaker cluster resource manager
Asunto: Re: [Pacemaker] Pacemaker not starting in 2nd node of a 2 node cluster
Am Montag, 29. J
Am Montag, 29. Juli 2013, 10:49:46 schrieb Enric Muñoz:
> I only see the multicast packets in the node that is online but not in the
> other one. How can I configure corosync to use unicast??
Googlesays:
http://www.google.de/url?sa=t&rct=j&q=corosync%20udpu&source=web&cd=1&cad=rja&ved=0CDQQFjAA&ur
I only see the multicast packets in the node that is online but not in the
other one. How can I configure corosync to use unicast??
After enabling IGMP in the switch it appears a new message in the LCMC:
Could not initialize corosync configuration API error 6
Crm verify: Could not establish cib_
Am Montag, 29. Juli 2013, 10:06:29 schrieb Enric Muñoz:
> Iptables is disabled and selinux set to permissive in both nodes.
Do a tcpdump on both nodes. You should see the multicast packets as well as
some unicast packets to the udp port you defined. As fasr as I remember there
are three (or four
Hello
If you are using multicast check your igmp switch support is enabled.
Thanks
2013/7/29 Enric Muñoz
> Iptables is disabled and selinux set to permissive in both nodes.
>
> ** **
>
> *De:* Michael Schwartzkopff [mailto:mi...@clusterbau.com]
> *Enviado el:* lunes, 29 de julio de 2013
Iptables is disabled and selinux set to permissive in both nodes.
De: Michael Schwartzkopff [mailto:mi...@clusterbau.com]
Enviado el: lunes, 29 de julio de 2013 11:55
Para: The Pacemaker cluster resource manager
Asunto: Re: [Pacemaker] Pacemaker not starting in 2nd node of a 2 node cluster
Am Mo
Am Montag, 29. Juli 2013, 09:32:53 schrieb Enric Muñoz:
> Hi,
>
> It seems that the nodes don't see each other:
>
> # corosync-objctl | grep members
> runtime.totem.pg.mrp.srp.members.1275439296.ip=r(0) ip(192.168.5.204)
> runtime.totem.pg.mrp.srp.members.1275439296.join_count=1
> runtime.totem.p
Hi,
It seems that the nodes don't see each other:
# corosync-objctl | grep members
runtime.totem.pg.mrp.srp.members.1275439296.ip=r(0) ip(192.168.5.204)
runtime.totem.pg.mrp.srp.members.1275439296.join_count=1
runtime.totem.pg.mrp.srp.members.1275439296.status=joined
I can ping from one node to
Hello
You need configure stonith for your cluster.
Thanks
2013/7/29 Enric Muñoz
> Hi all,
>
> ** **
>
> I am trying to build a 2 node iSCSI HA storage cluster with Pacemaker,
> Corosync and DRBD on CentOS 6.4. I have problems while Building the
> cluster. The problem is that pacemaker is
Am Montag, 29. Juli 2013, 09:01:01 schrieb Enric Muñoz:
> Hi all,
>
> I am trying to build a 2 node iSCSI HA storage cluster with Pacemaker,
> Corosync and DRBD on CentOS 6.4. I have problems while Building the
> cluster. The problem is that pacemaker is not starting in the second node.
> When do
Hi all,
I am trying to build a 2 node iSCSI HA storage cluster with Pacemaker, Corosync
and DRBD on CentOS 6.4. I have problems while Building the cluster. The problem
is that pacemaker is not starting in the second node. When doing
corosync-cfgtool -s both nodes are active with no faults and
20 matches
Mail list logo
