logstash icon indicating copy to clipboard operation
logstash copied to clipboard

Logstash container fails to start

Open mohanss08 opened this issue 4 months ago • 4 comments

My Elasticsearch, Logstash and Kibana stack setup is based on Docker Compose and the version is - 8.15.2.

Logstash container always fails to start and throws the following error.

logstash  | ERROR: Failed to load settings file from "path.settings". Aborting... path.setting=/usr/share/logstash/config, exception=LogStash::ConfigurationError, message=>Cannot evaluate `${xpack.monitoring.elasticsearch.password}`. Replacement variable `xpack.monitoring.elasticsearch.password` is not defined in a Logstash secret store or as an Environment entry and there is no default value given.
logstash  | [FATAL] 2024-10-09 05:30:54.028 [main] Logstash - Logstash stopped processing because of an error: (SystemExit) exit
logstash  | org.jruby.exceptions.SystemExit: (SystemExit) exit
logstash  |     at org.jruby.RubyKernel.exit(org/jruby/RubyKernel.java:921) ~[jruby.jar:?]
logstash  |     at org.jruby.RubyKernel.exit(org/jruby/RubyKernel.java:880) ~[jruby.jar:?]
logstash  |     at usr.share.logstash.lib.bootstrap.environment.<main>(/usr/share/logstash/lib/bootstrap/environment.rb:90) ~[?:?]
logstash  | 2024/10/09 05:30:54 Setting 'xpack.monitoring.elasticsearch.password' from environment.
logstash  | 2024/10/09 05:30:54 Setting 'xpack.monitoring.enabled' from environment.
logstash  | 2024/10/09 05:30:54 Setting 'xpack.monitoring.elasticsearch.username' from environment.
logstash  | Using bundled JDK: /usr/share/logstash/jdk

It seems that Logstash cannot find or evaluate the variable ${xpack.monitoring.elasticsearch.password} which was working fine with v8.6.2 before the upgrade and it is working fine until with Logstash v8.12.2.

In the following release notes page - Logstash 8.15.2 Release Notes | Logstash Reference [8.15] | Elastic I could see that docker env variables related issues are fixed withv8.15.2 but it is not working as expected like old v8.12.2 and getting same above errors, when i start the container.

Please let me know whether I should wait for the next release?

mohanss08 avatar Oct 16 '24 06:10 mohanss08