Re: solved: daemons can talk to one another using unicast udp

> I had multiple issues. I had two versions of spread daemons 4.3 and loggi=
ng set higher in one configuration file then the other.

The logging level should not affect whether daemons can communicate or not.=
  The only part of the configuration that is used for the config hash are t=
he Spread segments.  They basically have to be exactly the same, including =
their ordering, on all the daemons in a configuration.

> I did notice that SAFE messages are not persistent, I though if I killed =
an app running one one machine that joined to a group shared by the other m=
achine that a safe message would be delivered when I rejoined the group. =


No, Spread does not do persistent messaging.  Spread is an ephemeral messag=
ing service.  It=92s kind of like TCP/IP but generalized for multicast.  A =
SAFE message delivered before a transitional signal will be delivered in th=
e same AGREED order to all other group members unless they crash.

Cheers!

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

On Jul 9, 2014, at 6:34 PM, Dave Schere <[email protected]> wrote:


I had multiple issues. I had two versions of spread daemons 4.3 and logging=
 set higher in one configuration file then the other.

The correct configuration for two spread daemons using UDP was

Spread_Segment <ip of machine 1>:4803{
    <host name of machine 1> <ip of machine 1>
}
Spread_Segment <ip of machine 2>:4803{
    <host name of machine 2> <ip of machine 2>
}

I did notice that SAFE messages are not persistent, I though if I killed an=
 app running one one machine that joined to a group shared by the other mac=
hine that a safe message would be delivered when I rejoined the group. =


whatever, its working ....



_______________________________________________
Spread-users mailing list
[email protected]
http://lists.spread.org/mailman/listinfo/spread-users