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
Description of the problem including expected versus actual behavior:
In Logstash 7.15.0 Bundler got updated to 2.x and along came a functionality of locking the bundle (Gemfile).
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.
Using bundled JDK: /home/kares/workspace/work/elastic/logstash-7.15.0/jdk
[FATAL] 2021-11-25 13:28:18.046 [main] Logstash - Logstash was unable to start due to an unexpected Gemfile change.
If you are a user, this is a bug.
If you are a logstash developer, please try restarting logstash with the `--enable-local-plugin-development` flag set.
NOTE: work-around is to run with --enable-local-plugin-development ...
edit Gemfile (change source)
bin/logstash --enable-local-plugin-development -e "" to re-lock the bundle
the next time the usual bin/logstash -e "" will now work
The text was updated successfully, but these errors were encountered:
Logstash information: >=
7.15.0
Description of the problem including expected versus actual behavior:
In Logstash 7.15.0 Bundler got updated to 2.x and along came a functionality of locking the bundle (
Gemfile
).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.
bin/logstash -e ""
workingbin/logstash -e ""
again -> startup failsProvide logs (if relevant):
NOTE: work-around is to run with
--enable-local-plugin-development
...bin/logstash --enable-local-plugin-development -e ""
to re-lock the bundlebin/logstash -e ""
will now workThe text was updated successfully, but these errors were encountered: