Re: [Pacemaker] Managing DRBD Dual Primary with Pacemaker always initial Split Brains

2014-10-07 Thread Andrew Beekhof
On 8 Oct 2014, at 9:20 am, Felix Zachlod wrote: > Hello Andrew, > > Am 06.10.2014 04:30, schrieb Andrew Beekhof: >> >> On 3 Oct 2014, at 5:07 am, Felix Zachlod wrote: >> >>> Am 02.10.2014 18:02, schrieb Digimer: On 02/10/14 02:44 AM, Felix Zachlod wrote: > I am currently running 8.4

Re: [Pacemaker] Managing DRBD Dual Primary with Pacemaker always initial Split Brains

2014-10-07 Thread Felix Zachlod
Hello Andrew, Am 06.10.2014 04:30, schrieb Andrew Beekhof: On 3 Oct 2014, at 5:07 am, Felix Zachlod wrote: Am 02.10.2014 18:02, schrieb Digimer: On 02/10/14 02:44 AM, Felix Zachlod wrote: I am currently running 8.4.5 on to of Debian Wheezy with Pacemaker 1.1.7 Please upgrade to 1.1.10+!

Re: [Pacemaker] Managing DRBD Dual Primary with Pacemaker always initial Split Brains

2014-10-05 Thread Andrew Beekhof
On 3 Oct 2014, at 5:07 am, Felix Zachlod wrote: > Am 02.10.2014 18:02, schrieb Digimer: >> On 02/10/14 02:44 AM, Felix Zachlod wrote: >>> I am currently running 8.4.5 on to of Debian Wheezy with Pacemaker 1.1.7 >> >> Please upgrade to 1.1.10+! >> > > Are you referring to a special bug/ code c

Re: [Pacemaker] Managing DRBD Dual Primary with Pacemaker always initial Split Brains

2014-10-02 Thread Felix Zachlod
Am 02.10.2014 18:02, schrieb Digimer: On 02/10/14 02:44 AM, Felix Zachlod wrote: I am currently running 8.4.5 on to of Debian Wheezy with Pacemaker 1.1.7 Please upgrade to 1.1.10+! Are you referring to a special bug/ code change? I normally don't like building all this stuff from source in

Re: [Pacemaker] Managing DRBD Dual Primary with Pacemaker always initial Split Brains

2014-10-02 Thread Digimer
On 02/10/14 02:44 AM, Felix Zachlod wrote: I am currently running 8.4.5 on to of Debian Wheezy with Pacemaker 1.1.7 Please upgrade to 1.1.10+! -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? __

Re: [Pacemaker] Managing DRBD Dual Primary with Pacemaker always initial Split Brains

2014-10-02 Thread Felix Zachlod
Am 02.10.2014 09:01, schrieb Felix Zachlod: Am 02.10.2014 08:44, schrieb Felix Zachlod: Am 01.10.2014 20:46, schrieb Digimer: At some point along the way, both nodes were Primary while not connected, even if for just a moment. Your log snippet above shows the results of this break, they do not

Re: [Pacemaker] Managing DRBD Dual Primary with Pacemaker always initial Split Brains

2014-10-02 Thread Felix Zachlod
Am 02.10.2014 08:44, schrieb Felix Zachlod: Am 01.10.2014 20:46, schrieb Digimer: At some point along the way, both nodes were Primary while not connected, even if for just a moment. Your log snippet above shows the results of this break, they do not appear to speak to the break itself. Even

Re: [Pacemaker] Managing DRBD Dual Primary with Pacemaker always initial Split Brains

2014-10-01 Thread Felix Zachlod
Am 01.10.2014 20:46, schrieb Digimer: At some point along the way, both nodes were Primary while not connected, even if for just a moment. Your log snippet above shows the results of this break, they do not appear to speak to the break itself. Even easier to reproduce is the problem when I try

Re: [Pacemaker] Managing DRBD Dual Primary with Pacemaker always initial Split Brains

2014-10-01 Thread Digimer
On 01/10/14 02:21 PM, Felix Zachlod wrote: Hello! I'm currently experimenting how a good DRBD Dual Primary Setup can be achieved with Pacemaker. I know all of the "you have to have good fencing in place things" ... that is just what I'am currently trying to test in my setup beside other things.

[Pacemaker] Managing DRBD Dual Primary with Pacemaker always initial Split Brains

2014-10-01 Thread Felix Zachlod
Hello! I'm currently experimenting how a good DRBD Dual Primary Setup can be achieved with Pacemaker. I know all of the "you have to have good fencing in place things" ... that is just what I'am currently trying to test in my setup beside other things. But even without a node crashing or the