I'll try to boil down this overly complicated problem into a few lines: How do I tell Graylog2 what interface to connect to elasticsearch on?
I can tell Elasticsearch where to find other cluster nodes, via the network.host: "_eth1:ipv4_" configuration option, and then I can build a cluster no problem. But graylog2 can never find that cluster because even though one node is running on the same server, it's trying to use eth0, which is a NAT'd interface on the host. Even if I tell the elasticsearch node to connect to other IPs (via discovery.zen.ping.unicast.hosts: ["192.168.x.135", "192.168.x.114"]), it wants to broadcast that it's connected to the eth0 interface, so the unicast host definition never find each other. Any ideas? Some of the things I've tried: server_rest_listen_uri = "http://192.168.x.10:12900"; server_rest_listen_uri = "http://192.168.x.10:12900/"; server_rest_transport_uri = "http://192.168.x.10:12900/"; When I do this, Graylog2 still drops its ability to connect to the elasticsearch cluster, etc. Thanks in advance! -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
