# After executing sudo bin/logstash -f /home/web/ghost\_files/trans\_client\_auth.config I get this error

**URL:** <https://discuss.elastic.co/t/after-executing-sudo-bin-logstash-f-home-web-ghost-files-trans-client-auth-config-i-get-this-error/167282>\
**Category:** Logstash\
**Created:** [February 6, 2019, 12:06pm UTC](https://discuss.elastic.co/t/after-executing-sudo-bin-logstash-f-home-web-ghost-files-trans-client-auth-config-i-get-this-error/167282 "2019-02-06T12:06:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sachin\_augustine](https://avatars.discourse-cdn.com/v4/letter/s/b2d939/32.png) [@sachin\_augustine](https://discuss.elastic.co/u/sachin_augustine)\
**Post date:** [February 6, 2019, 12:06pm UTC](https://discuss.elastic.co/t/after-executing-sudo-bin-logstash-f-home-web-ghost-files-trans-client-auth-config-i-get-this-error/167282/1 "2019-02-06T12:06:25Z")

</div>

WARNING: Could not find logstash.yml which is typically located in $LS\_HOME/config or /etc/logstash. You can specify the path using --path.settings. Continuing using the defaults  
Could not find log4j2 configuration at path /usr/share/logstash/config/log4j2.properties. Using default config which logs errors to the console  
[ERROR] 2019-02-06 17:32:58.411 [[main]-pipeline-manager] pipeline - Error registering plugin {:pipeline\_id=\>"main", :plugin=\>"#\<LogStash::OutputDelegator:0x6deb9986 @namespaced\_metric=#\<LogStash::Instrument::NamespacedMetric:0x67a3fc5d @metric=#\<LogStash::Instrument::Metric:0x4ff9b3d6 @collector=#\<LogStash::Instrument::Collector:0xc001450 @agent=nil, @metric\_store=#\<LogStash::Instrument::MetricStore:0x3d169bff @store=#\<Concurrent:🗺0x00000000000fb0 entries=4 default\_proc=nil\>, @structured\_lookup\_mutex=#Mutex:0x452fc914, @fast\_lookup=#\<Concurrent:🗺0x00000000000fb4 entries=87 default\_proc=nil\>\>\>\>, @namespace\_name=[:stats, :pipelines, :main, :plugins, :outputs, :"660a26e50fc97a5cc7bec4ce8b5bd0187c7ec995d29ead28e6b15126e105c268"]\>, @metric=#\<LogStash::Instrument::NamespacedMetric:0x4b648b59 @metric=#\<LogStash::Instrument::Metric:0x4ff9b3d6 @collector=#\<LogStash::Instrument::Collector:0xc001450 @agent=nil, @metric\_store=#\<LogStash::Instrument::MetricStore:0x3d169bff @store=#\<Concurrent:🗺0x00000000000fb0 entries=4 default\_proc=nil\>, @structured\_lookup\_mutex=#Mutex:0x452fc914, @fast\_lookup=#\<Concurrent:🗺0x00000000000fb4 entries=87 default\_proc=nil\>\>\>\>, @namespace\_name=[:stats, :pipelines, :main, :plugins, :outputs]\>, @logger=#\<LogStash::Logging::Logger:0x79783e90 @logger=#ssl\_certificate\_verification=\>true, sniffing=\>false, sniffing\_delay=\>5, timeout=\>60, pool\_max=\>1000, pool\_max\_per\_route=\>100, resurrect\_delay=\>5, validate\_after\_inactivity=\>10000, http\_compression=\>false, ssl=\>true\>\>, @in\_counter=org.jruby.proxy.org.logstash.instrument.metrics.counter.LongCounter$Proxy2 - name: in value:0, @id="660a26e50fc97a5cc7bec4ce8b5bd0187c7ec995d29ead28e6b15126e105c268", @time\_metric=org.jruby.proxy.org.logstash.instrument.metrics.counter.LongCounter$Proxy2 - name: duration\_in\_millis value:0, @metric\_events=#\<LogStash::Instrument::NamespacedMetric:0x6e7c85b4 @metric=#\<LogStash::Instrument::Metric:0x4ff9b3d6 @collector=#\<LogStash::Instrument::Collector:0xc001450 @agent=nil, @metric\_store=#\<LogStash::Instrument::MetricStore:0x3d169bff @store=#\<Concurrent:🗺0x00000000000fb0 entries=4 default\_proc=nil\>, @structured\_lookup\_mutex=#Mutex:0x452fc914, @fast\_lookup=#\<Concurrent:🗺0x00000000000fb4 entries=87 default\_proc=nil\>\>\>\>, @namespace\_name=[:stats, :pipelines, :main, :plugins, :outputs, :"660a26e50fc97a5cc7bec4ce8b5bd0187c7ec995d29ead28e6b15126e105c268", :events]\>, @output\_class=LogStash::Outputs::ElasticSearch\>", :error=\>"Unrecognized SSL message, plaintext connection?", :thread=\>"#\<Thread:0x190316c3@/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:245 run\>"}  
[ERROR] 2019-02-06 17:32:58.415 [[main]-pipeline-manager] pipeline - Pipeline aborted due to error {:pipeline\_id=\>"main", :exception=\>#\<Manticore::UnknownException: Unrecognized SSL message, plaintext connection?\>, :backtrace=\>["/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/manticore-0.6.1-java/lib/manticore/response.rb:37:in `block in initialize'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/manticore-0.6.1-java/lib/manticore/response.rb:79:in`call'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.0.2-java/lib/logstash/outputs/elasticsearch/http\_client/manticore\_adapter.rb:74:in `perform_request'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.0.2-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:287:in`perform\_request\_to\_url'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.0.2-java/lib/logstash/outputs/elasticsearch/http\_client/pool.rb:241:in `block in healthcheck!'", "org/jruby/RubyHash.java:1343:in`each'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.0.2-java/lib/logstash/outputs/elasticsearch/http\_client/pool.rb:237:in `healthcheck!'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.0.2-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:337:in`update\_urls'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.0.2-java/lib/logstash/outputs/elasticsearch/http\_client/pool.rb:70:in `start'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.0.2-java/lib/logstash/outputs/elasticsearch/http_client.rb:292:in`build\_pool'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.0.2-java/lib/logstash/outputs/elasticsearch/http\_client.rb:60:in `initialize'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.0.2-java/lib/logstash/outputs/elasticsearch/http_client_builder.rb:101:in`create\_http\_client'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.0.2-java/lib/logstash/outputs/elasticsearch/http\_client\_builder.rb:97:in `build'", "/usr/share/logstash/vendor/bundle/jru/output_delegator_strategies/shared.rb:9:in`register'", "/usr/share/logstash/logstash-core/lib/logstash/output\_delegator.rb:43:in `register'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:343:in`register\_plugin'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:354:in `block in register_plugins'", "org/jruby/RubyArray.java:1734:in`each'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:354:in `register_plugins'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:743:in`maybe\_setup\_out\_plugins'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:364:in `start_workers'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:288:in`run'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:248:in `block in start'"], :thread=\>"#\<Thread:0x190316c3@/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:245 run\>"}  
[ERROR] 2019-02-06 17:32:58.427 [Ruby-0-Thread-1: /usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/stud-0.0.23/lib/stud/task.rb:22] agent - Failed to execute action {:id=\>:main, :action\_type=\>LogStash::ConvergeResult::FailedAction, :message=\>"Could not execute action: LogStash::PipelineAction::Create/pipeline\_id:main, action\_result: false", :backtrace=\>nil}

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [February 7, 2019, 1:59pm UTC](https://discuss.elastic.co/t/after-executing-sudo-bin-logstash-f-home-web-ghost-files-trans-client-auth-config-i-get-this-error/167282/2 "2019-02-07T13:59:06Z")

</div>

What does the configuration look like?

---

<div class="post-metadata">

**Author:** ![sachin\_augustine](https://avatars.discourse-cdn.com/v4/letter/s/b2d939/32.png) [@sachin\_augustine](https://discuss.elastic.co/u/sachin_augustine)\
**Post date:** [February 8, 2019, 11:30am UTC](https://discuss.elastic.co/t/after-executing-sudo-bin-logstash-f-home-web-ghost-files-trans-client-auth-config-i-get-this-error/167282/3 "2019-02-08T11:30:00Z")

</div>

I found the solution in the hosts in had put https instead of http

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 8, 2019, 11:30am UTC](https://discuss.elastic.co/t/after-executing-sudo-bin-logstash-f-home-web-ghost-files-trans-client-auth-config-i-get-this-error/167282/4 "2019-03-08T11:30:10Z")

</div>

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