Parshvi writes:
>
> Hi,
> We are upgrading to Pacemaker 1.1.7 and Corosync 1.4.3.
> The previous version was:
> Pacemaker: 1.0.12
> Corosync : 1.2.7
> The issues faced in the older version are:
> 1) Numerous, Policy engine and crmd crashes, stopping failed cluster
> resources
> from recovering
Hi,
We are upgrading to Pacemaker 1.1.7 and Corosync 1.4.3.
The previous version was:
Pacemaker: 1.0.12
Corosync : 1.2.7
The issues faced in the older version are:
1) Numerous, Policy engine and crmd crashes, stopping failed cluster resources
from recovering.
2) pacemaker logs show FSM in pending
Ive finally managed to resolve this issue by rejigging the iSCSI resources
agents.
I've reduced the number of iSCSI target resources which then allowed me to
remove the use of groups.
The following config is now stable for me.
node cs1san1 \
attributes standby="off"
node cs1san2 \
On 22/11/12 14:37 +0300, Vladislav Bogdanov wrote:
22.11.2012 14:18, Angus Salkeld wrote:
On 22/11/12 11:48 +1100, Andrew Beekhof wrote:
On Tue, Nov 20, 2012 at 5:32 PM, Vladislav Bogdanov
wrote:
Hi,
Running 06229e9 with qb 0.14.3, and noticed following assert() in trace
logging path:
#0 0
