On 17/04/2013, at 3:19 AM, pavan tc wrote:
> On Fri, Apr 12, 2013 at 9:27 AM, pavan tc wrote:
> > Absolutely none in the syslog. Only the regular monitor logs from my
> > resource agent which continued to report as secondary.
>
> This is very strange, because the thing that caused the I_PE_CA
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 Andrew I've managed to set up the system and currently I have it working
but still on testing.
On 10/04/2013, at 2:21 PM, Andrei Belov wrote:
>
> On Apr 10, 2013, at 2:06 , Andrew Beekhof wrote:
>
>>
>> On 09/04/2013, at 4:13 PM, Andrei Belov wrote:
>>
>>> Hello pacemaker users,
>>>
>>> I noticed that neither "-p" nor "-f" option does not make any sense for
>>> pacemakerd -
>>> pi
Hi Chris,
just seen in the github repo - which I found after posting here -
that you made a fix.
Thank you for the very fast reaction.
Best regards
Andreas
-Ursprüngliche Nachricht-
Von: Chris Feist [mailto:cfe...@redhat.com]
Gesendet: Mittwoch, 17. April 2013 00:34
An: The Pacemaker c
On 15/04/2013, at 7:08 PM, Pavlos Parissis wrote:
> Hoi,
>
> I upgraded 1st node and here are the logs
> https://dl.dropboxusercontent.com/u/1773878/pacemaker-issue/node1.debuglog
> https://dl.dropboxusercontent.com/u/1773878/pacemaker-issue/node2.debuglog
>
> Enabling tracing on the mentioned
Hi Chris,
I would like to see something where you can start your
pacemaker configuration (only) from scratch.
In a way, so that you know nothing is left (constraints, etc.).
Best regards
Andreas
-Ursprüngliche Nachricht-
Von: Chris Feist [mailto:cfe...@redhat.com]
Gesendet: Mittwoch, 1
On 11/04/2013, at 7:23 PM, Kazunori INOUE wrote:
> Hi Andrew,
>
> (13.04.08 12:01), Andrew Beekhof wrote:
>>
>> On 27/03/2013, at 7:45 PM, Kazunori INOUE
>> wrote:
>>
>>> Hi,
>>>
>>> I'm using pacemaker-1.1 (c7910371a5. the latest devel).
>>>
>>> When fencing failed 10 times, S_TRANSITION
This should solve your issue:
https://github.com/beekhof/pacemaker/commit/dbbb6a6
On 11/04/2013, at 7:23 PM, Kazunori INOUE wrote:
> Hi Andrew,
>
> (13.04.08 11:04), Andrew Beekhof wrote:
>>
>> On 05/04/2013, at 3:21 PM, Kazunori INOUE
>> wrote:
>>
>>> Hi,
>>>
>>> When fencing fai
On 17/04/2013, at 11:28 AM, Daniel Bareiro wrote:
> Ho Andrew.
>
> On Monday, 15 April 2013 14:36:48 +1000,
> Andrew Beekhof wrote:
>
>>> I'm testing Pacemaker+Corosync cluster with KVM virtual machines. When
>>> restarting a node, I got the following status:
>>>
>>> # crm status
>>>
Ho Andrew.
On Monday, 15 April 2013 14:36:48 +1000,
Andrew Beekhof wrote:
> > I'm testing Pacemaker+Corosync cluster with KVM virtual machines. When
> > restarting a node, I got the following status:
> >
> > # crm status
> >
> > Last updated: Sun Apr 14 11:50:00 2013
> > Last change
On 04/14/13 02:52, Andreas Mock wrote:
Hi all,
can someone tell me what the pcs equivalent to
crm configure erase is?
From my understanding, 'crm configure erase' will remove everything from the
configuration file except for the nodes.
Are you trying to clear your configuration out and sta
On 17/04/2013, at 8:33 AM, Chris Feist wrote:
> On 04/16/13 06:46, Andreas Mock wrote:
>> Hi all,
>>
>> as I don't really know, where to address this
>> issue, I do post it here. On the one handside
>> as an information for guys scripting with the
>> help of 'pcs' and on the other handside with
On 04/16/13 06:46, Andreas Mock wrote:
Hi all,
as I don't really know, where to address this
issue, I do post it here. On the one handside
as an information for guys scripting with the
help of 'pcs' and on the other handside with
the hope that one maintainer is listening
and will have a look at
Hi,
On Tue, Apr 09, 2013 at 08:23:43PM +, Xavier Lashmar wrote:
> Hi,
>
> I am investigating XML parsing errors appearing in my
> /var/log/cluster/corosync.log files. While doing so, I've been using the crm
> tool to 'view' my configuration and I get the following interesting errors:
>
>
On Fri, Apr 12, 2013 at 9:27 AM, pavan tc wrote:
> > Absolutely none in the syslog. Only the regular monitor logs from my
> resource agent which continued to report as secondary.
>
>>
>> This is very strange, because the thing that caused the I_PE_CALC is a
>> timer that goes off every 15 minutes
Hi Rastislav,
thank you for your hints.
In this case, only to rely on pcs, I could
probably use the following to get the list
of resources:
pcs resource show --all | perl -M5.010 -ane 'say $F[1] if $F[0] eq
"Resource:"'
Best regards
Andreas Mock
-Ursprüngliche Nachricht-
Von: Rasto L
Hi Ivor,
I don't know whether I understand you completely right:
If you want independence of resources don't put them into a group.
Look at
http://clusterlabs.org/doc/en-US/Pacemaker/1.1-plugin/html/Pacemaker_Explain
ed/ch10.html
A group is made to tie together several resources with
Hi guys,
I need some help with pacemaker configuration, it is all new to me and can't
find solution...
I have two-node HA environment with services that I want to be partially
independent, in pacemaker/heartbeat configuration.
There is active/active sip service with two floating IPs, it should
Hi all,
as I don't really know, where to address this
issue, I do post it here. On the one handside
as an information for guys scripting with the
help of 'pcs' and on the other handside with
the hope that one maintainer is listening
and will have a look at this.
Problem: When cluster is down a 'p
On Tue, Apr 16, 2013 at 9:38 AM, Andreas Mock wrote:
> Hi all,
>
> I try to bring that topic up once again because
> it's still unresolved for me:
>
> a) How can I do the equivalent of 'crm configure erase'
> in pcs? Is there a way?
>
> b) If I can't do it woith pcs, is there a reliable
> and secu
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 ?
Regards,
Rauthan
Please do not print this email unless it is absolutely
yea, that's what i meant by edit CIB&cluster.conf by hands
however, two problems with it:
1. it requires restart of cman on each node to "forget" expelled node
after cluster.conf edit
2. after editing CIB (removing all entries belonging to expelled node)
and replacing CIB via "pcs cluster push
http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html-single/Pacemaker_Explained/index.html#_options_2
example 2.4
# cibadmin --query > tmp.xml
# vi tmp.xml
# cibadmin --replace --xml-file tmp.xml
- Original Message -
> Hi,
>
> Can anyone point me to the correct procedure of addin
Hi,
Can anyone point me to the correct procedure of adding/removing node
to/from cluster in cman+pacemaker stack, preferably without stopping
whole cluster?
"pcs cluster node add|remove" doesn't work, as there's no "pcsd" daemon
in centos6.4; cman tools (cman_tool, ccs_tool, ccs_sync) - doesn'
Hi all,
I try to bring that topic up once again because
it's still unresolved for me:
a) How can I do the equivalent of 'crm configure erase'
in pcs? Is there a way?
b) If I can't do it woith pcs, is there a reliable
and secure way to do it with pacemaker low level tools?
Thank you in advance.
25 matches
Mail list logo