[Pacemaker] Sending message via cpg FAILED: (rc=12) Doesn't exist

[Steven Dake]

On 07/22/2011 01:15 AM, Proskurin Kirill wrote:
> Hello all.
> 
> 
> pacemaker-1.1.5
> corosync-1.4.0
> 
> 4 nodes in cluster. 3 online 1 not.
> In logs:
> 
> Jul 22 11:50:23 my106.example.com crmd: [28030]: info:
> pcmk_quorum_notification: Membership 0: quorum retained (0)
> Jul 22 11:50:23 my106.example.com crmd: [28030]: info: do_started:
> Delaying start, no membership data (0000000000100000)
> Jul 22 11:50:23 my106.example.com crmd: [28030]: info:
> config_query_callback: Shutdown escalation occurs after: 1200000ms
> Jul 22 11:50:23 my106.example.com crmd: [28030]: info:
> config_query_callback: Checking for expired actions every 900000ms
> Jul 22 11:50:23 my106.example.com crmd: [28030]: info: do_started:
> Delaying start, no membership data (0000000000100000)
> Jul 22 11:50:27 my106.example.com attrd: [28028]: info: cib_connect:
> Connected to the CIB after 1 signon attempts
> Jul 22 11:50:27 my106.example.com attrd: [28028]: info: cib_connect:
> Sending full refresh
> Jul 22 11:52:18 corosync [TOTEM ] A processor joined or left the
> membership and a new membership was formed.
> Jul 22 11:52:18 corosync [CPG   ] chosen downlist: sender r(0)
> ip(10.3.1.107) ; members(old:4 left:1)
> Jul 22 11:52:18 corosync [MAIN  ] Completed service synchronization,
> ready to provide service.
> Jul 22 11:52:19 my106.example.com pacemakerd: [28021]: ERROR:
> send_cpg_message: Sending message via cpg FAILED: (rc=12) Doesn't exist
> Jul 22 11:52:19 my106.example.com pacemakerd: [28021]: ERROR:
> send_cpg_message: Sending message via cpg FAILED: (rc=12) Doesn't exist
> Jul 22 11:52:19 my106.example.com pacemakerd: [28021]: ERROR:
> send_cpg_message: Sending message via cpg FAILED: (rc=12) Doesn't exist
> 
> 
> 
> DC:
> 
> Jul 22 11:50:07 corosync [TOTEM ] Retransmit List: e4 e5 e7 e8 ea eb ed ee
> Jul 22 11:50:07 corosync [TOTEM ] Retransmit List: e4 e5 e7 e8 ea eb ed ee
> Jul 22 11:50:07 my107.example.com pacemakerd: [22388]: info:
> update_node_processes: Node my106.example.com now has process list:
> 00000000000000000000000000000002 (was 000000000000000000
> 00000000100002)
> Jul 22 11:50:07 my107.example.com attrd: [22397]: info: crm_update_peer:
> Node my106.example.com: id=0 state=unknown addr=(null) votes=0 born=0
> seen=0 proc=000000000000000000000000000000
> 02 (new)
> Jul 22 11:50:07 my107.example.com cib: [22395]: info: crm_update_peer:
> Node my106.example.com: id=0 state=unknown addr=(null) votes=0 born=0
> seen=0 proc=00000000000000000000000000000002
>  (new)
> Jul 22 11:50:07 my107.example.com stonith-ng: [22394]: info:
> crm_update_peer: Node my106.example.com: id=0 state=unknown addr=(null)
> votes=0 born=0 seen=0 proc=0000000000000000000000000
> 0000002 (new)
> Jul 22 11:50:07 my107.example.com crmd: [22399]: info: crm_update_peer:
> Node my106.example.com: id=0 state=unknown addr=(null) votes=0 born=0
> seen=0 proc=0000000000000000000000000000000
> 2 (new)
> Jul 22 11:50:07 corosync [TOTEM ] Retransmit List: e4 e5 e7 e8 ea eb ed ee
> Jul 22 11:50:07 corosync [TOTEM ] Retransmit List: e4 e5 e7 e8 ea eb ed ee
> 
> 
> There is a problem?
> 

Does your retransmit list continually display e4 e5 etc for rest of
cluster lifetime, or is this short lived?