Questions about logs that are output multiple times

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

When ring was recovered from FAULTY, "Automatically recovered ring"
log is *sometimes* output several times.
Is this the designed behavior?

* corosync - v2.3.4 (2429481)
* libqb - v0.17.1 (3f7de65)
* RHEL6.5 (hostname: vm1, vm2)

* corosync.conf
  totem {
      version: 2
      rrp_mode: active
      token: 1000
      interface {
          ringnumber: 0
          bindnetaddr: 192.168.101.0
          mcastport: 5415
          mcastaddr: 239.255.1.1
      }
      interface {
          ringnumber: 1
          bindnetaddr: 192.168.102.0
          mcastport: 5415
          mcastaddr: 239.255.1.1
      }
  }
  logging {
      syslog_facility: local1
      debug: on
  }
  quorum {
      provider: corosync_votequorum
      expected_votes: 2
  }

[steps to reproduce]
1) start corosync on vm1 and vm2.
2) intercept ring0 until the following log is output.
   "ringid 0 interface 192.168.101.161 FAULTY"
3) cancel the interception, and "Automatically recovered ring" log is
sometimes output 2-5 times.

* log (vm1)
  Sep  3 14:04:57 vm1 corosync[11389]:  [TOTEM ] Incrementing problem
counter for seqid 1497 iface 192.168.101.161 to [10 of 10]
  Sep  3 14:04:57 vm1 corosync[11389]:  [TOTEM ] Marking seqid 1497
ringid 0 interface 192.168.101.161 FAULTY
  Sep  3 14:05:04 vm1 corosync[11389]:  [TOTEM ] received message
requesting test of ring now active
  Sep  3 14:05:04 vm1 corosync[11389]:  [TOTEM ] received message
requesting test of ring now active
  Sep  3 14:05:04 vm1 corosync[11389]:  [TOTEM ] received message
requesting test of ring now active
  Sep  3 14:05:04 vm1 corosync[11389]:  [TOTEM ] Automatically recovered ring 0
  Sep  3 14:05:04 vm1 corosync[11389]:  [TOTEM ] Automatically recovered ring 0
  Sep  3 14:05:04 vm1 corosync[11389]:  [TOTEM ] Automatically recovered ring 0

* log (vm2)
  Sep  3 14:04:57 vm2 corosync[6207]:  [TOTEM ] Incrementing problem
counter for seqid 1496 iface 192.168.101.162 to [10 of 10]
  Sep  3 14:04:57 vm2 corosync[6207]:  [TOTEM ] Marking seqid 1496
ringid 0 interface 192.168.101.162 FAULTY
  Sep  3 14:05:04 vm2 corosync[6207]:  [TOTEM ] received message
requesting test of ring now active
  Sep  3 14:05:04 vm2 corosync[6207]:  [TOTEM ] received message
requesting test of ring now active
  Sep  3 14:05:04 vm2 corosync[6207]:  [TOTEM ] received message
requesting test of ring now active
  Sep  3 14:05:04 vm2 corosync[6207]:  [TOTEM ] Automatically recovered ring 0
  Sep  3 14:05:04 vm2 corosync[6207]:  [TOTEM ] Automatically recovered ring 0
  Sep  3 14:05:04 vm2 corosync[6207]:  [TOTEM ] Automatically recovered ring 0

Regards,
Kazunori INOUE
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss




[Index of Archives]     [Linux Clusters]     [Corosync Project]     [Linux USB Devel]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Linux Kernel]     [Linux SCSI]     [X.Org]

  Powered by Linux