Hi,
On Sun, Feb 27, 2011 at 05:18:22PM -0500, Vadym Chepkov wrote:
> Hi
>
> In pacemaker-1.0.10 I discovered a following issue:
>
> since "start" operation is not exactly reversal of "stop", I created an alias
> to remove target-role attribute.
> I have a naming pattern when a virtual machine i
Robert van Leeuwen writes:
Hi Arthur. My case is similar but I need a little extra help.
> > I have two nodes.
> >
> > Node1 (192.168.0.1)
> > Node2 (192.168.0.2)
> >
> > I want a failover ipaddress (192.168.0.3), so that when Node1 is up it has
> > eth0:0 with 192.168.0.3.
> > And if Node1
Dear all,
i have read the clusterbook, but i have not understand how can i
configure example three services so that if one service failed, all
three services switch to another node.
Example:
primitive ServiceAmavis lsb:amavis op monitor interval="10" timeout="20s"
primitive ServiceApache lsb:apa
-Original message-
To: pacema...@clusterlabs.org;
From: florin
Sent: Mon 28-02-2011 11:25
Subject:Re: [Pacemaker] Help for my first test
> Now I have the following question
> How would look the commands to set up this three IP's (especially I need a bit
> more explanations
> The question is, is it possible to all server to be part of the same
> cluster with completely different roles running completly different
> services, all managed by the same corosync settings. Then i would never
> lose quorum.
Arthur,
Yes, you can combine different resources in a single cluste
Hi,
On 02/28/2011 02:00 PM, Thomas Elsäßer wrote:
Dear all,
i have read the clusterbook, but i have not understand how can i
configure example three services so that if one service failed, all
three services switch to another node.
Example:
primitive ServiceAmavis lsb:amavis op monitor interv
On Mon, 28 Feb 2011 13:00:04 +0100, Thomas Elsäßer
wrote:
> i have read the clusterbook, but i have not understand how can i
> configure example three services so that if one service failed, all
> three services switch to another node.
I'd set up a group for that.
As an alternative, you could
Hi!
I still suffer the problem, that the fail-count is not cleared after
failure-timeout. After the second failure of Kamailio the IP-address is
moved to the other node, and restarted on the previous node after
failure-timeout.
But as the fail-count is not cleared, subsequent failures will cause
Hello,
I tried to stick a group fixed to one node, but if the service
corosync is stopped the group is jumping to the next node.
Here is my configuration:
How I can configure that behavior that my group is running only in
that specific host ?
regards,
Thomas
Folks -
I have a configuration issue that I am unsure how to resolve. Consider the
following set of resources.
clone rsc1-clone rsc1 \
meta clone-max="2" target-role="Started"
primitive rsc1 ...
primitive rsc2 ... meta resource-stickiness="1"
primitive rsc3 ... meta resource-stickiness="1"
P
On Mon, Feb 28, 2011 at 07:59:30PM +0100, Thomas Baumann wrote:
> Hello,
>
> I tried to stick a group fixed to one node, but if the service
> corosync is stopped the group is jumping to the next node.
>
> Here is my configuration:
>
> score="INFINITY"/>
>
> How I can configure that behavior th
I'm looking for a simple way to disable failover, i.e. prevent
Pacemaker from migrating resources due to node or resource failures.
Simple meaning that I can easily revert back to the previous state
with failover enabled without modifying all the resources, for
example.
Barring that I'd like a way
Alan,
Have you tried this command?
# crm configure property maintenance-mode=true
I have used this when I don't want Pacemaker to react to a monitor failing such
as when I run gdb on a process.
Thanks,
Bob
- Original Message
From: Alan Jones
To: The Pacemaker cluster resource mana
On Feb 28, 2011, at 3:52 AM, Dejan Muhamedagic wrote:
> Hi,
>
> On Sun, Feb 27, 2011 at 05:18:22PM -0500, Vadym Chepkov wrote:
>> Hi
>>
>> In pacemaker-1.0.10 I discovered a following issue:
>>
>> since "start" operation is not exactly reversal of "stop", I created an
>> alias to remove targe
On Feb 28, 2011, at 7:38 PM, Bob Schatz wrote:
> Alan,
>
> Have you tried this command?
>
> # crm configure property maintenance-mode=true
>
> I have used this when I don't want Pacemaker to react to a monitor failing
> such
> as when I run gdb on a process.
>
I usually use
crm configure
15 matches
Mail list logo