Logstash running and failing w/o apparent errors in logs on Docker/Fargate

After resolving my previous errors the logstash application is starting successfully, connecting with Elasticsearch on Elastic Cloud, validating the licenses successfully, starting the pipelines, and metrics, and successfully running a healthcheck; then a sigterm is issued and the process is killed. I've set the logs to "debug" and have not found any issues.

The ECS Container Healthcheck runs successfully with a 200 response status code, then shortly thereafter, a sigterm is issued:

[2019-10-08T22:13:18,844][DEBUG][logstash.agent ] API HTTP Request {:status=>200, :request_method=>"GET", :path_info=>"/", :query_string=>"pretty", :http_version=>"HTTP/1.1", :http_accept=>"/"}

[2019-10-08T22:13:20,141][DEBUG][org.logstash.execution.PeriodicFlush] Pushing flush onto pipeline.

[2019-10-08T22:13:20,449][DEBUG][logstash.agent ] Converging pipelines state {:actions_count=>0}

[2019-10-08T22:13:20,588][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ParNew"}

[2019-10-08T22:13:20,588][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ConcurrentMarkSweep"}

[2019-10-08T22:13:25,141][DEBUG][org.logstash.execution.PeriodicFlush] Pushing flush onto pipeline.

[2019-10-08T22:13:25,455][DEBUG][logstash.agent ] Converging pipelines state {:actions_count=>0}

[2019-10-08T22:13:25,593][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ParNew"}

[2019-10-08T22:13:25,593][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ConcurrentMarkSweep"}

[2019-10-08T22:13:30,141][DEBUG][org.logstash.execution.PeriodicFlush] Pushing flush onto pipeline.

[2019-10-08T22:13:30,444][DEBUG][logstash.agent ] Converging pipelines state {:actions_count=>0}

[2019-10-08T22:13:30,599][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ParNew"}

[2019-10-08T22:13:30,600][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ConcurrentMarkSweep"}

[2019-10-08T22:13:35,141][DEBUG][org.logstash.execution.PeriodicFlush] Pushing flush onto pipeline.

[2019-10-08T22:13:35,443][DEBUG][logstash.agent ] Converging pipelines state {:actions_count=>0}

[2019-10-08T22:13:35,605][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ParNew"}

[2019-10-08T22:13:35,605][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ConcurrentMarkSweep"}

[2019-10-08T22:13:40,141][DEBUG][org.logstash.execution.PeriodicFlush] Pushing flush onto pipeline.

[2019-10-08T22:13:40,444][DEBUG][logstash.agent ] Converging pipelines state {:actions_count=>0}

[2019-10-08T22:13:40,610][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ParNew"}

[2019-10-08T22:13:40,610][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ConcurrentMarkSweep"}

[2019-10-08T22:13:42,030][WARN ][logstash.runner ] SIGTERM received. Shutting down.

logstash.yml

node.name: Fargate-Logstash

cloud.id:
cloud.auth: logstash_admin_user:${logstash_admin}

http.host: "0.0.0.0"
http.port: 9600
log.level: debug
xpack.monitoring.enabled: true
xpack.monitoring.elasticsearch.hosts: ["Elasticsearch host URL on Elastic Cloud" ]
xpack.monitoring.elasticsearch.username: logstash_application_user
xpack.monitoring.elasticsearch.password: ${es_password}

xpack.management.enabled: true
xpack.management.pipeline.id: ["rawlogs", ".monitoring-logstash"]
xpack.management.elasticsearch.hosts: [ "Elasticsearch host URL on Elastic Cloud" ]
xpack.management.elasticsearch.username: logstash_admin_user
xpack.management.elasticsearch.password: ${logstash_admin}

Ugh, I found the problem, it was a misconfiguration in AWS.

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