On Thu, 2019-08-22 at 09:07 +0200, Ulrich Windl wrote:
> Hi!
>
> When starting pacemaker (1.1.19+20181105.ccd6b5b10-3.10.1) on a node
> that had been down for a while, I noticed some unexpected messages
> about the node name:
>
> pacemakerd: notice: get_node_name: Could not obtain a node name
> for corosync nodeid 739512332
> pacemakerd: info: crm_get_peer:Created entry a21bf687-045b-
> 4fd7-9340-0562ef595883/0x18752f0 for node (null)/739512332 (1 total)
> pacemakerd: info: crm_get_peer:Node 739512332 has uuid
> 739512332
>
> Seems UUID and node ID is mixed up in the message at least...
"UUID" is a misnomer, for historical reasons. It was an actual UUID for
heartbeat (originally the only supported cluster layer), but for
corosync it's the node ID and for Pacemaker Remote nodes it's the node
name.
Ironically the string after "Created entry" is an actual UUID but
that's not the "node UUID", just an internal hash table id.
We should definitely update all those messages to reflect the current
reality.
> pacemakerd: info: crm_update_peer_proc: cluster_connect_cpg: Node
> (null)[739512332] - corosync-cpg is now online
> pacemakerd: notice: cluster_connect_quorum: Quorum acquired
> pacemakerd: info: corosync_node_name: Unable to get node name for
> nodeid 739512332
> pacemakerd: notice: get_node_name: Defaulting to uname -n for the
> local corosync node name
> pacemakerd: info: crm_get_peer:Node 739512332 is now known as
> h12
> ...
> pacemakerd: info: main:Starting mainloop
> pacemakerd: info: pcmk_quorum_notification:Quorum
> retained | membership=172 members=2
> pacemakerd: info: corosync_node_name: Unable to get node
> name for nodeid 739512331
> pacemakerd: notice: get_node_name: Could not obtain a node name
> for corosync nodeid 739512331
> pacemakerd: info: crm_get_peer:Created entry f4ef35e4-1b49-
> 4e48-916b-bb0fab7c52c9/0x1876820 for node (null)/739512331 (2 total)
> pacemakerd: info: crm_get_peer:Node 739512331 has uuid
> 739512331
> ...
> pacemakerd: info: corosync_node_name: Unable to get node
> name for nodeid 739512331
> ...
> pacemakerd: notice: get_node_name: Could not obtain a node name
> for corosync nodeid 739512331
> pacemakerd: notice: crm_update_peer_state_iter: Node (null)
> state is now member | nodeid=739512331 previous=unknown
> source=pcmk_quorum_notification
> pacemakerd: notice: crm_update_peer_state_iter: Node 12 state
> is now member | nodeid=739512332 previous=unknown
> source=pcmk_quorum_notification
> pacemakerd: info: pcmk_cpg_membership: Node 739512332 joined
> group pacemakerd (counter=0.0, pid=32766, unchecked for rivals)
> stonith-ng: info: corosync_node_name: Unable to get node
> name for nodeid 739512332
> stonith-ng: notice: get_node_name: Could not obtain a node name
> for corosync nodeid 739512332
>
> What's that? The ID had been resolved before!
stonith-ng is a completely different process; each daemon has to figure
out the node information itself from what corosync gives it. You'll see
a lot of such messages repeated for each daemon that uses corosync.
>
> stonith-ng: info: crm_get_peer:Created entry 155a30a0-ddd3-
> 4b31-9f76-46313ffa9824/0x1bff130 for node (null)/739512332 (1 total)
> stonith-ng: info: crm_get_peer:Node 739512332 has uuid
> 739512332
> ...
> stonith-ng: notice: crm_update_peer_state_iter: Node (null)
> state is now member | nodeid=739512332 previous=unknown
> source=crm_update_peer_proc
> ...
> attrd: notice: get_node_name: Could not obtain a node name for
> corosync nodeid 739512332
> attrd: info: crm_get_peer:Created entry 961e718f-ad71-479a-
> ae04-c2ec5ba29858/0x256ca40 for node (null)/739512332 (1 total)
> attrd: info: crm_get_peer:Node 739512332 has uuid 739512332
> attrd: info: crm_update_peer_proc:cluster_connect_cpg: Node
> (null)[739512332] - corosync-cpg is now online
> attrd: notice: crm_update_peer_state_iter: Node (null) state
> is now member | nodeid=739512332 previous=unknown
> source=crm_update_peer_proc
> ...
> pacemakerd: notice: get_node_name: Could not obtain a node name
> for corosync nodeid 739512331
> pacemakerd: info: pcmk_cpg_membership: Node 739512331 still
> member of group pacemakerd (peer=(null):7275, counter=0.0, at least
> once)
> stonith-ng: notice: get_node_name: Defaulting to uname -n for the
> local corosync node name
> ...
> pacemakerd: info: crm_get_peer:Node 739512331 is now known as
> h11
> ...
> attrd: info: corosync_node_name: Unable to get node name for
> nodeid 739512332
> attrd: notice: get_node_name: Defaulting to uname -n for the
> local corosync node name
> attrd: info: crm_get_peer:Node 739512332 is now known as h12
> stonith-ng: info: corosync_node_name: Unable to get node
> name for nodeid 739512332
> stonith-ng: notice: get_node_name:
