Hi, make sure to also set the elasticsearch_network_host setting in Graylog's configuration file to the public IP address of your Graylog node (i. e. 172.31.83.21).
Cheers, Jochen On Tuesday, 24 May 2016 16:23:54 UTC+2, Chen Jie Peng wrote: > > Hi, I built a graylog testing env on azure, and the setup information as > following. > > > > GRAY LOG SERVER v2.0.1 (172.31.83.21) ---> > ElasticSearch(2.3.2)&Mongodb(3.2.6) - node(172.31.83.20) > > > > ES Config: > > network.host: 172.31.83.20 > > http.port: 9200 > > discovery.zen.ping.multicast.enabled: false > > discovery.zen.ping.unicast.hosts: ["172.31.83.20:9300"] > > discovery.zen.minimum_master_nodes: 1 > > > > Graylog Config: > > rest_listen_uri = http://172.31.83.21:12900/ > > elasticsearch_discovery_zen_ping_unicast_hosts = 172.31.83.20:9300 > > > > But when I start the graylog server, it seemed that the server could not > work properly, with the error message below, could anyone give a hand? thx > a lot. > > > > 2016-05-24 21:00:20,243 INFO : org.elasticsearch.discovery.zen - > [yumes-e74a31a7-011a-48e6-9563-7aaad5320202] failed to send join request to > master > [{SGHAZUIOS_83_20}{EMGDMR3rSIO2M8gD3aR-yg}{172.31.83.20}{172.31.83.20:9300}], > reason > [RemoteTransportException[[SGHAZUIOS_83_20][172.31.83.20:9300][internal:discovery/zen/join]]; > > nested: > ConnectTransportException[[yumes-e74a31a7-011a-48e6-9563-7aaad5320202][ > 127.0.0.1:9350] connect_timeout[30s]]; nested: > NotSerializableExceptionWrapper[connect_exception: Connection refused: / > 127.0.0.1:9350]; ] > -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/734d005e-c9d8-496e-bb3b-b8e469829cce%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
