Logstash with X-Pack

Elastic Stack Logstash
1

Dear All,

I have elk stack with difference machine
[Client - beat] - [VM1 - Logstash | 192.168.33.101] - [VM2 - ES and Kibana | 192.168.33.102]

I have install x-pack plugin for logstash, es, and kibana.
and have success test curl with this command.

curl --user logstash_system:changeme '192.168.33.102:9200'

but if running from logstash. if show error, logstash send log to localhost:9200 instead send to 192.168.33.102:9200.

Here the error:
[2017-06-21T08:15:41,552][INFO ][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck_url=>http://logstash_system:xxxxxx@localhost:9200/, :path=>"/"}
[2017-06-21T08:15:41,560][WARN ][logstash.outputs.elasticsearch] Attempted to resurrect connection to dead ES instance, but got an error. {:url=>#<URI::HTTP:0x790d79b0 URL:http://logstash_system:xxxxxx@localhost:9200/>, :error_type=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError, :error=>"Elasticsearch Unreachable: [http://logstash_system:xxxxxx@localhost:9200/][Manticore::SocketException] Connection refused (Connection refused)"}

Here my configure:

input {
  beats {
    port => 5044
  }
}
output {
  elasticsearch { 
    hosts => ["192.168.33.102:9200"]
    user => logstash_internal
    password => changeme
  }
  stdout {
    codec => rubydebug 
  }
}

can someone give me clue?

Thank you.

2

The username is different too (logstash_system vs. logstash_internal). Are you really running Logstash with the configuration you think?

3

yes. I put right crendential. But thanks for reply my thread.

I solved this issue by disable health check in conf/logstash.yml
just put this code in end of file;

xpack.monitoring.enabled: false

4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.