[Spread-users] Spread 2.5

[Göran Hasse]

Could you not change logging a bit. My logs are filled with
"Send_join: State is 4"
It would be nice to understand if this is a state transition. What is
state 4? Does it mean
everyting is ok? or something else?

Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4
Send_join: State is 4

2014-09-03 5:23 GMT+02:00 John Lane Schultz <jschultz at spreadconcepts.com>:
> >From the logs, can you tell us what state the daemons were in when this was occurring?  It could be a bug.
>
> Cheers!
>
> -----
> John Lane Schultz
> Spread Concepts LLC
> Cell: 443 838 2200
>
> On Sep 2, 2014, at 10:43 PM, Yair Amir <yairamir at cs.jhu.edu> wrote:
>
> I have a setup with 6 devices (running spread 4.4.0 on linux) with each one configured on a separate segment because they are located on separate subnets. Multicast and broadcast is not available so I configured the segments as follow
>
> Spread_Segment  172.23.1.1 {
>  node1   172.23.1.1
> }
>
> Spread_Segment  172.23.2.1 {
>  node2   172.23.2.1
> }
>
> Spread_Segment  172.23.3.1 {
> node3   172.23.3.1
> }
>
> Spread_Segment  172.23.4.1 {
>  node4   172.23.4.1
> }
>
> Spread_Segment  172.23.5.1 {
>  node5   172.23.5.1
> }
>
> Spread_Segment  172.23.6.1 {
>  node6   172.23.6.1
> }
>
> Everything works perfectly 99.999%  of the time but it happened a few times that we had a situation where all the communication between the nodes were stalled and looking at spmonitor we discovered that some daemon were constantly retransmitting.  There was no way to get out of this mode besides restarting the daemon. During that time all communication between the nodes were work fine on all other ports (ping, 22, http, and some other udp port that we use).
>
> My Questions are:
> - Why would that happen ?
> - Is there a way to detect it and to resolve it without restarting the daemon ?
>
> Thanks
>
> Claude
> _______________________________________________
> Spread-users mailing list
> Spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users
>
>
> _______________________________________________
> Spread-users mailing list
> Spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users



-- 
gorhas at gmail.com
Göran Hasse
Boo 229
715 91  ODENSBACKEN
Mob: 070-5530148