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

Support for logstash 6.x and 7.x needed #87

Open
BillGrim opened this issue Jun 18, 2019 · 11 comments
Open

Support for logstash 6.x and 7.x needed #87

BillGrim opened this issue Jun 18, 2019 · 11 comments

Comments

@BillGrim
Copy link

I trying to upgrade ELK 5.5.2 to ELK 6.8 or ELK 7.1, but get error messages shown below when running ./bin/logstash -t -f config/logstash.conf with logstash 7.1.
error message:

[2019-06-18T17:59:33,192][ERROR][logstash.plugins.registry] Tried to load a plugin's code, but failed. {:exception=>#<LoadError: no such file to load -- i18n/core_ext/string/interpolate>, :path=>"logstash/filters/fix_protocol", :type=>"filter", :name=>"fix_protocol"}
[2019-06-18T17:59:33,202][FATAL][logstash.runner          ] The given configuration is invalid. Reason: Couldn't find any filter plugin named 'fix_protocol'. Are you sure this is correct? Trying to load the fix_protocol filter plugin resulted in this error: no such file to load -- i18n/core_ext/string/interpolate
[2019-06-18T17:59:33,211][ERROR][org.logstash.Logstash    ] java.lang.IllegalStateException: Logstash stopped processing because of an error: (SystemExit) exit

I've already installed fix_protocol plugin with ./bin/logstash-plugin install logstash-filter-fix_protocol, and got result Validating logstash-filter-fix_protocol Installing logstash-filter-fix_protocol Installation successful

So I think it is a problem related to version mis-compatibility.

I'd appreciate it if anyone can add a pull request to this plugin. Thanks.

@nktl
Copy link

nktl commented Jul 23, 2019

+1, same problem here

@zandabanda
Copy link

+1

@daino3
Copy link
Contributor

daino3 commented Aug 16, 2019

@cbusbey - you guys want to take ownership of this project? Unlikely I'll be maintaining this going forward.

@cbusbey
Copy link
Contributor

cbusbey commented Aug 19, 2019

Of course. We would gladly merge a pr from the community to address this issue.

@ronyv
Copy link

ronyv commented Sep 13, 2019

Getting the same issue on logstash version 7.3. It was working fine with version 6.6.0.
Any updates on this issue ???
Is there any other FIX message parser plugins available for Logstash ?

Any help on this will be greatly appreciated!

@nktl
Copy link

nktl commented Sep 13, 2019

We are very desperate to get it up and running with modern ELK too, at the moment simply considering running separate logstash 6.6 instance just for this thing....

@lechaimwilson
Copy link

+1

@zandabanda
Copy link

zandabanda commented Sep 18, 2019

Could this be related to jruby 9.2.5.0 -> 9.2.6.0 (see Logstash 6.7.0 release notes: https://www.elastic.co/guide/en/logstash/6.8/logstash-6-7-0.html)

https://github.com/elastic/logstash/pull/10425/files

Assuming this breaks in going from Logstash 6.6 -> 6.7

@ourcookiemonster
Copy link

The error we see when trying to use the plugin in logstash-7.4.2 is the following:

[2019-11-15T16:39:20,984][ERROR][logstash.plugins.registry] Tried to load a plugin's code, but failed. {:exception=>#<LoadError: no such file to load -- i18n/core_ext/string/interpolate>, :path=>"logstash/filters/fix_protocol", :type=>"filter", :name=>"fix_protocol"}

It is not clear what the plug-in's dependency to i18n is since we were able to workaround the issue by simply placing an empty file in this location:
logstash-7.4.2\vendor\bundle\jruby\2.5.0\gems\i18n-1.7.0\lib\i18n\core_ext\string\interpolate.rb

Alternatively the source it may be looking for is from an older version of the i18n gem... you can find it here:
https://github.com/ruby-i18n/i18n/tree/0.6/lib/i18n/core_ext/string

Everything appears to be working by adding either a blank file or the old gem's interpolate.rb file. Your mileage may vary of course, we've only used this workaround in a development environment and have no familiarity with this plug-ins source code.

@michael-doubez
Copy link

It seems to be related to ruby version support:
ruby-i18n/i18n#299

@michael-doubez
Copy link

#89

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

No branches or pull requests

9 participants