[Spread-users] spread-5.0.0rc1 : old way to explicitly select an interface by IP in spread.conf fails

John Lane Schultz jschultz at spreadconcepts.com
Thu Dec 8 13:24:38 EST 2016


Would you please send the portion of your configuration file that is having trouble and what you expect should happen (and has happened in past versions)?

It looks like you have a spread segment address of 192.168.2.109 and then a daemon with an address of 192.168.2.105 that you also explicitly configure its interface?  Something like:

Spread_Segment 192.168.2.109
{
  …
  easy1al1 192.168.2.105 { 192.168.2.105 }
  ...
}

Is that right?

The new code binds to the daemon’s IP (192.168.2.105) for receiving, but then also binds to the broadcast address (192.168.2.109) to receive the broadcasts, but the bind to the broadcast address looks to be failing.

Are you sure that is the correct broadcast address for your network and that the NIC is properly configured (e.g. - net mask) too?

Cheers!

-----
John Lane Schultz
Spread Concepts LLC
Cell: 443 838 2200

On Dec 8, 2016, at 9:36 AM, Martin Schu <martin.sc11111 at gmail.com> wrote:

Hi,

here is an observation while testing spread-5.0.0rc1 in our Linux (RHEL) environment:

With spread-5 a new way to configure interfaces by name has been introduced in spread.conf (IPv6address%ifname).

The old way to explicitly select an interface by configuring its IP address (192.168.2.109 {192.168.2.109}) in spread.conf should be working too, but something is strange here with spread-5. We are using that old way in our spread.conf because we don't know the ifnames at other hosts.

In spread-4.4 the redundant explicit choice of an interface by IP address was accepted.
Seemingly spread-5 ist trying to bind the same interface twice in this case, which is failing of course.
Net_init: explicit: binding a recv bcast channel to [192.168.2.105]:5892
Net_init: explicit: binding an extra recv bcast channel to [192.168.2.109]:5892
DL_init_channel_gen: bind error (99: Cannot assign requested address) for [192.168.2.109]:5892; probably already running!
If I remove the explicit configuration of a specific interface by IP address from spread.conf everything is working fine with spread-5.

But we need to explicitly configure the interfaces by IP address, because we observed in rare cases some wrong interface choice by spread-4.4 when we rely on the implicit automatic choice. In rare cases we saw in netstat -g some binding to a wrong interface. This is the reason why we want to use the explicit choice.

Kind regards,
Martin
2016-12-06 12:46:11 GMT Disabling Dangerous Monitor Commands!
2016-12-06 12:46:11 GMT Setting SO_REUSEADDR to auto
2016-12-06 12:46:11 GMT Hash value for this configuration is: 2769325100
2016-12-06 12:46:11 GMT Finished configuration file.
2016-12-06 12:46:11 GMT Conf_load_conf_file: using sin6_scope_id 0 for interface 192.168.2.105
2016-12-06 12:46:11 GMT Conf_load_conf_file: My name: easy1al1, id: 3220897676, addr: 192.168.2.105, port: 5892
2016-12-06 12:46:11 GMT E_init: went ok
2016-12-06 12:46:11 GMT Net_signal_conf_reload: Bcast needed
2016-12-06 12:46:11 GMT Net_init: explicit: binding a recv bcast channel to [192.168.2.105]:5892
2016-12-06 12:46:11 GMT Net_init: explicit: binding a recv token channel to [192.168.2.105]:5893
2016-12-06 12:46:11 GMT Net_init: explicit: binding an extra recv bcast channel to [192.168.2.109]:5892
2016-12-06 12:46:11 GMT DL_init_channel_gen: bind error (99: Cannot assign requested address) for [192.168.2.109]:5892; probably already running!
Exit caused by Alarm!






More information about the Spread-users mailing list