On 25 Feb 2014, at 2:18 am, Leon Fauster wrote:
> Am 24.02.2014 um 12:53 schrieb fatcha...@gmx.de:
>>
>> so the only solution is to migrate from openais to cman ? Is there a less
>> painful way?
>
> the "supported" solution is with cman, it does not mean that other stacks do
> not
> work, (
Am 24.02.2014 um 12:53 schrieb fatcha...@gmx.de:
>
> so the only solution is to migrate from openais to cman ? Is there a less
> painful way?
the "supported" solution is with cman, it does not mean that other stacks do
not
work, (to use your wording) there are just more "painful".
Check the
reff: Re: [Pacemaker] pacemaker/corosync on CentOS 6.4/6.5 node offline after update
On 21 Feb 2014, at 3:11 am, fatcha...@gmx.de wrote:
> Hi,
>
> Im using a pacemaker/corosync 2 node cluster on an CentOS 6.4 to provide a loadbalancer-service via pound.
> After a update with yum the updatet
On 21 Feb 2014, at 3:11 am, fatcha...@gmx.de wrote:
> Hi,
>
> Im using a pacemaker/corosync 2 node cluster on an CentOS 6.4 to provide a
> loadbalancer-service via pound.
> After a update with yum the updatet node is not able to work in the cluster
> again.
>
> Here is the cmr_mon and some
Hi,
Im using a pacemaker/corosync 2 node cluster on an CentOS 6.4 to provide a loadbalancer-service via pound.
After a update with yum the updatet node is not able to work in the cluster again.
Here is the cmr_mon and some facts about the updatet node powerpound:
Linux powerpound 2.6.
