[Spread-users] Multihomed configuration problem.

John Schultz jschultz at spreadconcepts.com
Tue Apr 1 12:40:58 EDT 2008


Yes, simply pass the -n <server_name> command line argument to Spread when 
it runs.

For example, from your conf file on 10.0.0.1 run

./spread -n server1-eth1

Cheers!

---
John Schultz
Spread Concepts
Phn: 443 838 2200

On Tue, 1 Apr 2008, Rodrick Brown wrote:

> I have about 30 nodes defined with the following configuration
>
> Each server is configured with 2 interfaces.
>
> serverX is defined in /etc/hosts and is the current hostname/nodename
> of serverX.
> serverX-eth1 is also defined in /etc/hosts and this is the interface I
> want to use for spread daemon communication.
>
> My configuration looks like the following. basically client
> communication should only try to use local host but daemon
> communication should use the dedicated interface on eth1.
>
> Spread_Segment 244.1.1.5:4803 {
>  server1-eth1 10.0.0.1 { D 10.1.0.0.1 C 127.0.0.1 }
>  server2-eth1 10.0.0.2 { D 10.1.0.0.2 C 127.0.0.1 }
>  ...
> }
>
> With this configuration is started I get the following error:
>
> Conf_load_conf_file: using file: /tmp/spread.conf
> Successfully configured Segment 0 [244.187.31.0:4803] with 16 procs:
>              server1-eth1: 10.0.0.1
>              server2-eth1: 10.0.0.2
>              server3-eth1: 10.0.0.3
>              ...
> Finished configuration file.
> Hash value for this configuration is: 332396006
> Conf_load_conf_file: My proc id (10.0.0.1) is not in configuration
> (this is the main address on eth0)
> Exit caused by Alarm(EXIT)
>
> Anyone know how I can work around this issue? I don't want spread to
> know about the interface running on eth0.
> I just want to make sure all daemon communication is sent/recv on eth1 only.
>
> Thanks.
>
>
>
> -- 
> [ Rodrick R. Brown ]
> http://www.rodrickbrown.com
> http://www.linkedin.com/in/rodrickbrown
>
> _______________________________________________
> Spread-users mailing list
> Spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users
>




More information about the Spread-users mailing list