Thanks Andrew for your input.
Andrew Beekhof writes:
>
> On Fri, Nov 23, 2012 at 11:47 PM, Parshvi wrote:
> > 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:
>
you should use stonith device for the server and configure stonith-enabled
to true to get the expected behavior of the resource failure.
On Fri, Nov 23, 2012 at 12:03 PM, Юлия Школьникова wrote:
> Hello, again. Why you didn't answer me? I so need your help!!
>
> Пересылаемое сообщение -
Could be a bug. crm_report?
On Tue, Nov 20, 2012 at 6:30 PM, Vladislav Bogdanov
wrote:
> Hi,
>
> Looking at pengine inputs (06229e9) I noticed that there are transient
> last-failure- attributes for resources last failed a long ago
> (more that 6 seconds).
>
> Example is:
>join="member" e
On Mon, Nov 26, 2012 at 11:37 AM, Pedro Sousa wrote:
> Hi,
>
> thank you for your answer.
>
> Do you think that if I increase the resource timeout that's failling it will
> solve the problem?
It couldn't hurt.
>
> Regards,
> Pedro Sousa
>
>
> On Mon, Nov 26, 2012 at 12:23 AM, Andrew Beekhof wro
Hi,
thank you for your answer.
Do you think that if I increase the resource timeout that's failling it
will solve the problem?
Regards,
Pedro Sousa
On Mon, Nov 26, 2012 at 12:23 AM, Andrew Beekhof wrote:
> On Wed, Nov 21, 2012 at 2:02 AM, Pedro Sousa wrote:
> > Hi all,
> >
> > some strange b
On Thu, Nov 15, 2012 at 6:35 PM, Carlos Luna wrote:
> Hello.
>
> I have a task that I can't seem to figure out how to implement in PaceMaker.
>
> I have two virtual ip resources and they are grouped together (colocated).
> They
> are initially started on node 1.
>
> I have a group of resources (
On Wed, Nov 21, 2012 at 2:02 AM, Pedro Sousa wrote:
> Hi all,
>
> some strange behavior is happening when I do some more intensive work on my
> cluster like running a bash script or wireshark, some pacemaker resources
> start to time out and fail back to the other node. I was running this
> script
On Fri, Nov 23, 2012 at 11:47 PM, Parshvi wrote:
> 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 re
On Wed, Nov 21, 2012 at 5:56 AM, Craig Donnelly wrote:
> Hi there,
>
> I think Ive exhausted everything I can find online in terms of trying to
> solve my problem so here goes with a posting to see if anyone on this mailing
> list might be able to help please.
>
> I have a pacemaker1.1.7/corosyn
