Hi Jochen,
Thanks for your reply. I got confused bit while trying other
posts and issue is not resolved. could you please help to configure and how
to define it in,
elasticsearch_network_host =
elasticsearch_network_bind_host =
elasticsearch_network_publish_host =
Graylog clusters example as,
Master node1 : graylog-1 (192.168.100.177)
node2: graylog-2 (192.168.100.178)
node3: graylog-3 (192.168.100.179)
elasticsearch clusters example as,
node1 : es-1 (192.168.100.62)
node2: es-2 (192.168.100.63)
On Friday, April 15, 2016 at 2:44:15 PM UTC+5:30, Jochen Schalanda wrote:
>
> Hi Rajkumar,
>
> the error message states that your Elasticsearch nodes (at least es.node-1)
> is not able to connect back to Graylog with the host name graylod-1 on
> port 9350. Make sure that the Elasticsearch nodes are able to communicate
> with Graylog on graylod-1:9350 (maybe there's a typo in the host name).
>
> If you need Graylog to announce another host name for the Elasticsearch
> nodes to connect to, please take a look at the elasticsearch_network_*
> settings in the Graylog configuration file:
> https://github.com/Graylog2/graylog2-server/blob/1.3.4/misc/graylog2.conf#L179-L186
>
> Cheers,
> Jochen
>
> On Friday, 15 April 2016 09:50:07 UTC+2, raj kumar wrote:
>>
>> Hi guys,
>>
>> We are running Graylog production setup with 3 graylog nodes and
>> 2 elasticsearch nodes.
>>
>> 1. I am not able to access graylog GUI, but the services are
>> running fine in graylog clusters
>>
>> 2. ES cluster is in green and data is logging, also i can access
>> the cluster status from any graylog node using curl -XGET es.node-1:9200/
>>
>>
>> Graylog master node erroe:
>>
>> INFO [zen] [graylog2-server] failed to send join request to master
>> [[es.node-1][ZYdi_m85TkCwWN-AkqwnvA][es.node-1][inet[/es.node-1:9300]]{master=true}],
>>
>> reason
>> [RemoteTransportException[[es.node-1][inet[/es.node-1:9300]][internal:discovery/zen/join]];
>>
>> nested: ConnectTransportException[[graylog2-server][inet[/graylod-1:9350]]
>> connect_timeout[30s]]; nested: NoRouteToHostException[No route to host]; ]
>>
>> elasticsearch:
>>
>> ][INFO ][transport ] [Harold H. Harold] bound_address
>> {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/es.node-1:9300]}
>> [INFO ][discovery ] [Harold H. Harold]
>> elasticsearch/S7n9z36wSWiS2vk1muCAhQ
>> [INFO ][cluster.service ] [Harold H. Harold] new_master [Harold
>> H. Harold][S7n9z36wSWiS2vk1muCAhQ][localhost][inet[/es.node-1:9300]],
>> reason: zen-disco-join (elected_as_master)
>> [INFO ][http ] [Harold H. Harold] bound_address
>> {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/es.node-1:9200]}
>> [INFO ][node ] [Harold H. Harold] started
>> [INFO ][gateway ] [Harold H. Harold] recovered [0]
>> indices into cluster_state
>> [INFO ][node ] [Harold H. Harold] stopping ...
>> [INFO ][node ] [Harold H. Harold] stopped
>> [INFO ][node ] [Harold H. Harold] closing ...
>> [INFO ][node ] [Harold H. Harold] closed
>>
>>
>> Thanks & Regards,
>> Rajkumar V
>>
>
--
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/09568fea-2394-43f5-8035-e2f3f1a3a34c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
