Hi
Because there was typo in pacemaker.spec.in, I was not able to register
service of pacemaker_remote.
-
diff --git a/pacemaker.spec.in b/pacemaker.spec.in
index 10296a5..1e1fd6d 100644
--- a/pacemaker.spec.in
+++ b/pacemaker.spec.in
@@ -404,7 +404,7 @@ exit 0
%
On 17/04/2013, at 4:02 PM, Oriol Mula-Valls wrote:
> On 16/04/13 06:10, Andrew Beekhof wrote:
>>
>> On 10/04/2013, at 3:20 PM, Oriol Mula-Valls wrote:
>>
>>> On 10/04/13 02:10, Andrew Beekhof wrote:
On 09/04/2013, at 7:31 PM, Oriol Mula-Valls
wrote:
> Thanks Andre
On 24/04/2013, at 7:44 PM, Rainer Brestan wrote:
> Pacemaker log of int2node2 with trace setting.
> https://www.dropbox.com/s/04ciy2g6dfbauxy/pacemaker.log?n=165978094
> On int2node1 (1.1.7) the trace setting did not create the pacemaker.log file.
>
Ah, yes, 1.1.7 wasn't so smart yet.
Can you
On 26/04/2013, at 9:12 PM, James Masson wrote:
>
>
> On 26/04/13 01:29, Andrew Beekhof wrote:
>>
>> On 26/04/2013, at 12:12 AM, James Masson wrote:
>>
>>>
>>> Hi list,
>>>
>>> I'm trying to build and run pacemaker from a custom location.
>>>
>>> Corosync starts up fine.
>>>
>>> Pacemake
On 26/04/2013, at 7:34 PM, Forum Registrant wrote:
> Hi!
>
> I have 2 node cluster. On each node I have mysql, nginx and php-fpm. Each
> node have it's own virtual IP. I need this virtual ip to migrate to other
> node if one of services (mysql/nginx/php-fpm) is down/stopped. How can I do
> i
On 19/04/2013, at 5:44 PM, Rasto Levrinc wrote:
> On Fri, Apr 19, 2013 at 9:11 AM, Alexandr A. Alexandrov
> wrote:
>> Hi Rasto,
>>
>> Note that on RHEL 6/CentOS 6, you should run the Pacemaker through CMAN and
>> not a Corosync plugin
>
> I wonder if that's still true,
Yes.
More so since t
On 20/04/2013, at 3:39 AM, Brian J. Murrell wrote:
> Given:
>
> host1# crm node attribute host1 show foo
> scope=nodes name=foo value=bar
>
> Why doesn't this return anything:
>
> host1# crm_attribute --node host1 --name foo --query
This is looking up transient attributes.
You need to add "
On 26/04/2013, at 7:05 PM, Grant Bagdasarian wrote:
> Hello,
>
> Let’s say I have three physical servers available to configure in a redundant
> way. I’m going to use two of the three servers to connect each to a different
> network. The one that is left over will be the fallback server for
On 18/04/2013, at 2:42 PM, Yuichi SEINO wrote:
> Hi,
>
> 2013/4/15 Andrew Beekhof :
>>
>> On 15/04/2013, at 3:38 PM, Yuichi SEINO wrote:
>>
>>> Hi,
>>>
>>> 2013/4/8 Andrew Beekhof :
I'm not 100% sure what the best approach is here.
Traditionally this is done with resource ag
On 16/04/2013, at 6:37 PM, ravindra.raut...@wipro.com wrote:
> Hi All,
> I have created cluster with these versions in fedora 17.
> pacemaker-1.1.7-2.fc17.x86_64
> corosync-2.0.0-1.fc17.x86_64
>
> Everything is working fine for me except resource stickiness.
>
> Any idea on this ?
On 23/04/2013, at 6:05 PM, T. wrote:
> Hi Devin,
>
> thank you very much for your answer.
>
>> If you insist on trying to do this with just the Linux-HA cluster,
>> I don't have any suggestions as to how you should proceed.
> I know that the "construct" we are building is quite complicated.
>
On 18/04/2013, at 5:58 PM, T. wrote:
> Hi,
>
>> Seems appropriate :)
>>
>>
>> http://blog.clusterlabs.org/blog/2009/configuring-heartbeat-v1-was-so-simple/
> "…because it couldn’t do anything."
>
> That might be true, but this was everything I needed the last years ...
You didn't need to k
On 26/04/2013, at 4:25 PM, Angel L. Mateo wrote:
> El 26/04/13 02:01, Andrew Beekhof escribió:
>>
>> On 24/04/2013, at 10:48 PM, Angel L. Mateo wrote:
>>
>>> Hello,
>>>
>>> I'm trying to configure a 2 node cluster in ubuntu with cman + corosync
>>> + pacemaker (the use of cman is becaus
On 29/04/2013, at 2:48 PM, Mark Williams wrote:
> Hi all,
>
> My two node cluster (qemu VMs, drbd) is now in quite a messy state.
>
> The problem started with a unresponsive qemu VM, which appeared to be
> caused by a libvertd problem/bug.
> Others said the solution was to kill & restart libve
On 30/04/2013, at 1:32 AM, Xavier Lashmar wrote:
> Hello Andrew,
>
> Thanks for your help. We've upgrade to pacemaker 1.1.9 and still have the
> same issue.
Thats a disappointing but useful data point.
>
> We are trying to get the core information but we are missing some debuginfo
> fil
Am Montag, 29. April 2013, 20:43:44 schrieb Michael Schwartzkopff:
> Am Montag, 29. April 2013, 18:37:08 schrieb Matchett, John:
> > My two node cluster has two virtual machines winA and winB which have the
> > config parameter config="/etc/libvirt/qemu/win01.xml A CRM configure
> > verify yield
Am Montag, 29. April 2013, 18:37:08 schrieb Matchett, John:
> My two node cluster has two virtual machines winA and winB which have the
> config parameter config="/etc/libvirt/qemu/win01.xml A CRM configure
> verify yields a warning about pacemaker violate uniqueness for parameter
> /etc/libvi
My two node cluster has two virtual machines winA and winB which have the
config parameter config="/etc/libvirt/qemu/win01.xml
A CRM configure verify yields a warning about pacemaker violate uniqueness for
parameter /etc/libvirt/qemu/win01.xml
Also the machines wont stay running. Could this
Hello Andrew,
Thanks for your help. We've upgrade to pacemaker 1.1.9 and still have the same
issue.
We are trying to get the core information but we are missing some debuginfo
files which we are trying to get our hands on. I'll try to forward this
information soon.
Is there something w
19 matches
Mail list logo
