Hi Kef, there is a bug in Graylog2 0.90.0 and 0.91.0-rc.1 which prevents the correct use of the elasticsearch_discovery_zen_ping_unicast_hosts setting in your graylog2.conf if it only contains a single host, see https://github.com/Graylog2/graylog2-server/issues/734 for details. This will be fixed in Graylog2 0.90.1 and 0.91.1.
Please also check if the Elasticsearch configuration file referenced by elasticsearch_config_file in your graylog2.conf contains the correct value for the discovery.zen.ping.unicast.hosts setting. You can also use this setting to work around the bug with the elasticsearch_discovery_zen_ping_unicast_hosts setting in your graylog2.conf. Cheers, Jochen Am Freitag, 3. Oktober 2014 13:35:36 UTC+2 schrieb Kef Risen: > > Hello! > > I had reconfigure elasticsearch on 127.0.0.1 address. > > Then change address in my graylog conf (I had try many options): > > elasticsearch_discovery_zen_ping_multicast_enabled = false > elasticsearch_discovery_zen_ping_unicast_hosts = 127.0.0.1:9300 > > But graylog trying to connect on old address: > > 2014-10-03 12:45:19,456 DEBUG: org.elasticsearch.discovery.zen - > [graylog2-server] filtered ping responses: (filter_client[true], > filter_data[false]) > --> target [[Moira > MacTaggert][VTufQwgnQAKgwqjx5zd9Kg][inet[/176.9.xxx.xxx:9300]]], master > [[Moira MacTaggert][VTufQwgnQAKgwqjx5zd9Kg][inet[/176.9.xxx.xxx:9300]]] > 2014-10-03 12:45:19,462 WARN : org.elasticsearch.discovery.zen - > [graylog2-server] failed to connect to master [[Moira > MacTaggert][VTufQwgnQAKgwqjx5zd9Kg][inet[/176.9.xxx.xxx:9300]]], retrying... > > Can you say what I doing wrong? > > Thanks! > -- 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.
