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

Logstash is unable to start after upgrading to version 7.16.0 #13480

Closed
romain-chanu opened this issue Dec 8, 2021 · 1 comment · Fixed by #13481
Closed

Logstash is unable to start after upgrading to version 7.16.0 #13480

romain-chanu opened this issue Dec 8, 2021 · 1 comment · Fixed by #13481

Comments

@romain-chanu
Copy link

romain-chanu commented Dec 8, 2021

Logstash information:

Please include the following information:

  1. Logstash version (e.g. bin/logstash --version): 7.16.0

  2. Logstash installation source (e.g. built from source, with a package manager: DEB/RPM, expanded from tar or zip archive, docker): MacOS package

  3. How is Logstash being run (e.g. as a service/service manager: systemd, upstart, etc. Via command line, docker/kubernetes): Command line

Plugins installed: (bin/logstash-plugin list --verbose):

logstash-codec-avro (3.3.0)
logstash-codec-cef (6.2.3)
logstash-codec-collectd (3.1.0)
logstash-codec-dots (3.0.6)
logstash-codec-edn (3.1.0)
logstash-codec-edn_lines (3.1.0)
logstash-codec-es_bulk (3.1.0)
logstash-codec-fluent (3.4.1)
logstash-codec-graphite (3.0.6)
logstash-codec-json (3.1.0)
logstash-codec-json_lines (3.1.0)
logstash-codec-line (3.1.1)
logstash-codec-msgpack (3.1.0)
logstash-codec-multiline (3.1.1)
logstash-codec-netflow (4.2.2)
logstash-codec-plain (3.1.0)
logstash-codec-rubydebug (3.1.0)
logstash-filter-aggregate (2.10.0)
logstash-filter-anonymize (3.0.6)
logstash-filter-cidr (3.1.3)
logstash-filter-clone (4.1.1)
logstash-filter-csv (3.1.1)
logstash-filter-date (3.1.9)
logstash-filter-de_dot (1.0.4)
logstash-filter-dissect (1.2.1)
logstash-filter-dns (3.1.4)
logstash-filter-drop (3.0.5)
logstash-filter-elasticsearch (3.11.0)
logstash-filter-fingerprint (3.3.2)
logstash-filter-geoip (7.2.3)
logstash-filter-grok (4.4.0)
logstash-filter-http (1.0.2)
logstash-filter-json (3.2.0)
logstash-filter-kv (4.5.0)
logstash-filter-memcached (1.1.0)
logstash-filter-metrics (4.0.7)
logstash-filter-mutate (3.5.4)
logstash-filter-prune (3.0.4)
logstash-filter-ruby (3.1.7)
logstash-filter-sleep (3.0.7)
logstash-filter-split (3.1.8)
logstash-filter-syslog_pri (3.1.0)
logstash-filter-throttle (4.0.4)
logstash-filter-translate (3.3.0)
logstash-filter-truncate (1.0.4)
logstash-filter-urldecode (3.0.6)
logstash-filter-useragent (3.3.1)
logstash-filter-uuid (3.0.5)
logstash-filter-xml (4.1.2)
logstash-input-azure_event_hubs (1.4.0)
logstash-input-beats (6.2.1)
└── logstash-input-elastic_agent (alias)
logstash-input-couchdb_changes (3.1.6)
logstash-input-dead_letter_queue (1.1.5)
logstash-input-elasticsearch (4.12.1)
logstash-input-exec (3.3.3)
logstash-input-file (4.4.0)
logstash-input-ganglia (3.1.4)
logstash-input-gelf (3.3.0)
logstash-input-generator (3.0.6)
logstash-input-graphite (3.0.6)
logstash-input-heartbeat (3.1.1)
logstash-input-http (3.4.2)
logstash-input-http_poller (5.1.0)
logstash-input-imap (3.1.0)
logstash-input-jms (3.1.2)
logstash-input-pipe (3.0.7)
logstash-input-redis (3.7.0)
logstash-input-s3 (3.8.1)
logstash-input-snmp (1.2.8)
logstash-input-snmptrap (3.0.6)
logstash-input-sqs (3.1.3)
logstash-input-stdin (3.4.0)
logstash-input-syslog (3.5.0)
logstash-input-tcp (6.2.1)
logstash-input-twitter (4.0.3)
logstash-input-udp (3.5.0)
logstash-input-unix (3.0.7)
logstash-integration-elastic_enterprise_search (2.1.2)
 ├── logstash-output-elastic_app_search
 └──  logstash-output-elastic_workplace_search
logstash-integration-jdbc (5.1.6)
 ├── logstash-input-jdbc
 ├── logstash-filter-jdbc_streaming
 └── logstash-filter-jdbc_static
logstash-integration-kafka (10.8.1)
 ├── logstash-input-kafka
 └── logstash-output-kafka
logstash-integration-rabbitmq (7.3.0)
 ├── logstash-input-rabbitmq
 └── logstash-output-rabbitmq
logstash-output-cloudwatch (3.0.9)
logstash-output-csv (3.0.8)
logstash-output-elasticsearch (11.2.1)
logstash-output-email (4.1.1)
logstash-output-file (4.3.0)
logstash-output-graphite (3.1.6)
logstash-output-http (5.2.5)
logstash-output-lumberjack (3.1.9)
logstash-output-nagios (3.0.6)
logstash-output-null (3.0.5)
logstash-output-pipe (3.0.6)
logstash-output-redis (5.0.0)
logstash-output-s3 (4.3.5)
logstash-output-sns (4.0.7)
logstash-output-sqs (6.0.0)
logstash-output-stdout (3.1.4)
logstash-output-tcp (6.0.0)
logstash-output-udp (3.2.0)
logstash-output-webhdfs (3.0.6)
logstash-patterns-core (4.3.1)

JVM (e.g. java -version): bundled JDK.

OS version (uname -a if on a Unix-like system): Darwin Kernel Version 20.6.0

Description of the problem including expected versus actual behavior: Logstash is unable to start after upgrading to version 7.16.0.

Steps to reproduce:

  1. Using the following logstash.yml configuration:
http.enabled: true
http.host: 0.0.0.0
http.port: 9600
  1. Start Logstash version 7.16.0 and observe the below cryptic error message:
Your settings are invalid. Reason: super: no superclass method `validate' for #<LogStash::Setting::DeprecatedAlias:0x7d31b371>
  1. The problem is related to Secure API #13308. As per my understanding:
  • The http.* settings should be deprecated and it should not prevent Logstash from running.
  • The above error message is very cryptic and does not provide any useful information to the user regarding the problematic settings.
  1. A quick workaround would be to rename the http.* settings as per below:
Setting name (version < 7.16) Setting name (version = 7.16.0)
http.enabled api.enabled
http.environment api.environment
http.host api.http.host
http.port api.http.port
@kares
Copy link
Contributor

kares commented Dec 8, 2021

Thanks for the report, confirmed - setting (the deprecated) http.enabled:

# api.enabled: true
http.enabled: true

... is sufficient to trigger the issue

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

Successfully merging a pull request may close this issue.

3 participants