Logstash code 503

Elastic Stack Logstash
1

Bonjour à tous,

J'ai besoin d'aide car depuis quelques jours j'ai le souci suivant :

Dec 11 08:54:12 s-log-p-i02-fr logstash[1011]: [2019-12-11T08:54:12,757][INFO ][logstash.outputs.elasticsearch][main] retrying failed action with response code: 503 ({"type"=>"unavailable_shards_exception", "reason"=>"[filebeat-7.4.2-2019.12.03][0] primary shard is not active Timeout: [1m], request: [BulkShardRequest [[filebeat-7.4.2-2019.12.03][0]] containing [110] requests]"})
Dec 11 08:54:12 s-log-p-i02-fr logstash[1011]: [2019-12-11T08:54:12,758][INFO ][logstash.outputs.elasticsearch][main] retrying failed action with response code: 503 ({"type"=>"unavailable_shards_exception", "reason"=>"[filebeat-7.4.2-2019.12.03][0] primary shard is not active Timeout: [1m], request: [BulkShardRequest [[filebeat-7.4.2-2019.12.03][0]] containing [110] requests]"})
Dec 11 08:54:12 s-log-p-i02-fr logstash[1011]: [2019-12-11T08:54:12,758][INFO ][logstash.outputs.elasticsearch][main] retrying failed action with response code: 503 ({"type"=>"unavailable_shards_exception", "reason"=>"[filebeat-7.4.2-2019.12.03][0] primary shard is not active Timeout: [1m], request: [BulkShardRequest [[filebeat-7.4.2-2019.12.03][0]] containing [110] requests]"})
Dec 11 08:54:12 s-log-p-i02-fr logstash[1011]: [2019-12-11T08:54:12,758][INFO ][logstash.outputs.elasticsearch][main] retrying failed action with response code: 503 ({"type"=>"unavailable_shards_exception", "reason"=>"[filebeat-7.4.2-2019.12.03][0] primary shard is not active Timeout: [1m], request: [BulkShardRequest [[filebeat-7.4.2-2019.12.03][0]] containing [110] requests]"})
Dec 11 08:54:12 s-log-p-i02-fr logstash[1011]: [2019-12-11T08:54:12,758][INFO ][logstash.outputs.elasticsearch][main] retrying failed action with response code: 503 ({"type"=>"unavailable_shards_exception", "reason"=>"[filebeat-7.4.2-2019.12.03][0] primary shard is not active Timeout: [1m], request: [BulkShardRequest [[filebeat-7.4.2-2019.12.03][0]] containing [110] requests]"})
Dec 11 08:54:12 s-log-p-i02-fr logstash[1011]: [2019-12-11T08:54:12,759][INFO ][logstash.outputs.elasticsearch][main] retrying failed action with response code: 503 ({"type"=>"unavailable_shards_exception", "reason"=>"[filebeat-7.4.2-2019.12.03][0] primary shard is not active Timeout: [1m], request: [BulkShardRequest [[filebeat-7.4.2-2019.12.03][0]] containing [110] requests]"})
Dec 11 08:54:12 s-log-p-i02-fr logstash[1011]: [2019-12-11T08:54:12,759][INFO ][logstash.outputs.elasticsearch][main] retrying failed action with response code: 503 ({"type"=>"unavailable_shards_exception", "reason"=>"[filebeat-7.4.2-2019.12.03][0] primary shard is not active Timeout: [1m], request: [BulkShardRequest [[filebeat-7.4.2-2019.12.03][0]] containing [110] requests]"})
Dec 11 08:54:12 s-log-p-i02-fr logstash[1011]: [2019-12-11T08:54:12,759][INFO ][logstash.outputs.elasticsearch][main] retrying failed action with response code: 503 ({"type"=>"unavailable_shards_exception", "reason"=>"[filebeat-7.4.2-2019.12.03][0] primary shard is not active Timeout: [1m], request: [BulkShardRequest [[filebeat-7.4.2-2019.12.03][0]] containing [110] requests]"})
Dec 11 08:54:12 s-log-p-i02-fr logstash[1011]: [2019-12-11T08:54:12,759][INFO ][logstash.outputs.elasticsearch][main] retrying failed action with response code: 503 ({"type"=>"unavailable_shards_exception", "reason"=>"[filebeat-7.4.2-2019.12.03][0] primary shard is not active Timeout: [1m], request: [BulkShardRequest [[filebeat-7.4.2-2019.12.03][0]] containing [110] requests]"})
Dec 11 08:54:12 s-log-p-i02-fr logstash[1011]: [2019-12-11T08:54:12,760][INFO ][logstash.outputs.elasticsearch][main] Retrying individual bulk actions that failed or were rejected by the previous bulk request. {:count=>110}

pouvez-vous m'aider ?

Merci,

2
  • Your Elasticsearch is refusing to index the events, and indicates in its response that there are no shards available.
  • Logstash is retrying the failed request repeatedly, hoping that your Elasticsearch will eventually accept the events
  • You need to resolve the health of your Elasticsearch cluster before the requests will begin succeeding

Auto-translate to French:

  • Votre Elasticsearch refuse d'indexer les événements et indique dans sa réponse qu'aucun fragment n'est disponible.
  • Logstash réessaye la demande qui a échoué à plusieurs reprises, en espérant que votre Elasticsearch accepte finalement les événements
  • Vous devez résoudre l'intégrité de votre cluster Elasticsearch avant que les demandes ne commencent à réussir
3

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