[Pacemaker] pacemaker service start failed.

Vladislav Bogdanov bubble at hoster-ok.com
Mon Nov 12 17:56:01 EST 2012

13.11.2012 01:39, Andrew Beekhof пишет:
> On Tue, Nov 13, 2012 at 9:36 AM, Vladislav Bogdanov
> <bubble at hoster-ok.com> wrote:
>> 12.11.2012 05:42, Andrew Beekhof wrote:
>>> On Fri, Nov 9, 2012 at 5:15 PM, Vladislav Bogdanov <bubble at hoster-ok.com> wrote:
>>>> 09.11.2012 04:48, Andrew Beekhof wrote:
>>>> ...
>>>>> A bit of an update....
>>>>> The reverse lookup functionality has turned out to cause far more
>>>>> problems and confusion than it was intended to solve.
>>>>> So I am basically removing it.  Anyone worried about that
>>>>> bootstrapping case will be encouraged to use a corosync nodelist.
>>>>> Below is the new section I added to the asciidoc documentation yesterday:
>>>>> == Where Pacemaker Gets the Node Name ==
>>>>> Traditionally, Pacemaker required nodes to be referred to by the value
>>>>> returned by `uname -n`.  This can be problematic for services that
>>>>> require the `uname -n` to be a specific value (ie. for a licence
>>>>> file).
>>>>> Since version 2.0.0 of Pacemaker, this requirement has been relaxed
>>>>> for clusters using Corosync 2.0 or later.  The name Pacemaker uses is:
>>>>> . The value stored in 'corosync.conf' under +ring0_addr+ in the
>>>>> +nodelist+, if it does not contain an IP address; otherwise
>>>>> . The value stored in 'corosync.conf' under +name+ in the +nodelist+; otherwise
>>>>> . The value of `uname -n`
>>>>> Pacemaker provides the `crm_node -n` command which displays the name
>>>>> used by a running cluster.
>>>>> If a Corosync nodelist is used, `crm_node --name-for-id $number` is also
>>>>> available to display the name used by the node with the corosync
>>>>> +nodeid+ of '$number', eg. `crm_node --name-for-id 2`
>>>> Andrew, could you please add that 'nodelist.node.%d.name' is a
>>>> pacemaker-specific extension to corosync configuration and is neither
>>>> used by corosync nor mentioned in its documentation?
>>> I guess.
>>> Corosync lets you stick anything in the config, it didn't seem important.
>>>> Also, can you please some-how emphasize that behavior change in some
>>>> "Upgrading to 2.0.0" chapter?
>>> Sure.
>>>> And, 'uname -n' does not work for remote nodes (you wrote that
>>>> reverse-lookup functionality was primarily(?) introduced to get names of
>>>> remote nodes before they are known to cluster). Will it still work if
>>>> neither +ring0_addr+ has a name nor +name+ is populated?
>>> Define 'it'?
>>> Without a name in 'ring0_addr' or 'name', Pacemaker will fall back to
>>> uname -n as it always has.
>> I mean that if corosync.conf doesn't have names in ring0_addr and name,
>> then it is not possible to get remote nodes names before they announce
>> themselves to cluster. In this case you only know ip address and
>> corosync id. Not name.
> Which is how it has always been when using corosync.
Yes. But I thought you need node names before they join. If not then
there is no problem at all.

> _______________________________________________
> 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://bugs.clusterlabs.org

More information about the Pacemaker mailing list