Logstash full DLQ, невозможно подключиться к Elasticsearch - PullRequest
Новая
       6

Logstash full DLQ, невозможно подключиться к Elasticsearch

0 голосов
/ 02 сентября 2018

Я выяснил, у меня есть полный DLQ в logstash сегодня. Я получаю эти ошибки: 

[2018-09-02T10:05:27,667][ERROR][logstash.outputs.elasticsearch] Encountered a retryable error. Will Retry with exponential backoff  {:code=>502, :url=>"http://elk-es-data-hot-2.dc2.company.local:9200/_bulk"}
[2018-09-02T10:05:27,702][ERROR][logstash.outputs.elasticsearch] Encountered a retryable error. Will Retry with exponential backoff  {:code=>502, :url=>"http://elk-es-data-hot-1.dc2.company.local:9200/_bulk"}
[2018-09-02T10:05:27,993][INFO ][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck_url=>http://admin:xxxxxx@elk-es-data-hot-1.dc1.company.local:9200/, :path=>"/"}
[2018-09-02T10:05:27,997][WARN ][logstash.outputs.elasticsearch] Attempted to resurrect connection to dead ES instance, but got an error. {:url=>"http://admin:xxxxxx@elk-es-data-hot-1.dc1.company.local:9200/", :error_type=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError, :error=>"Got response code '502' contacting Elasticsearch at URL 'http://elk-es-data-hot-1.dc1.company.local:9200/'"}
[2018-09-02T10:05:27,997][INFO ][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck_url=>http://admin:xxxxxx@elk-es-data-hot-1.dc2.company.local:9200/, :path=>"/"}
[2018-09-02T10:05:27,999][WARN ][logstash.outputs.elasticsearch] Attempted to resurrect connection to dead ES instance, but got an error. {:url=>"http://admin:xxxxxx@elk-es-data-hot-1.dc2.company.local:9200/", :error_type=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError, :error=>"Got response code '502' contacting Elasticsearch at URL 'http://elk-es-data-hot-1.dc2.company.local:9200/'"}
[2018-09-02T10:05:27,999][INFO ][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck_url=>http://admin:xxxxxx@elk-es-data-hot-2.dc2.company.local:9200/, :path=>"/"}
[2018-09-02T10:05:28,002][WARN ][logstash.outputs.elasticsearch] Attempted to resurrect connection to dead ES instance, but got an error. {:url=>"http://admin:xxxxxx@elk-es-data-hot-2.dc2.company.local:9200/", :error_type=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError, :error=>"Got response code '502' contacting Elasticsearch at URL 'http://elk-es-data-hot-2.dc2.company.local:9200/'"}

До упругости (на том же узле) есть прокси nginx с базовой аутентификацией, ничего более. Я подумал, проблема в том, что объем больше максимального размера тела nginx, поэтому я настроил: 

client_max_body_size 128m;

Кто-нибудь знает, как решить эту проблему?

...