You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the affected version of Logstash is 7.9 (or earlier), or if it is NOT using the bundled JDK or using the 'no-jdk' version in 7.10 (or higher), please provide the following information:
JVM version (java -version)
JVM installation source (e.g. from the Operating System's package manager, from source, etc).
Value of the LS_JAVA_HOME environment variable if set.
OS version (uname -a if on a Unix-like system):
Amazon Linux 2
Description of the problem including expected versus actual behavior:
$ cd /usr/share/logstash/bin
$ ./logstash-plugin install logstash-input-kinesis logstash-codec-gzip_lines
Using bundled JDK: /usr/share/logstash/jdk
Validating logstash-input-kinesis
Validating logstash-codec-gzip_lines
Resolving mixin dependencies
WARN: Unresolved or ambiguous specs during Gem::Specification.reset:
date (>= 0)
Available/installed versions of this gem:
- 3.3.4
- 3.3.3
WARN: Clearing out unresolved specs. Try 'gem cleanup <gem>'
Please report a bug if this causes problems.
Installing logstash-input-kinesis, logstash-codec-gzip_lines
Installation successful
Steps to reproduce:
Please include a minimal but complete recreation of the problem,
including (e.g.) pipeline definition(s), settings, locale, etc. The easier
you make for us to reproduce it, the more likely that somebody will take the
time to look at it.
Logstash information:
Please include the following information:
bin/logstash --version
)Plugins installed: (
bin/logstash-plugin list --verbose
)JVM (e.g.
java -version
):If the affected version of Logstash is 7.9 (or earlier), or if it is NOT using the bundled JDK or using the 'no-jdk' version in 7.10 (or higher), please provide the following information:
java -version
)LS_JAVA_HOME
environment variable if set.OS version (
uname -a
if on a Unix-like system):Description of the problem including expected versus actual behavior:
Steps to reproduce:
Please include a minimal but complete recreation of the problem,
including (e.g.) pipeline definition(s), settings, locale, etc. The easier
you make for us to reproduce it, the more likely that somebody will take the
time to look at it.
Provide logs (if relevant):
Related discuss: https://discuss.elastic.co/t/unresolved-or-ambiguous-specs-during-gem-specification-reset-date-0-but-cannot-run-gem-command-to-resolve/351931
The text was updated successfully, but these errors were encountered: