[Pacemaker] syslog full of redundand link messages

[Dan Frincu]

Hi,

On Sun, Jan 8, 2012 at 1:59 AM, Attila Megyeri
<amegyeri at minerva-soft.com> wrote:
> Hi All,
>
>
>
> My syslogs are full of messages like this:
>
>
>
> Jan  7 23:55:47 oa2 corosync[362]:   [TOTEM ] received message requesting
> test of ring now active
>
> Jan  7 23:55:48 oa2 corosync[362]:   [TOTEM ] received message requesting
> test of ring now active
>
> Jan  7 23:55:48 oa2 corosync[362]:   [TOTEM ] received message requesting
> test of ring now active
>
> Jan  7 23:55:48 oa2 corosync[362]:   [TOTEM ] received message requesting
> test of ring now active
>
> Jan  7 23:55:49 oa2 corosync[362]:   [TOTEM ] received message requesting
> test of ring now active
>
> Jan  7 23:55:49 oa2 corosync[362]:   [TOTEM ] received message requesting
> test of ring now active
>
> Jan  7 23:55:49 oa2 corosync[362]:   [TOTEM ] received message requesting
> test of ring now active
>
> Jan  7 23:55:50 oa2 corosync[362]:   [TOTEM ] received message requesting
> test of ring now active
>
> Jan  7 23:55:50 oa2 corosync[362]:   [TOTEM ] received message requesting
> test of ring now active
>
> Jan  7 23:55:50 oa2 corosync[362]:   [TOTEM ] received message requesting
> test of ring now active
>
> Jan  7 23:55:51 oa2 corosync[362]:   [TOTEM ] received message requesting
> test of ring now active
>
> Jan  7 23:55:51 oa2 corosync[362]:   [TOTEM ] received message requesting
> test of ring now active
>
> Jan  7 23:55:51 oa2 corosync[362]:   [TOTEM ] received message requesting
> test of ring now active
>
> Jan  7 23:55:52 oa2 corosync[362]:   [TOTEM ] received message requesting
> test of ring now active
>
> Jan  7 23:55:52 oa2 corosync[362]:   [TOTEM ] received message requesting
> test of ring now active
>
> Jan  7 23:55:52 oa2 corosync[362]:   [TOTEM ] received message requesting
> test of ring now active
>
>
>
>
>
> What could be the reason for this?
>
>
>
>
>
> Pacemaker 1.1.6, Corosync 1.4.2
>
>
>
>
>
> The relevant part of the config:
>
>
>
> Eth0 is ont he 10.100.1.X subnet, eth1 is 192.168.100.X
>
>
>
>
>
>
>
>
>
> totem {
>
>         version: 2
>
>         secauth: off
>
>         threads: 0
>
>         rrp_mode: passive
>
>         interface {
>
>                 ringnumber: 0
>
>                 bindnetaddr: 10.100.1.255
>
>                 mcastaddr: 226.100.40.1
>
>                 mcastport: 4000
>
>         }
>
>         interface {
>
>                 ringnumber: 1
>
>         bindnetaddr: 192.168.100.255
>
>         mcastaddr: 226.101.40.1
>
>         mcastport: 4000
>
>         }
>

Are the subnets /24 or higher (/23, /22, etc.)? Because as I see
you're using what would be the broadcast address on a /24 subnet and
may cause issues.

>
>
>
>
> }
>
>
>
>
>
> Thanks,
>
>
>
> Attila
>
>
>
>
> _______________________________________________
> 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
>



-- 
Dan Frincu
CCNA, RHCE