Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

8.14.0 xpack.management.pipeline.id * no longer working #16200

Open
Aqualie opened this issue Jun 6, 2024 · 1 comment
Open

8.14.0 xpack.management.pipeline.id * no longer working #16200

Aqualie opened this issue Jun 6, 2024 · 1 comment

Comments

@Aqualie
Copy link

Aqualie commented Jun 6, 2024

Logstash information:

Please include the following information:

  1. Logstash version (e.g. bin/logstash --version)
  2. 8.14.0
  3. Logstash installation source (e.g. built from source, with a package manager: DEB/RPM, expanded from tar or zip archive, docker)
  4. docker.elastic.co/logstash/logstash:8.14.0
  5. How is Logstash being run (e.g. as a service/service manager: systemd, upstart, etc. Via command line, docker/kubernetes)
  6. kubernetes

OS version (uname -a if on a Unix-like system): K8S 1.26.13

Description of the problem including expected versus actual behavior:
After upgrading from 8.13.0 to 8.14.0 logstash fails to start

Steps to reproduce:

  1. add the below configuration in logstash.yml to:
xpack.management.pipeline.id:
- '*'

Provide logs (if relevant):

ERROR: Pipeline id in `xpack.management.pipeline.id` must begin with a letter or underscore and contain only letters, underscores, dashes, and numbers. The asterisk wildcard `*` can also be used. Invalid ids: ["*"]
usage:
  bin/logstash -f CONFIG_PATH [-t] [-r] [] [-w COUNT] [-l LOG]
  bin/logstash --modules MODULE_NAME [-M "MODULE_NAME.var.PLUGIN_TYPE.PLUGIN_NAME.VARIABLE_NAME=VALUE"] [-t] [-w COUNT] [-l LOG]
  bin/logstash -e CONFIG_STR [-t] [--log.level fatal|error|warn|info|debug|trace] [-w COUNT] [-l LOG]
  bin/logstash -i SHELL [--log.level fatal|error|warn|info|debug|trace]
  bin/logstash -V [--log.level fatal|error|warn|info|debug|trace]
  bin/logstash --help
[2024-06-06T11:35:47,812][FATAL][org.logstash.Logstash    ] Logstash stopped processing because of an error: (SystemExit) exit
org.jruby.exceptions.SystemExit: (SystemExit) exit
        at org.jruby.RubyKernel.exit(org/jruby/RubyKernel.java:921) ~[jruby.jar:?]
        at org.jruby.RubyKernel.exit(org/jruby/RubyKernel.java:880) ~[jruby.jar:?]
        at usr.share.logstash.lib.bootstrap.environment.<main>(/usr/share/logstash/lib/bootstrap/environment.rb:90) ~[?:?]

@kaisecheng
Copy link
Contributor

@Aqualie Can you provide steps to reproduce the issue?

I tried with

docker run -d --name=ls -v /tmp/8_14_0/config/logstash.yml:/usr/share/logstash/config/logstash.yml:ro docker.elastic.co/logstash/logstash:8.14.0

and the following logstash.yml

xpack.management.enabled: true
xpack.management.pipeline.id:
  - '*'
xpack.management.logstash.poll_interval: 1s
xpack.management.elasticsearch.hosts: ["redacted"]
xpack.management.elasticsearch.username: redacted
xpack.management.elasticsearch.password: redacted

The container starts successfully

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants