On Mon, Oct 22, 2012 at 10:29 PM, Yuusuke Iida
<iiday...@intellilink.co.jp> wrote:
> Hi, Vossel
>
> (2012/10/20 0:42), David Vossel wrote:
>>
>>
>> ----- Original Message -----
>>> From: "Yuusuke Iida" <iiday...@intellilink.co.jp>
>>> To: "pacemaker@oss" <pacemaker@oss.clusterlabs.org>
>>> Cc: shimaza...@intellilink.co.jp
>>> Sent: Friday, October 19, 2012 1:43:25 AM
>>> Subject: [Pacemaker] pacemaker service start failed.
>>>
>>> Hi, Andrew
>>>
>>> I made a version of Pacemaker latest.
>>> Then pacemaker came to fail in start.
>>>
>>> I think that this came to be caused by the following changes.
>>> https://github.com/ClusterLabs/pacemaker/commit/4f88cb1049e898726472a91fff834dcccbd6f665
>>>
>>> I confirm movement in the following versions now.
>>>
>>> OS: RHEL6.3
>>> # pacemakerd -F
>>> Pacemaker 1.1.8 (Build: bd68c20)
>>> Supporting: agent-manpages ncurses libqb-logging libqb-ipc
>>> lha-fencing
>>> heartbeat corosync-native
>>> # corosync -v
>>> Corosync Cluster Engine, version '2.1.0.1-20c58'
>>>
>>> I collected crm_report of this time.
>>>
>>> Did how to use pacemaker change?
>>> Does my setting have a problem?
>>
>> Looking at your corosync.conf, what happens if you un-comment the udpu
>> transport and node list? I'm curious to know if this is a problem limited to
>> the use of corosync with multicast for some reason.
> I un-comment and started pacemaker, but have failed like the last time.
>
> nodeid seems to be always handled with 0 as far as I watch
> "lib/cluster/corosync.c".
nodeid 0 is a way of saying "our node"
>
> Like the patch which I attached, should not I use pcmk_nodeid here?
It shouldn't be necessary.
I run the exact same setup (multicast, no nodelist) and it seems to work fine.
How are node names mapped to ip addresses? DNS or /etc/hosts
Could you turn on debug and see if you're getting this message please?
crm_debug("Unable to get node address for nodeid %u: %s",
nodeid, cs_strerror(rc));
I'm using DNS but I thought /etc/hosts worked too.
>
> Supplement: Because I build corosync cluster using multicast, I do not
> want to set nodelist.
>
> I send a modified patch about new crm_report and nodeid.
>
> Best Regards,
> Yuusuke
>>
>> -- Vossel
>>
>>> Best Regards,
>>> Yuusuke
>>> --
>>> ----------------------------------------
>>> METRO SYSTEMS CO., LTD
>>>
>>> Yuusuke Iida
>>> Mail: iiday...@intellilink.co.jp
>>> ----------------------------------------
>>>
>>> _______________________________________________
>>> Pacemaker mailing list: Pacemaker@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://bugs.clusterlabs.org
>>>
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker@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://bugs.clusterlabs.org
>>
>
> --
> ----------------------------------------
> METRO SYSTEMS CO., LTD
>
> Yuusuke Iida
> Mail: iiday...@intellilink.co.jp
> ----------------------------------------
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker@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://bugs.clusterlabs.org
>
_______________________________________________
Pacemaker mailing list: Pacemaker@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://bugs.clusterlabs.org
