-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Unresolved or ambiguous specs during Gem::Specification.reset: date (>= 0) #16095
Comments
We were able to workaround this one by forcing date cleanup prior installing the desired module
Note that in our case command is being used since this is part of the docker container config file at which afterwards you'll need to start logstash using command line since you're now using the command parameter |
Some news on this, we are facing the same problem, an gem cleanup does not help.
With a fresh 8.15.0.tgz I get already this: |
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: