[Pacemaker] pacemaker service start failed.

[Vladislav Bogdanov]

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?

Also, can you please some-how emphasize that behavior change in some
"Upgrading to 2.0.0" chapter?

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?

One little note which is not worthy of separate message.
crm_get_cluster_name() does not work for corosync2. totem.cluster_name?