On 25/03/14 01:55 AM, 邓尧 wrote:
Thanks for the detailed explanation.
We do have network failover setup, so completely network failure is
unlikely. Still, I removed acpid, just in case.
Thank you again.
Happy to help!
Of course, "unlikely" is rarely good enough in the HA world. So I am
glad
Thanks for the detailed explanation.
We do have network failover setup, so completely network failure is
unlikely. Still, I removed acpid, just in case.
Thank you again.
On Tue, Mar 25, 2014 at 11:47 AM, Digimer wrote:
> On 24/03/14 11:45 PM, Digimer wrote:
>
>> Consider a fence-loop or an er
On 24/03/14 11:45 PM, Digimer wrote:
Consider a fence-loop or an errant command rebooting the stack
Sorry, that should have read "Consider a switch-loop (causing a packet
storm) or an errant command rebooting the stack"
I need more coffee. >_>
--
Digimer
Papers and Projects: https://alteeve
Hi 邓尧,
This question requires a little longer answer.
The delay that Kristoffer talks about is where you set one node to
wait a certain number of seconds before fencing the other node. In the
opposite direction, the other node does not wait to fence, so in the
case where both nodes try to
Hello,
I did upgrade to 1.1.10 which was available in Debian SID (unstable).
Altough it fixed issues with stonith it introduces another problems.
When I had both nodes UP and did power off on one of them (lets call it
"A") another node (lets call it "B") shut down crmd.
When going trough logs I f
How much time delay difference is enough ? I'm currently setting the delays
at 5s and 15s, dual fencing does disappear, but I'm sure whether the
difference is large enough for all situations.
On Mon, Mar 24, 2014 at 8:00 PM, Kristoffer Grönlund wrote:
> On Mon, 24 Mar 2014 19:41:16 +0800
> 邓尧 w
Hi all,
I'm using pcs 0.9.115 on fedora 20.
---
[root@saturn ~]# pcs --version
0.9.115
[root@saturn ~]# cat /etc/redhat-release
Fedora release 20 (Heisenbug)
---
I want to add locational rule property "boolean-op" using pcs,
but this pcs seems it does not be implemented...
---
[root@saturn ~]#
On Mon, 24 Mar 2014 20:01:25 +0100
Alexandre wrote:
> Hi,
>
> I am configuring a cluster on nodes that doesn't have pcs installed
> (pacemaker 1.1.7 with crmsh).
> I would like to configure collocated sets of resources (as show
> here:http://clusterlabs.org/doc/en-US/Pacemaker/1.1-plugin/html-si
Greetings,
I am getting closer to what I need.
I am having trouble figuring out a rule for p_VIPeth1_1 that will cause it's
score to be -inf if p_R_NODE1 is not running.Here is the rule that I am
struggling with.
location p_VIPeth1_1_loc2 p_VIPeth1_1 \ rule $id="p_VIPeth1_1_loc2-rule" -inf:
p_
Hi,
I am configuring a cluster on nodes that doesn't have pcs installed
(pacemaker 1.1.7 with crmsh).
I would like to configure collocated sets of resources (as show
here:http://clusterlabs.org/doc/en-US/Pacemaker/1.1-plugin/html-single/Pacemaker_Explained/#s-resource-sets-collocation)
in that clu
Actually, I was wrong, the version used is 1.1.10.
So, how I can know which process is taking so long?
thanks
On 3/23/14, 7:35 PM, "Andrew Beekhof" wrote:
>
>On 21 Mar 2014, at 3:57 am, Drapeau, Mathieu
>wrote:
>
>> Hello,
>> From pacemaker 1.1.8-7 from EL6, crmd died unexpected generating thi
On Mon, 24 Mar 2014 19:41:16 +0800
邓尧 wrote:
> I'm configuring a 2-node cluster on CentOS 6 with corosync +
> pacemaker + cman. Everything works well except fencing.
>
> I'm using IPMI as the fencing device, I know it's not the best fencing
> device, but this is the only option I have.
> Manual
Hi Andrew,
thank you for your answer. I found that blog entry before.
I'm pretty sure I'm too stupid to get my information out
of that blog entry.
You write there:
"[...] If the level of detail in the cluster log file is still insufficient,
or you simply wish to go blind, you can turn on debuggi
I'm configuring a 2-node cluster on CentOS 6 with corosync + pacemaker +
cman. Everything works well except fencing.
I'm using IPMI as the fencing device, I know it's not the best fencing
device, but this is the only option I have.
Manual fencing a node (pcs stonith fence ) works well: peer node g
but it will be implemented?
2014-03-24 2:22 GMT+01:00 Andrew Beekhof :
>
> On 24 Mar 2014, at 11:04 am, emmanuel segura wrote:
>
> > how can i turn off the debug without reboot the pacemaker?
>
> you cant.
>
> >
> >
> > 2014-03-24 0:36 GMT+01:00 Andrew Beekhof :
> >
> > On 20 Mar 2014, at 11:24
On Friday, March 21, 2014 08:59:27 pm David Vossel wrote:
>
> This could be a pcs bug. If using --force works, this is definitely a pcs
> bug. pcs is supposed to be looking through /etc/init.d/* on the local
> machine for valid lsb scripts before applying a lsb resource into the cluster
> conf
Hi,
We have a 2-node Pacemaker (1.1.7 on Fedora Core 16) cluster that runs a
PostgreSQL database on a DRBD drive, Apache, Tomcat and a few custom
services. The load is pretty low (a few HTTP clients, a few database
clients, infrequent database updates - every hour or so). It worked
perfectly f
Am 19.03.2014 14:39, schrieb Jan Friesse:
Stephan Buchner napsal(a):
Hm, i tried recompiling all three packages (libqb, corosync and
pacemaker), using versions which have been marked stable by the gentoo
project.
I used the following versions: libqb = 0.14.4
18 matches
Mail list logo