[ClusterLabs] Antw: Re: Random failure with clone of IPaddr2
Ulrich Windl
Ulrich.Windl at rz.uni-regensburg.de
Tue Dec 20 02:19:51 EST 2016
>>> <alian at amisw.com> schrieb am 19.12.2016 um 20:37 in Nachricht
<e771b07e017c52d1fdd310d77a53cf93.squirrel at webmail2-int.amisw.com>:
>> 3 Nodes A B C.
>> If resource on:
>> A + B => ok
>> Only A => ok
>> Only B => ok
>> Only C => ok
>> A + C => random fail
>> B + C => random fail
>> A + B + C => random fail
>
> I use same corosync / pacemaker on three host, but:
> Host A & B have same kernel, C is different:
> A & B : 3.7.10-1.45-desktop
> C: 4.1.15-8-default
I don't know why you do that, but I'd either put C into standby, or put A nad B into standby and upgrade them one by one to the versions of C (undo standby after that). Your configuration makes troubleshooting a challenge (for you and others)!
Regards,
Ulrich
> I use same version, but no same binary:
> pacemaker-1.1.13-12.2.x86_64
> corosync-2.3.5-4.2.x86_64
> On C host it's native rpm. I use the src-rpm to rebuild it for host A & B.
> I check all the sysctl settings, but see no difference ...
>
>
>
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://lists.clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
More information about the Users
mailing list