[Spread-users] Newbie: 2 servers, 1 linux, 1 NT, each has one deamon running, locally work fine, but can't communicate over the internet

Paolo Bernasconi paolo.bernasconi at gmail.com
Thu Jan 22 03:13:22 EST 2009


Hi John,
thanks for the quick reply.
I will definitely modify the segment address to 127.0.0.1 , since I do have
one single machine on each side and plan to make use of only one single
daemon on each side.
About the communication issue: ping goes through without a problem, though I
am not sure which port that is.
I'll try sp_send and sp_recv and see if I can get some more clues about
which port is open and which not.
My suspect is that, since both machines are virtual servers, there sure is
one layer of firewall where things might get stopped. I have control of the
firewall of my server, but not of the box in which it runs.
I will need to bother tech support at both sites, but first I need to
understand what the problem is, otherwise ... they will simply tell me that
they do not support the use of spread ... ;-(
I will do some more digging with the sp_* tools and go from there.

Thanks for your help! If I manage to get it working, I'll post the solution
...
regards,
Paolo
On Wed, Jan 21, 2009 at 11:56 PM, John Lane Schultz <
jschultz at spreadconcepts.com> wrote:

> Something between your two daemons is probably blocking their
> point-to-point traffic to one another.  The culprit could be any number of
> things, but is most likely either a machine level or network level firewall
> somewhere in the mix.
>
> You need to make sure that the port number you pick X (3333), port X + 1
> and port X + 2 are all open for UDP traffic for all the daemons in your
> configuration.  You can try using sp_send and sp_recv to see if traffic can
> flow on those ports at all between your machines.  Or, you could try some
> other more basic utility (ping?) to check the same thing.
>
> PS - If you are only going to have single machines in a segment, then set
> the segment address to be 127.0.0.1 so they don't bother any other machines
> in their subnet.  If you are going to have multiple daemons within a subnet,
> then use a multicast address (e.g. - 227.227.227.227) so that your daemons
> don't needlessly bother uninvolved machines by using the network broadcast
> address.
>
> Cheers!
> John
>
> ---
> John Lane Schultz
> Spread Concepts LLC
> Phn: 443 838 2200
> Fax: 301 560 8875
>
> Thursday, January 22, 2009, 2:29:39 AM, you wrote:
>
> > Hi,
> > here is the config file,same for both servers:
> >
> > Spread_Segment xxx.93.145.255:3333 {
> > machine1 xxx.93.145.124
> > }
> > Spread_Segment yyy.154.219.255:3333 {
> > machineB1 yyy.154.219.120
> > }
> >
> > On each server the deamon works fine, and client sessions can
> > communicate, but there is no way to make both server deamona see
> > each other and have the messages cross over the internet and reach the
> other deamon.
> >
> > After starting up the deamons on each server, this is what I get:
> >
> > on server at yyy.154.219.120 (linux)
>
> > ....
> > Conf_load_conf_file: using file: spread.conf
> > Successfully configured Segment 0 [xxx.93.145.255:3333] with 1 procs:
> >                     machine1: xxx.93.145.124
> > Successfully configured Segment 1 [yyy.154.219.255:3333] with 1 procs:
> >                    machineB1: yyy.154.219.120
> > Finished configuration file.
> > Hash value for this configuration is: 1744128833
> > Conf_load_conf_file: My name: machineB1, id: xyyy.154.219.120, port: 3333
> > Membership id is ( -660939912, 1232603174)
> > --------------------
> > Configuration at machineB1 is:
> > Num Segments 2
> >         0       xxx.93.145.255    3333
> >         1       xxyyy.154.219.255   3333
> >                 machineB1               yyy.154.219.120
> > ====================
> >
> > <<<<<<<<<<<<<<<<
> >
> > On server xxx.93.145.255    (NT)
> >
>
> > Conf_load_conf_file: using file: spread.conf
> > Successfully configured Segment 0 [xxx.93.145.124:3333] with 1 procs:
> >                     machine1: xxx.93.145.124
> > Successfully configured Segment 1 [yyy.154.219.120:3333] with 1 procs:
> >                    machineB1: yyy.154.219.120
> > Finished configuration file.
> > Hash value for this configuration is: 2008767669
> > Conf_load_conf_file: My name: machine1, id: xxx.93.145.124, port: 3333
> > Membership id is ( -799174276, 1232608861)
> > --------------------
> > Configuration at machine1 is:
> > Num Segments 2
> >         1       xxx.93.145.124    3333
> >                 machine1                xxx.93.145.124
> >         0       yyy.154.219.120   3333
> > ====================
> >
> > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> >
> > I can connect locally on each server using spuser, join a group and
> > send messages. If I use several clients joining the same group, they all
> see each other.
> > However. joining the same group on both severs across the internet
> > will not get me anywhere. No client session from one server gets to the
> other server
> > Now, both server have no firewall, I have disabled it on the NT and
> opened everything on the linux.
> > Shoulnd't this work or am I missing something?
> >
> > Hope someone can help, I haven't been able to figure it out.
> >
> > Thanks in advance
> > Paolo
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.spread.org/pipermail/spread-users/attachments/20090122/41865002/attachment.html 


More information about the Spread-users mailing list