Logstash pod is not coming up once the pipeline status is running

Logstash is deployed in a kubernetes cluster and Elastic Search is deployed in another cluster.
For transferring the log files from logstash to Elasticsearch using outputs in the logstash.conf file.

// output {
// elasticsearch {
// hosts => ""
// index => "log4j-%{+YYYY.MM.dd}"
// user => "
// password => "*******"
// }
// stdout {

// }

Pipeline in the logstash logs is started and in running status but the logstash pod is not coming up to ready status.

Logs from logstash:

logstash.javapipeline ][main] Pipeline started {"pipeline.id"=>"main"}
logstash.agent ] Pipelines running {:count=>1, :running_pipelines=>[:main], :non_running_pipelines=>}
org.logstash.beats.Server][main][c0385372af50163076bd202d1f67af2354a4aad3ffe76d447a7f03c18cadc76b] Starting server on port: 5044
logstash.runner ] SIGTERM received. Shutting down.
logstash.javapipeline ][main] Pipeline terminated {"pipeline.id"=>"main"}
logstash.pipelinesregistry] Removed pipeline from registry successfully {:pipeline_id=>:main}
logstash.runner Logstash shut down.

Describing the LogStash Pod:
Normal Started 62s kubelet Started container logstash
Warning Unhealthy 2s kubelet Readiness probe failed: Get "": dial tcp connect: connection refused

There are no errors but logstash is not in ready status.

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