Unable to start logstash after SSL config

-- The start-up result is RESULT.
May 03 22:50:44 ip-172-26-2-38 kibana[18148]: {"type":"response","@timestamp":"2020-05-03T22:50:44Z","tags":,"pid":1814
May 03 22:50:51 ip-172-26-2-38 logstash[31241]: Sending Logstash logs to /var/log/logstash which is now configured via lo
May 03 22:50:52 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:52,263][WARN ][logstash.config.source.multilocal] Ignor
May 03 22:50:52 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:52,395][INFO ][logstash.runner ] Starting Logs
May 03 22:50:54 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:54,390][INFO ][logstash.monitoring.internalpipelinesour
May 03 22:50:54 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:54,395][INFO ][logstash.monitoring.internalpipelinesour
May 03 22:50:54 ip-172-26-2-38 kibana[18148]: {"type":"response","@timestamp":"2020-05-03T22:50:54Z","tags":,"pid":1814
May 03 22:50:55 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:55,871][INFO ][org.reflections.Reflections] Reflections
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:56,275][INFO ][logstash.outputs.elasticsearch][main] El
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:56,355][WARN ][logstash.outputs.elasticsearch][main] Re
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:56,368][INFO ][logstash.outputs.elasticsearch][main] ES
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:56,375][WARN ][logstash.outputs.elasticsearch][main] De
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:56,448][INFO ][logstash.outputs.elasticsearch][main] Ne
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:56,524][INFO ][logstash.outputs.elasticsearch][main] Us
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:56,598][INFO ][logstash.outputs.elasticsearch][main] At
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:56,624][WARN ][org.logstash.instrument.metrics.gauge.La
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:56,643][INFO ][logstash.javapipeline ][main] Startin
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: warning: thread "Ruby-0-Thread-6: :1" terminated with exception (report_o
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError:
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: perform_request at /usr/share/logstash/vendor/bundle/
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: perform_request_to_url at /usr/share/logstash/vendor/bundle/
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: perform_request at /usr/share/logstash/vendor/bundle/
lines 1131-1158/1229 96%
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError:
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: perform_request at /usr/share/logstash/vendor/bundle/
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: perform_request_to_url at /usr/share/logstash/vendor/bundle/
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: perform_request at /usr/share/logstash/vendor/bundle/
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: with_connection at /usr/share/logstash/vendor/bundle/
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: perform_request at /usr/share/logstash/vendor/bundle/
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: Pool at /usr/share/logstash/vendor/bundle/
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: exists? at /usr/share/logstash/vendor/bundle/
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: rollover_alias_exists? at /usr/share/logstash/vendor/bundle/
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: maybe_create_rollover_alias at /usr/share/logstash/vendor/bundle/
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: setup_ilm at /usr/share/logstash/vendor/bundle/
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: setup_after_successful_connection at /usr/share/logstash/vendor/bundle/
May 03 22:50:56 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:56,784][ERROR][logstash.agent ] An exception
May 03 22:50:58 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:58,305][WARN ][logstash.outputs.elasticsearch] You are
May 03 22:50:58 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:58,420][WARN ][logstash.outputs.elasticsearch][.monitor
May 03 22:50:58 ip-172-26-2-38 logstash[31241]: ** WARNING ** You have enabled encryption but DISABLED certificate verifi
May 03 22:50:58 ip-172-26-2-38 logstash[31241]: ** WARNING ** To make sure your data is secure change :ssl_certificate_ve
May 03 22:50:58 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:58,472][INFO ][logstash.outputs.elasticsearch][.monitor
May 03 22:50:58 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:58,531][WARN ][logstash.outputs.elasticsearch][.monitor
May 03 22:50:58 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:58,538][INFO ][logstash.outputs.elasticsearch][.monitor
May 03 22:50:58 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:58,547][WARN ][logstash.outputs.elasticsearch][.monitor
May 03 22:50:58 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:58,574][INFO ][logstash.outputs.elasticsearch][.monitor
May 03 22:50:58 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:58,584][INFO ][logstash.javapipeline ][.monitoring-l
May 03 22:50:58 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:58,922][INFO ][logstash.inputs.beats ][main] Beats i
May 03 22:50:58 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:58,977][INFO ][logstash.javapipeline ][.monitoring-l
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:59,386][ERROR][logstash.javapipeline ][main] Pipelin
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:59,400][ERROR][logstash.agent ] Failed to exe
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:59,418][INFO ][logstash.outputs.elasticsearch][main] El
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:59,400][ERROR][logstash.agent ] Failed to exe
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:59,418][INFO ][logstash.outputs.elasticsearch][main] El
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:59,454][WARN ][logstash.outputs.elasticsearch][main] Re
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:59,459][INFO ][logstash.outputs.elasticsearch][main] ES
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:59,460][WARN ][logstash.outputs.elasticsearch][main] De
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:59,483][INFO ][logstash.outputs.elasticsearch][main] Ne
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:59,498][INFO ][logstash.outputs.elasticsearch][main] Us
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:59,499][INFO ][logstash.javapipeline ][main] Startin
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:59,535][INFO ][logstash.outputs.elasticsearch][main] At
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: warning: thread "Ruby-0-Thread-22: :1" terminated with exception (report_
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError:
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: perform_request at /usr/share/logstash/vendor/bundle/
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: perform_request_to_url at /usr/share/logstash/vendor/bundle/
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: perform_request at /usr/share/logstash/vendor/bundle/
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: with_connection at /usr/share/logstash/vendor/bundle/
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: perform_request at /usr/share/logstash/vendor/bundle/
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: Pool at /usr/share/logstash/vendor/bundle/
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: exists? at /usr/share/logstash/vendor/bundle/
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: rollover_alias_exists? at /usr/share/logstash/vendor/bundle/
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: maybe_create_rollover_alias at /usr/share/logstash/vendor/bundle/
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: setup_ilm at /usr/share/logstash/vendor/bundle/
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: setup_after_successful_connection at /usr/share/logstash/vendor/bundle/
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:59,554][INFO ][logstash.inputs.beats ][main] Beats i
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:59,631][FATAL][logstash.runner ] An unexpected
May 03 22:50:59 ip-172-26-2-38 logstash[31241]: [2020-05-03T22:50:59,647][ERROR][org.logstash.Logstash ] java.lang.Ill
May 03 22:50:59 ip-172-26-2-38 systemd[1]: logstash.service: Main process exited, code=exited, status=1/FAILURE
May 03 22:50:59 ip-172-26-2-38 systemd[1]: logstash.service: Failed with result 'exit-code'.
May 03 22:51:00 ip-172-26-2-38 systemd[1]: logstash.service: Service hold-off time over, scheduling restart.
May 03 22:50:59 ip-172-26-2-38 systemd[1]: logstash.service: Main process exited, code=exited, status=1/FAILURE
May 03 22:50:59 ip-172-26-2-38 systemd[1]: logstash.service: Failed with result 'exit-code'.
May 03 22:51:00 ip-172-26-2-38 systemd[1]: logstash.service: Service hold-off time over, scheduling restart.
May 03 22:51:00 ip-172-26-2-38 systemd[1]: logstash.service: Scheduled restart job, restart counter is at 39.
-- Subject: Automatic restarting of a unit has been scheduled

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