[Pacemaker] Cluster type is: corosync

Andrew Beekhof andrew at beekhof.net
Sun Jul 31 21:42:19 EDT 2011


On Wed, Jul 27, 2011 at 4:58 PM, Proskurin Kirill
<k.proskurin at corp.mail.ru> wrote:
> 27.07.2011 6:41, Andrew Beekhof пишет:
>
>>>> Ok. And did you add the pacemaker configuration options to corosync's
>>>> config file?
>>>
>>>
>>> I attach our corosync.conf. It is same on all nodes except IP addr.
>>
>> You missed a step from:
>>
>>  http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/s-configure-corosync.html
>
> Witch one?

"Finally, tell Corosync to load the Pacemaker plugin."

> At previous conversation Steven Dake said what I can use exact ip addr if I
> wish(And I do - because some node may have more then one ip addr on the same
> network).
> And I run pacemakerd after corosync start.
>
> I can`t say for sure but seems to I fix it by turning "compatibility: none".
> After this it start to tell me what here are "Cluster type: openais".
>
>>> Pacemaker is black now - no configuration at all.
>>>
>>> Online nodes:
>>> [root at mysender1 ~]# crm configure show
>>> node mysender1.example.com
>>> node mysender2.example.com
>>> node mysender3.example.com
>>> node mysender4.example.com
>>> node mysender5.example.com
>>> node mysender6.example.com
>>> node mysender7.example.com
>>> property $id="cib-bootstrap-options" \
>>>        dc-version="1.1.5-3-01e86afaaa6d4a8c4836f68df80ababd6ca3902f" \
>>>        cluster-infrastructure="openais" \
>>>        expected-quorum-votes="6"
>>>
>>>
>>> Offline nodes(Cluster type is: corosync)
>>> [root at mysender2 ~]# crm configure show
>>> [root at mysender2 ~]#
>>>
>>>
>>>>
>>>>> pacemaker-1.1.5
>>>>> corosync-1.4.0
>>>>> cluster-glue-1.0.6
>>>>> openais-1.1.2
>>>>>
>>>>> All nodes have same rpms.
>>>>>
>>>>>> On Fri, Jul 22, 2011 at 7:47 PM, Proskurin Kirill
>>>>>> <k.proskurin at corp.example.com>      wrote:
>>>>>>>
>>>>>>> Hello again!
>>>>>>>
>>>>>>> Hope I`m not flooding too much here but I have another problem.
>>>>>>>
>>>>>>> I install same rpm of corosync, openais, pacemaker, cluster_glue on
>>>>>>> all
>>>>>>> nodes. I check it twice.
>>>>>>>
>>>>>>> And then I start some of they - they can`t connect to cluster and
>>>>>>> stays
>>>>>>> offline. In logs I see what they see other nodes and connectivity is
>>>>>>> ok.
>>>>>>> But
>>>>>>> I found the difference:
>>>>>>>
>>>>>>> Online nodes in cluster have:
>>>>>>> [root at mysender39 ~]# grep 'Cluster type is' /var/log/corosync.log
>>>>>>> Jul 22 20:38:58 mysender39.example.com stonith-ng: [3499]: info:
>>>>>>> get_cluster_type: Cluster type is: 'openais'.
>>>>>>> Jul 22 20:38:58 mysender39.example.com attrd: [3502]: info:
>>>>>>> get_cluster_type:
>>>>>>> Cluster type is: 'openais'.
>>>>>>> Jul 22 20:38:58 mysender39.example.com cib: [3500]: info:
>>>>>>> get_cluster_type:
>>>>>>> Cluster type is: 'openais'.
>>>>>>> Jul 22 20:38:59 mysender39.example.com crmd: [3504]: info:
>>>>>>> get_cluster_type:
>>>>>>> Cluster type is: 'openais'.
>>>>>>>
>>>>>>> Offline have:
>>>>>>> [root at mysender2 ~]# grep 'Cluster type is' /var/log/corosync.log
>>>>>>> Jul 22 13:39:17 mysender2.example.com stonith-ng: [9028]: info:
>>>>>>> get_cluster_type: Cluster type is: 'corosync'.
>>>>>>> Jul 22 13:39:17 mysender2.example.com attrd: [9031]: info:
>>>>>>> get_cluster_type:
>>>>>>> Cluster type is: 'corosync'.
>>>>>>> Jul 22 13:39:17 mysender2.example.com cib: [9029]: info:
>>>>>>> get_cluster_type:
>>>>>>> Cluster type is: 'corosync'.
>>>>>>> Jul 22 13:39:18 mysender2.example.com crmd: [9033]: info:
>>>>>>> get_cluster_type:
>>>>>>> Cluster type is: 'corosync'.
>>>>>>>
>>>>>>> What`s wrong and how can I fix it?
>
>
> --
> Best regards,
> Proskurin Kirill
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs:
> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>




More information about the Pacemaker mailing list