On 2018-06-21 03:57 AM, facebook wrote:
> Dear All,
>
> I found a couple of issues in this page:
>
> https://clusterlabs.org/quickstart-redhat.html
>
> but I'm not sure if this mailing list is the right place to highlight
> it. Sorry if it's not.
>
> Best Regards,
>
> Mario.
Here is
Dear All,
I found a couple of issues in this page:
https://clusterlabs.org/quickstart-redhat.html
but I'm not sure if this mailing list is the right place to highlight it.
Sorry if it's not.
Best Regards,
Mario.
___
Users mailing
Hi,
Here the log:
corosync.log
Description: Binary data
> On 22 Jun 2018, at 12:10, Christine Caulfield wrote:
>
> On 22/06/18 10:39, Salvatore D'angelo wrote:
>> Hi,
>>
>> Can you tell me exactly which log you need. I’ll provide you as soon as
>> possible.
>>
>> Regarding some settings,
On 22/06/18 10:39, Salvatore D'angelo wrote:
> Hi,
>
> Can you tell me exactly which log you need. I’ll provide you as soon as
> possible.
>
> Regarding some settings, I am not the original author of this cluster. People
> created it left the company I am working with and I inerithed the code
Hi,
Can you tell me exactly which log you need. I’ll provide you as soon as
possible.
Regarding some settings, I am not the original author of this cluster. People
created it left the company I am working with and I inerithed the code and
sometime I do not know why some settings are used.
The
On 22/06/18 10:14, Salvatore D'angelo wrote:
> Hi Christine,
>
> Thanks for reply. Let me add few details. When I run the corosync
> service I se the corosync process running. If I stop it and run:
>
> corosync -f
>
> I see three warnings:
> warning [MAIN ] interface section bindnetaddr is
Hi Christine,
Thanks for reply. Let me add few details. When I run the corosync service I se
the corosync process running. If I stop it and run:
corosync -f
I see three warnings:
warning [MAIN ] interface section bindnetaddr is used together with nodelist.
Nodelist one is going to be used.
Hello Andrei,
thanks for this hint, but I need this "special" order. In an other setup it
works.
best regards
Stefan
> Gesendet: Freitag, 22. Juni 2018 um 06:57 Uhr
> Von: "Andrei Borzenkov"
> An: users@clusterlabs.org
> Betreff: Re: [ClusterLabs] corosync doesn't start any resource
>
>
On 21/06/18 16:16, Salvatore D'angelo wrote:
> Hi,
>
> I upgraded my PostgreSQL/Pacemaker cluster with these versions.
> Pacemaker 1.1.14 -> 1.1.18
> Corosync 2.3.5 -> 2.4.4
> Crmsh 2.2.0 -> 3.0.1
> Resource agents 3.9.7 -> 4.1.1
>
> I started on a first node (I am trying one node at a time
