Re: Secondary ring problem with corosync 1.4.1

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

 



Hello,

On Wed, Aug 22, 2012 at 1:46 PM, Maurits van de Lande
<M.vandeLande@xxxxxxxxxxxxxxxx> wrote:
> Hello,
>
>
>
> I hope this is the right mailing list for this question.
>
>
>
> Problem:
>
> On a cman cluster with two redundant rings running on Centos6.3, Ring 1 is
> marked as faulty every few seconds and then recovers again.
>
>
>
> Ring 0:
>
> Two 10Gbe adapters bonded in mode 1 (bond0)
>
>
>
> Ring 1:
>
> An 1Gbe adapter connected to a dedicated “ secondary ring network”
>
>

Could you post the corosync version and the configuration file?

>
> The problem look similar as problem 3 in this thread
>
> http://www.spinics.net/lists/corosync/msg01637.html
>
>
>
>
>
> Below I pasted some of the logged messages:
>
>
>
> Aug 22 12:41:43 vmhost1d corosync[4947]:   [TOTEM ] Marking ringid 1
> interface 172.16.100.4 FAULTY
>
> Aug 22 12:41:44 vmhost1d corosync[4947]:   [TOTEM ] Automatically recovered
> ring 1
>
> Aug 22 12:41:44 vmhost1d corosync[4947]:   [TOTEM ] Automatically recovered
> ring 1
>
> Aug 22 12:41:44 vmhost1d corosync[4947]:   [TOTEM ] Automatically recovered
> ring 1
>
> Aug 22 12:41:47 vmhost1d corosync[4947]:   [TOTEM ] Marking ringid 1
> interface 172.16.100.4 FAULTY
>
> Aug 22 12:41:48 vmhost1d corosync[4947]:   [TOTEM ] Automatically recovered
> ring 1
>
> Aug 22 12:41:48 vmhost1d corosync[4947]:   [TOTEM ] Automatically recovered
> ring 1
>
> Aug 22 12:41:48 vmhost1d corosync[4947]:   [TOTEM ] Automatically recovered
> ring 1
>
> Aug 22 12:41:51 vmhost1d corosync[4947]:   [TOTEM ] Retransmit List: 2de76d
>
> Aug 22 12:41:51 vmhost1d corosync[4947]:   [TOTEM ] Retransmit List: 2de76f
>
> Aug 22 12:41:51 vmhost1d corosync[4947]:   [TOTEM ] Retransmit List: 2de770
>
> Aug 22 12:41:51 vmhost1d corosync[4947]:   [TOTEM ] Retransmit List: 2de772
>
> Aug 22 12:41:51 vmhost1d corosync[4947]:   [TOTEM ] Retransmit List: 2de772
>
> Aug 22 12:41:52 vmhost1d corosync[4947]:   [TOTEM ] Retransmit List: 2de775
>
> Aug 22 12:41:52 vmhost1d corosync[4947]:   [TOTEM ] Retransmit List: 2de777
>
> Aug 22 12:41:52 vmhost1d corosync[4947]:   [TOTEM ] Retransmit List: 2de778
>
> Aug 22 12:41:52 vmhost1d corosync[4947]:   [TOTEM ] Retransmit List: 2de779
>
> Aug 22 12:41:52 vmhost1d corosync[4947]:   [TOTEM ] Retransmit List: 2de779
>
> Aug 22 12:41:53 vmhost1d corosync[4947]:   [TOTEM ] Retransmit List: 2de77c
> 2de77e
>
> Aug 22 12:41:53 vmhost1d corosync[4947]:   [TOTEM ] Retransmit List: 2de77e
> 2de781
>
> Aug 22 12:41:53 vmhost1d corosync[4947]:   [TOTEM ] Retransmit List: 2de781
> 2de783
>
> Aug 22 12:41:53 vmhost1d corosync[4947]:   [TOTEM ] Retransmit List: 2de781
> 2de785
>
> Aug 22 12:41:53 vmhost1d corosync[4947]:   [TOTEM ] Marking ringid 1
> interface 172.16.100.4 FAULTY
>
>
>
> What can be done to solve this problem?
>
>
>
> Best regards,
>
>
>
> Maurits van de Lande
>
>
>
>
>
>
>
>
> _______________________________________________
> discuss mailing list
> discuss@xxxxxxxxxxxx
> http://lists.corosync.org/mailman/listinfo/discuss
>



-- 
Dan Frincu
CCNA, RHCE
_______________________________________________
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