Beyond odd. The only thing that strikes me as unusual is that 127.0.0.1:9300 is in the unicast host list. Usually you would omit that, and only put the members in the elasticsearch cluster into it. Do you have multiple elasticsearch nodes? Or is the one running on .166:9300 the only one? I guess 165:9300 is actually the same host right?
I would change the elasticsearch-graylog.conf to say: 1. discovery.zen.ping.unicast.hosts: ["172.16.1.166:9300"] The same for the actual elasticsearch.yml, that should not list any other nodes if you don't have them, especially not the graylog2 client node. Then it should simply discover the cluster. In fact, I would probably leave out the elasticsearch_config_file option, and configure everything in the graylog2.conf. Here's what I would configure: elasticsearch_cluster_name = graylog2 elasticsearch_node_name = graylog2-server elasticsearch_node_master = false elasticsearch_node_data = false elasticsearch_transport_tcp_port = 9350 elasticsearch_http_enabled = false elasticsearch_discovery_zen_ping_multicast_enabled = false elasticsearch_discovery_zen_ping_unicast_hosts = 172.1.16.166:9300 Basically all of these except the last two lines are the default values for those settings. You should also be able to see the graylog2 server node join the cluster in the elasticsearch log output. On Wed, Feb 5, 2014 at 5:54 PM, Scotty H <[email protected]> wrote: > Bigdesk screenshot. <http://i.imgur.com/WvxRiTl.png> > > -- > 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/groups/opt_out. > -- 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/groups/opt_out.
