[Pacemaker] repetative membership messages

Andrew Beekhof andrew at beekhof.net
Mon Apr 8 02:39:30 UTC 2013


On 03/04/2013, at 6:40 PM, Daniel Black <daniel.black at openquery.com> wrote:

> I'm getting this repetition of messages every 5 seconds. Is this normal?

No. This is indicative of core Corosync (not the pacemaker bits) not being very happy.
What version are you running?

> crm_mon is showing 5 members as constant.
> 
> Apr  3 03:29:50 tx-web04 corosync[7524]:   [pcmk  ] notice: pcmk_peer_update: Transitional membership event on ring 5837728: memb=5, new=0, lost=0
> Apr  3 03:29:50 tx-web04 corosync[7524]:   [pcmk  ] info: pcmk_peer_update: memb: tx-web01 1937811648
> Apr  3 03:29:50 tx-web04 corosync[7524]:   [pcmk  ] info: pcmk_peer_update: memb: tx-web02 92383424
> Apr  3 03:29:50 tx-web04 corosync[7524]:   [pcmk  ] info: pcmk_peer_update: memb: tx-web04 59156672
> Apr  3 03:29:50 tx-web04 corosync[7524]:   [pcmk  ] info: pcmk_peer_update: memb: tx-web05 310814912
> Apr  3 03:29:50 tx-web04 corosync[7524]:   [pcmk  ] info: pcmk_peer_update: memb: tx-web03 1033087168
> Apr  3 03:29:50 tx-web04 corosync[7524]:   [pcmk  ] notice: pcmk_peer_update: Stable membership event on ring 5837728: memb=5, new=0, lost=0
> Apr  3 03:29:50 tx-web04 corosync[7524]:   [pcmk  ] info: pcmk_peer_update: MEMB: tx-web01 1937811648
> Apr  3 03:29:50 tx-web04 corosync[7524]:   [pcmk  ] info: pcmk_peer_update: MEMB: tx-web02 92383424
> Apr  3 03:29:50 tx-web04 corosync[7524]:   [pcmk  ] info: pcmk_peer_update: MEMB: tx-web04 59156672
> Apr  3 03:29:50 tx-web04 corosync[7524]:   [pcmk  ] info: pcmk_peer_update: MEMB: tx-web05 310814912
> Apr  3 03:29:50 tx-web04 corosync[7524]:   [pcmk  ] info: pcmk_peer_update: MEMB: tx-web03 1033087168
> Apr  3 03:29:50 tx-web04 corosync[7524]:   [TOTEM ] A processor joined or left the membership and a new membership was formed.
> Apr  3 03:29:50 tx-web04 corosync[7524]:   [CPG   ] chosen downlist: sender r(0) ip(192.168.134.131) ; members(old:5 left:0)
> Apr  3 03:29:50 tx-web04 corosync[7524]:   [MAIN  ] Completed service synchronization, ready to provide service.
> 
> Apr  3 03:29:54 tx-web04 corosync[7524]:   [pcmk  ] notice: pcmk_peer_update: Transitional membership event on ring 5837732: memb=5, new=0, lost=0
> Apr  3 03:29:54 tx-web04 corosync[7524]:   [pcmk  ] info: pcmk_peer_update: memb: tx-web01 1937811648
> Apr  3 03:29:54 tx-web04 corosync[7524]:   [pcmk  ] info: pcmk_peer_update: memb: tx-web02 92383424
> Apr  3 03:29:54 tx-web04 corosync[7524]:   [pcmk  ] info: pcmk_peer_update: memb: tx-web04 59156672
> Apr  3 03:29:54 tx-web04 corosync[7524]:   [pcmk  ] info: pcmk_peer_update: memb: tx-web05 310814912
> Apr  3 03:29:54 tx-web04 corosync[7524]:   [pcmk  ] info: pcmk_peer_update: memb: tx-web03 1033087168
> Apr  3 03:29:54 tx-web04 corosync[7524]:   [pcmk  ] notice: pcmk_peer_update: Stable membership event on ring 5837732: memb=5, new=0, lost=0
> Apr  3 03:29:54 tx-web04 corosync[7524]:   [pcmk  ] info: pcmk_peer_update: MEMB: tx-web01 1937811648
> Apr  3 03:29:54 tx-web04 corosync[7524]:   [pcmk  ] info: pcmk_peer_update: MEMB: tx-web02 92383424
> Apr  3 03:29:54 tx-web04 corosync[7524]:   [pcmk  ] info: pcmk_peer_update: MEMB: tx-web04 59156672
> Apr  3 03:29:54 tx-web04 corosync[7524]:   [pcmk  ] info: pcmk_peer_update: MEMB: tx-web05 310814912
> Apr  3 03:29:54 tx-web04 corosync[7524]:   [pcmk  ] info: pcmk_peer_update: MEMB: tx-web03 1033087168
> Apr  3 03:29:54 tx-web04 corosync[7524]:   [TOTEM ] A processor joined or left the membership and a new membership was formed.
> Apr  3 03:29:54 tx-web04 corosync[7524]:   [CPG   ] chosen downlist: sender r(0) ip(192.168.134.131) ; members(old:5 left:0)
> Apr  3 03:29:54 tx-web04 corosync[7524]:   [MAIN  ] Completed service synchronization, ready to provide service.
> 
> 
> totem {
>        version: 2
>        token: 3000
>        token_retransmits_before_loss_const: 10
>        join: 1000
>        consensus: 3600
>        vsftype: none
>        max_messages: 20
>        clear_node_high_bit: yes
>        secauth: on
>        threads: 2
>        rrp_mode: none
>        interface {
>                ringnumber: 0
>                bindnetaddr: 192.168.128.0
>                mcastport: 4960
>                member {
>                        memberaddr: 192.168.128.115
>                }
>                member {
>                        memberaddr: 192.168.129.5
>                }
>                member {
>                        memberaddr: 192.168.147.61
>                }
>                member {
>                        memberaddr: 192.168.134.131
>                }
>                member {
>                        memberaddr: 192.168.134.146
>                }
>        }
>        transport: udpu
> }
> 
> amf {
>        mode: disabled
> }
> 
> service {
>        ver:       0
>        name:      pacemaker
> }
> 
> aisexec {
>        user:   root
>        group:  root
> }
> 
> logging {
>        fileline: off
>        to_stderr: no
>        to_logfile: no
>        to_syslog: yes
>        syslog_facility: daemon
>        debug: off
>        timestamp: on
>        logger_subsys {
>                subsys: AMF
>                debug: off
>                tags: enter|leave|trace1|trace2|trace3|trace4|trace6
>        }
> }
> 
> Debian package versions:
> corosync                                1.4.2-1~bpo60+1
> libcorosync4                            1.4.2-1~bpo60+1
> pacemaker                               1.1.7-1~bpo60+1
> 
> 
> _______________________________________________
> 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