-
Notifications
You must be signed in to change notification settings - Fork 31
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
US-ASCII error on default grok-pattern file #32
Comments
Same as #27 ??? |
I will check this issue later. |
Related to fluent/fluentd#1606 ? |
Released 2.1.4 |
great, thanks it worked. |
openstack-gerrit
pushed a commit
to openstack/kolla
that referenced
this issue
Nov 16, 2017
For ubuntu, we actually use fluentd 0.14.22 and ruby 2.1.10 now. Thus, we should use the specific gem version for the plugins: - fluent-plugin-rewrite-tag-filter:2.0.0 According to the README.md of this plugin[1] It shows: ---------------------------------------------------------- | fluent-plugin-rewrite-tag-filter | Fluentd | Ruby | |----------------------------------|------------|--------| | >= 2.0.0 | >= v0.14.2 | >= 2.1 | | < 2.0.0 | >= v0.12.0 | >= 1.9 | ---------------------------------------------------------- - fluent-plugin-grok-parser:2.1.4 When using the fluent-plugin-rewrite-tag-filter 2.0.0 to fix this bug, another bug[1] which is the same as this one[2] was triggered. According to https://github.com/fluent/fluent-plugin-grok-parser, it shows: --------------------------------------------------- | fluent-plugin-grok-parser | fluentd | Ruby | |---------------------------|------------|--------| | >= 1.0.0 | >= v0.14.0 | >= 2.1 | | < 1.0.0 | >= v0.12.0 | >= 1.9 | --------------------------------------------------- We actually use fluentd 0.14.22 now, but the version of fluent-plugin-grok-parser is still pinned in 0.3.1. So we need to upgrade the fluent-plugin-grok-parser to 2.1.4. [1] https://github.com/fluent/fluent-plugin-rewrite-tag-filter [2] http://paste.openstack.org/show/626145/ [3] fluent/fluent-plugin-grok-parser#32 backport: pike Change-Id: I47985113fe732569d640a262ca832c6edc8c2bb6 Partial-Bug: #1730664
openstack-gerrit
pushed a commit
to openstack/kolla
that referenced
this issue
Nov 22, 2017
For ubuntu, we actually use fluentd 0.14.22 and ruby 2.1.10 now. Thus, we should use the specific gem version for the plugins: - fluent-plugin-rewrite-tag-filter:2.0.0 According to the README.md of this plugin[1] It shows: ---------------------------------------------------------- | fluent-plugin-rewrite-tag-filter | Fluentd | Ruby | |----------------------------------|------------|--------| | >= 2.0.0 | >= v0.14.2 | >= 2.1 | | < 2.0.0 | >= v0.12.0 | >= 1.9 | ---------------------------------------------------------- - fluent-plugin-grok-parser:2.1.4 When using the fluent-plugin-rewrite-tag-filter 2.0.0 to fix this bug, another bug[1] which is the same as this one[2] was triggered. According to https://github.com/fluent/fluent-plugin-grok-parser, it shows: --------------------------------------------------- | fluent-plugin-grok-parser | fluentd | Ruby | |---------------------------|------------|--------| | >= 1.0.0 | >= v0.14.0 | >= 2.1 | | < 1.0.0 | >= v0.12.0 | >= 1.9 | --------------------------------------------------- We actually use fluentd 0.14.22 now, but the version of fluent-plugin-grok-parser is still pinned in 0.3.1. So we need to upgrade the fluent-plugin-grok-parser to 2.1.4. [1] https://github.com/fluent/fluent-plugin-rewrite-tag-filter [2] http://paste.openstack.org/show/626145/ [3] fluent/fluent-plugin-grok-parser#32 Change-Id: I47985113fe732569d640a262ca832c6edc8c2bb6 Partial-Bug: #1730664
yankcrime
pushed a commit
to stackhpc/kolla
that referenced
this issue
Feb 23, 2018
For ubuntu, we actually use fluentd 0.14.22 and ruby 2.1.10 now. Thus, we should use the specific gem version for the plugins: - fluent-plugin-rewrite-tag-filter:2.0.0 According to the README.md of this plugin[1] It shows: ---------------------------------------------------------- | fluent-plugin-rewrite-tag-filter | Fluentd | Ruby | |----------------------------------|------------|--------| | >= 2.0.0 | >= v0.14.2 | >= 2.1 | | < 2.0.0 | >= v0.12.0 | >= 1.9 | ---------------------------------------------------------- - fluent-plugin-grok-parser:2.1.4 When using the fluent-plugin-rewrite-tag-filter 2.0.0 to fix this bug, another bug[1] which is the same as this one[2] was triggered. According to https://github.com/fluent/fluent-plugin-grok-parser, it shows: --------------------------------------------------- | fluent-plugin-grok-parser | fluentd | Ruby | |---------------------------|------------|--------| | >= 1.0.0 | >= v0.14.0 | >= 2.1 | | < 1.0.0 | >= v0.12.0 | >= 1.9 | --------------------------------------------------- We actually use fluentd 0.14.22 now, but the version of fluent-plugin-grok-parser is still pinned in 0.3.1. So we need to upgrade the fluent-plugin-grok-parser to 2.1.4. [1] https://github.com/fluent/fluent-plugin-rewrite-tag-filter [2] http://paste.openstack.org/show/626145/ [3] fluent/fluent-plugin-grok-parser#32 backport: pike Change-Id: I47985113fe732569d640a262ca832c6edc8c2bb6 Partial-Bug: #1730664
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
since fluent version 0.14.17/0.14.18 with the fluent-plugin-grok-parser plugin 2.3.1, which is reading the default grok-patterns file, I get a /var/lib/gems/2.3.0/gems/fluent-plugin-grok-parser-2.1.3/lib/fluent/plugin/grok.rb:39:in `block in add_patterns_from_file': invalid byte sequence in US-ASCII (ArgumentError).
The default grok pattern file contains month where the german character "ä" ( May/März) is not us-ascii compatible. This was working with 0.14.16 with the same plugin version for fluent-plugin-grok-parser 2.3.1., but now it is crashing. I am using an Ubuntu container, where I have just changed the version number for fluentd and now it is crashing with: block in add_patterns_from_file': invalid byte sequence in US-ASCII (ArgumentError).
Any idea, what was changed?
Regards,
Olaf
The text was updated successfully, but these errors were encountered: