Logstash starts and stops within seconds while running it as a service

Elastic Stack Logstash
1

The logstash.err file spits out the following error

Faraday::ConnectionFailed: Connection refused - Connection refused
call at /opt/logstash/vendor/bundle/jruby/1.9/gems/faraday-0.9.0/lib/faraday/adapter/net_http.rb:44
build_response at /opt/logstash/vendor/bundle/jruby/1.9/gems/faraday-0.9.0/lib/faraday/rack_builder.rb:139
run_request at /opt/logstash/vendor/bundle/jruby/1.9/gems/faraday-0.9.0/lib/faraday/connection.rb:377
perform_request at /opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.1/lib/elasticsearch/transport/transport/http/faraday.rb:24
call at org/jruby/RubyProc.java:271
perform_request at /opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.1/lib/elasticsearch/transport/transport/base.rb:187
perform_request at /opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.1/lib/elasticsearch/transport/transport/http/faraday.rb:20
perform_request at /opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-transport-1.0.1/lib/elasticsearch/transport/client.rb:102
perform_request at /opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-api-1.0.1/lib/elasticsearch/api/namespace/common.rb:21
get_template at /opt/logstash/vendor/bundle/jruby/1.9/gems/elasticsearch-api-1.0.1/lib/elasticsearch/api/actions/indices/get_template.rb:24
template_exists? at /opt/logstash/lib/logstash/outputs/elasticsearch/protocol.rb:132
template_install at /opt/logstash/lib/logstash/outputs/elasticsearch/protocol.rb:21
register at /opt/logstash/lib/logstash/outputs/elasticsearch.rb:259
each at org/jruby/RubyArray.java:1613
outputworker at /opt/logstash/lib/logstash/pipeline.rb:220
start_outputs at /opt/logstash/lib/logstash/pipeline.rb:152

2

It looks like you've configured an Elasticsearch input or output that tries to connect to something that isn't running. This shouldn't stop Logstash though.

3

then whats the solution for this error?

4

then whats the solution for this error?

Either the configuration is incorrect or reality isn't what it should be. For example, a service that should be running isn't actually running. Without further details it's impossible to be more specific.