petabridge / lighthouse

Lighthouse - a simple service discovery platform for Akka.Cluster (Akka.NET)
Apache License 2.0
175 stars 99 forks source link

Seeds never associate despite allowed in firewall #41

Closed rabejens closed 5 years ago

rabejens commented 6 years ago

I tried to set up lighthouse on three machines. Here is a sample config for one machine, the others are set up accordingly:

lighthouse{
        actorsystem: "mysystem" #POPULATE NAME OF YOUR ACTOR SYSTEM HERE
    }

akka {
    actor { 
        provider = "Akka.Cluster.ClusterActorRefProvider, Akka.Cluster"
    }

    remote {
        log-remote-lifecycle-events = DEBUG
        dot-netty.tcp {
            transport-class = "Akka.Remote.Transport.DotNetty.TcpTransport, Akka.Remote"
            applied-adapters = []
            transport-protocol = tcp
            #will be populated with a dynamic host-name at runtime if left uncommented
            public-hostname = "10.5.4.20"
            hostname = "10.5.4.20"
            port = 4053
        }
    }            

    loggers = ["Akka.Logger.NLog.NLogLogger, Akka.Logger.NLog"]

    cluster {
        #will inject this node as a self-seed node at run-time
        seed-nodes = ["akka.tcp://mysystem@10.5.4.21:4053", "akka.tcp://mysystem@10.5.4.120:4053"] #manually populate other seed nodes here, i.e. "akka.tcp://lighthouse@127.0.0.1:4053", "akka.tcp://lighthouse@127.0.0.1:4044"
        roles = [lighthouse]
    }
}

Those systems do have multiple network adapters. Can it be that it binds to the wrong one? How do I sort this out, what should I put in the applied-adapters? Or am I missing something different?

rabejens commented 6 years ago

EDIT: I figured it out, I was missing the IP address of the node itself in the seed-nodes element. I am leaving this open as this should be pointed out in the readme.