netstat output:
Code: Select all
[root@naw02logserver01 config]# netstat -antp | egrep '(3515)|(5544)'
[root@naw02logserver01 config]#Code: Select all
[root@naw02logserver01 config]# tail /var/log/logstash/logstash.log
{:timestamp=>"2017-07-02T00:08:41.199000+0000", :message=>"retrying failed action with response code: 503", :level=>:warn}
{:timestamp=>"2017-07-02T00:08:41.199000+0000", :message=>"retrying failed action with response code: 503", :level=>:warn}
{:timestamp=>"2017-07-02T00:08:41.199000+0000", :message=>"retrying failed action with response code: 503", :level=>:warn}
{:timestamp=>"2017-07-02T00:08:41.199000+0000", :message=>"retrying failed action with response code: 503", :level=>:warn}
I found these cluster names in the logstash and elasticsearch configs:I found the problem, here is the solution:
1) on ES config, need to define the cluster name (default is "elasticsearch" )
2) on LS config file, add cluster definition as the above the example:
output {
elasticsearch
{ host => "zslesvm09:9300"
cluster => } # cluster_name defined @ ES
stdout { }
}
"cluster" is introduced by the latest LS 1.5.2.
Before we use the default definition that makes the LS cannot find the correct ES.
Thanks.
Code: Select all
[root@naw02logserver01 config]# cat elasticsearch.yml | grep cluster.name
cluster.name: nagios_elasticsearch
[root@naw02logserver01 config]# cat ../../logstash/etc/conf.d/999_outputs.conf | grep cluster
cluster => '53d62043-9568-47de-af43-7e7635380d8a'
