03.09.2013 07:04, Digimer wrote:
...
To solve problem 1, you can set a delay against one of the nodes. Say
you set the fence primitive for node 01 to have 'delay=15'. When node
1 goes to fence node 2, it starts immediately. When node 2 starts to
fence node 1, it sees the 15 second delay and
On 03/09/13 14:14, Vladislav Bogdanov wrote:
03.09.2013 07:04, Digimer wrote:
...
To solve problem 1, you can set a delay against one of the nodes. Say
you set the fence primitive for node 01 to have 'delay=15'. When node
1 goes to fence node 2, it starts immediately. When node 2 starts to
On 2013-09-03T21:14:02, Vladislav Bogdanov bub...@hoster-ok.com wrote:
To solve problem 2, simply disable corosync/pacemaker from starting on
boot. This way, the fenced node will be (hopefully) back up and running,
so you can ssh into it and look at what happened. It won't try to rejoin
03.09.2013 21:45, Digimer wrote:
On 03/09/13 14:14, Vladislav Bogdanov wrote:
03.09.2013 07:04, Digimer wrote:
...
To solve problem 1, you can set a delay against one of the nodes. Say
you set the fence primitive for node 01 to have 'delay=15'. When node
1 goes to fence node 2, it starts
03.09.2013 21:36, Lars Marowsky-Bree wrote:
On 2013-09-03T21:14:02, Vladislav Bogdanov bub...@hoster-ok.com wrote:
To solve problem 2, simply disable corosync/pacemaker from starting on
boot. This way, the fenced node will be (hopefully) back up and running,
so you can ssh into it and look
I've got a very simple question which I suspect betrays my lack of
understanding of something basic. Could someone help me understand?
If I have a two-node Pacemaker cluster - say, a really simple cluster
of two nodes, A B, with a solitary network connection between them -
then I have to set
On 02/09/13 23:23, Alex Sudakar wrote:
I've got a very simple question which I suspect betrays my lack of
understanding of something basic. Could someone help me understand?
If I have a two-node Pacemaker cluster - say, a really simple cluster
of two nodes, A B, with a solitary network
