On 26/07/2013, at 10:44 AM, Tan Tai hock wrote:
> Ops sorry for providing the wrong version number. I am using Corosync 2.3.0-1
> and Pacemaker 1.1.9-8. What should be done to clear the resources properly
> that are still running in the event that pacemaker isn't running?
Configure fencing.
Ops sorry for providing the wrong version number. I am using Corosync
2.3.0-1 and Pacemaker 1.1.9-8. What should be done to clear the resources
properly that are still running in the event that pacemaker isn't running?
On Thu, Jul 25, 2013 at 10:39 AM, Andrew Beekhof wrote:
>
> On 24/07/2013, a
On 24/07/2013, at 6:40 PM, Tan Tai hock wrote:
>
> I did not enable fencing. I observe the process running and see that when the
> node is up, I will see the following processes:
>
> Corosync
> --
> /usr/sbin/corosync
>
> Pacemaker
> -
> /usr/libexec/pacemaker/lrm
I did not enable fencing. I observe the process running and see that when
the node is up, I will see the following processes:
Corosync
--
/usr/sbin/corosync
Pacemaker
-
/usr/libexec/pacemaker/lrmd
/usr/libexec/pacemaker/pengine
pacemakerd
/usr/libexec/pacemaker/stonith
On 24/07/2013, at 9:54 AM, Tan Tai hock wrote:
> No I did not. It seems like corosync and pacemaker stop running when the
> network connection is lost.
Do you have fencing enabled?
If not, I'd be surprised if corosync or pacemaker stopped running.
> I am trying to simulate a scenario whereby
No I did not. It seems like corosync and pacemaker stop running when the
network connection is lost. I am trying to simulate a scenario whereby a
node which started the resource loses network connection and observe how it
reacts upon joining back the cluster. Is there any proper way to shutdown
bot
On 23/07/2013, at 11:28 AM, Tan Tai hock wrote:
> Hi,
>
> I have currently set up 3 machines with Pacemaker 2.3 with Corosync 1.19. I
> have tested some scenarios and have encountered some problem which I hope to
> get some advice on.
>
> My scenario is as follows:
>
> The 3 machines, name
Hi,
I have currently set up 3 machines with Pacemaker 2.3 with Corosync 1.19. I
have tested some scenarios and have encountered some problem which I hope
to get some advice on.
My scenario is as follows:
The 3 machines, name A,B,C are all running with A being the node which
started the resource
