On 04/15/2016 12:29 PM, Digimer wrote:
> That is what I assumed. Sorry, at a trade show so I'm reading and
> replying quickly.
I didn't spell it out, but that would be too easy.
However, it's not happening today. My guess is it was somehow caused by
DRBD being in inconsistent state: I didn't
On 04/15/2016 04:59 PM, Dmitri Maziuk wrote:
> On 2016-04-15 07:46, Klaus Wenninger wrote:
>
>> Which IP-address did you use to ssh to that box? One controlled
>> by pacemaker and possibly being migrated or a fixed one assigned
>> to that box?
>
> Good try but no: the "sunken" (as opposed to
On 2016-04-15 07:46, Klaus Wenninger wrote:
Which IP-address did you use to ssh to that box? One controlled
by pacemaker and possibly being migrated or a fixed one assigned
to that box?
Good try but no: the "sunken" (as opposed to floating ;) address of course.
If what digimer says is true,
On 04/15/2016 02:22 PM, Digimer wrote:
> On 14/04/16 05:38 PM, Dimitri Maziuk wrote:
>> Hi all,
>>
>> I've an up to date centos 7 w/ pcs + corosync + pacemaker active-passive
>> cluster running drbd (8.4) and apache. It's all working fine except when
>> I trigger a fail-over, my ssh connection to
On 14/04/16 05:38 PM, Dimitri Maziuk wrote:
> Hi all,
>
> I've an up to date centos 7 w/ pcs + corosync + pacemaker active-passive
> cluster running drbd (8.4) and apache. It's all working fine except when
> I trigger a fail-over, my ssh connection to active (being demoted) node
> gets cut.
>
>
Hi all,
I've an up to date centos 7 w/ pcs + corosync + pacemaker active-passive
cluster running drbd (8.4) and apache. It's all working fine except when
I trigger a fail-over, my ssh connection to active (being demoted) node
gets cut.
Am I missing something or is this an expected behaviour of
