elastic / elastic/logstash

Logstash container fails to start

Open
#16,563 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
14.9k
Forks
3.5k
Avg merge
1d 4h
Merged PRs (30d)
88

Description

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.(/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](https://www.elastic.co/guide/en/logstash/current/logstash-8-15-2.html) I could see that `docker env variables` related issues are fixed with`v8.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?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.