Logstash log


(rattisyam) #1

Hi team,
below is the error I am getting when i am running my conf file of logstash even though my elasticsearch server is reachable.
Please help me on this error as i am new to ELK. Thank you.

[2018-02-13T11:03:57,359][WARN ][logstash.outputs.elasticsearch] UNEXPECTED POOL ERROR {:e=>#<LogStash::Outputs::ElasticSearch::HttpClient::Pool::NoConnectionAvailableError: No Available connections>}
[2018-02-13T11:03:57,359][ERROR][logstash.outputs.elasticsearch] Attempted to send a bulk request to elasticsearch, but no there are no living connections in the connection pool. Perhaps Elasticsearch is unreachable or down? {:error_message=>"No Available connections", :class=>"LogStash::Outputs::ElasticSearch::HttpClient::Pool::NoConnectionAvailableError", :will_retry_in_seconds=>64}
[2018-02-13T11:03:57,456][INFO ][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck_url=>http://52.207.72.107:9200/, :path=>"/"}
root@ip-172-31-43-243:/var/log/logstash# cat logstash-plain.log | tail -10
[2018-02-13T12:21:11,974][INFO ][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck_url=>http://54.208.46.115:9200/, :path=>"/"}
[2018-02-13T12:21:12,378][WARN ][logstash.outputs.elasticsearch] Attempted to resurrect connection to dead ES instance, but got an error. {:url=>"http://54.89.237.179:9200/", :error_type=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError, :error=>"Elasticsearch Unreachable: [http://54.89.237.179:9200/][Manticore::ConnectTimeout] connect timed out"}
[2018-02-13T12:21:13,378][INFO ][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck_url=>http://54.89.237.179:9200/, :path=>"/"}
[2018-02-13T12:21:13,413][WARN ][logstash.outputs.elasticsearch] Attempted to resurrect connection to dead ES instance, but got an error. {:url=>"http://54.88.145.244:9200/", :error_type=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError, :error=>"Elasticsearch Unreachable: [http://54.88.145.244:9200/][Manticore::ConnectTimeout] connect timed out"}
[2018-02-13T12:21:13,644][WARN ][logstash.outputs.elasticsearch] Attempted to resurrect connection to dead ES instance, but got an error. {:url=>"http://52.0.9.221:9200/", :error_type=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError, :error=>"Elasticsearch Unreachable: [http://52.0.9.221:9200/][Manticore::ConnectTimeout] connect timed out"}
[2018-02-13T12:21:14,413][INFO ][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck_url=>http://54.88.145.244:9200/, :path=>"/"}
[2018-02-13T12:21:14,644][INFO ][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck_url=>http://52.0.9.221:9200/, :path=>"/"}
[2018-02-13T12:21:15,337][WARN ][logstash.outputs.elasticsearch] Attempted to resurrect connection to dead ES instance, but got an error. {:url=>"http://52.207.72.107:9200/", :error_type=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError, :error=>"Elasticsearch Unreachable: [http://52.207.72.107:9200/][Manticore::ConnectTimeout] connect timed out"}
[2018-02-13T12:21:16,337][INFO ][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck_url=>http://52.207.72.107:9200/, :path=>"/"}
[2018-02-13T12:21:22,023][WARN ][logstash.outputs.elasticsearch] Attempted to resurrect connection to dead ES instance, but got an error. {:url=>"http://54.208.46.115:9200/", :error_type=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError, :error=>"Elasticsearch Unreachable: [http://54.208.46.115:9200/][Manticore::ConnectTimeout] connect timed out"}
root@ip-172-31-43-243:/var/log/logstash# clear


(Walker) #2

Can you post your ElasticSearch and Logstash pipeline configs?


(system) #3

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