[Spread-users] Problems with more than 2 hosts in a segment

[Yair Amir]

Hi Jeurgen,

I think Jonathan answer is definitely correct and your network broadcast address does not work on your network (172.21.1.255).

So, to have Spread work with a broadcast address you need to make sure you have a working address. Or, you can try an ip-multicast address instead such as 225.172.21.1.
This is the kind of solution that will work best.

There is another solution that will definitely work immediately:

Change your config file to include:

Spread_Segment  0.0.0.0:3333{
    hermes 172.21.1.10
}
Spread_Segment 0.0.0.0:3333{
    baggins 172.21.1.25
}
Spread_Segment 0.0.0.0:3333{
    gamgee 172.21.1.26
}
Spread_Segment 0.0.0.0:3333{
    took 172.21.1.27
}

instead of :

Spread_Segment  172.21.1.255:3333 {
          hermes  172.21.1.10
          baggins 172.21.1.25
          gamgee  172.21.1.26
          took    172.21.1.27
  }

This will cause Spread only to use unicast. It will definitely work for you BUT it is only 1/3 as efficient, so should be used only temporarily.

    Enjoy,

    :) Yair.

Hans Juergen von Lengerke wrote:

> Hello George, Hello Yair,
>
> (jeez, I go for a coffee and got two replies... open source sucks
>  sometime ya know... you can't just relax and tell your manager you're
>  waiting for support ;-)
>
> I haven't tried _all_ permutations but I have tried
>
>         hermes, took    ... gamgee joins
>         baggins, gamgee ... hermes joins
>         hermes, gamgee  ... baggins joins
>
> all spread.conf's are exactly the same (distributed via FTP)
>
> I have used 'r' and 's' as suggested. The way I called them was
>
>         172.21.1.10 # r -d
> and     172.21.1.25 # s -a 172.21.1.10
>
> I've tried 'r -d' on any machine and 's'ed them from all other machines
> (including localhost). The only odd thing I could see is that the first
> 's' sent to a freshly started 'r -d' would always have one package
> missed. I suspect that this isn't the problem though.
>
> I have done more testing on the time it takes for machines to join the
> segment. Basically, when I start spread at the same time on two
> machines, it takes about 1 minute until the two machines see each other
> in the segment. After starting spread on the third machine (which brakes
> stuff) it takes again 1 minute until the third machine joins the
> segment.
>
> This kind of smells like it may have something to do with the resolver.
> All machines access the same nameserver. However, that nameserver
> doesn't know anything about the machines so resolving has to be done via
> /etc/hosts (which is the same on all machines in the segment and only
> contains IP's/Names of machines in the spread segment). Could this be
> the cause for the problem?
>
> Thx, Hans
>