Hi,
I am having an issue with Pacemaker on the cman stack where I can reliably
cause pacemaker to crash and coredump when I put the node in standby or
unstandby. Here is my messages log from when I do a unstandby like so "pcs
cluster unstandby `uname -n`":
Oct 18 18:33:11 localhost crmd[19258]:
On 18/10/13 07:00, Lars Marowsky-Bree wrote:
> On 2013-10-18T11:26:52, Nikola Ciprich wrote:
>
>> I'm using pacemaker-1.1.8 (RHEL6), fence-agents-4.0.3 (I compiled this myself
>> in order to use new netio stonith plugin), corosync-1.4.1, kernel-3.10.11 (in
>> case this would be important)
>
> Un
Hi, Andrew
Now, I am testing the configuration of one standby node and active node of 15.
About 10 Dummy resources are started per node.
If all the nodes are started with this composition, before all the
resources start, it will take the time for about 20 minutes.
And some resources have caused s
On 2013-10-18T11:26:52, Nikola Ciprich wrote:
> I'm using pacemaker-1.1.8 (RHEL6), fence-agents-4.0.3 (I compiled this myself
> in order to use new netio stonith plugin), corosync-1.4.1, kernel-3.10.11 (in
> case this would be important)
Unless 1.1.8-rhel has some fixes backported, I think you'd
Hi Lars,
ouch, I though I have to write all the versions and of course forgot at the
end :-( sorry about that
I'm using pacemaker-1.1.8 (RHEL6), fence-agents-4.0.3 (I compiled this myself
in order to use new netio stonith plugin), corosync-1.4.1, kernel-3.10.11 (in
case this would be important)
On 2013-10-18T11:04:26, Nikola Ciprich wrote:
> Hi,
>
> I'm still trying to get fencing working with dual power supply / node
> and either I'm blind to some dumb mistake of mine, or there's some
> nasty pacemaker bug..
To anticipate the next obvious question, what's your pacemaker version?
Re
Hi,
I'm still trying to get fencing working with dual power supply / node
and either I'm blind to some dumb mistake of mine, or there's some
nasty pacemaker bug..
I've set 4 stonith resources:
node1-st1-off ... action="off"
node1-st2-off ... action="off"
node1-st1-on ... action="on"
node1-st
