Fluentd worker crashing on startup when connecting to Graylog #1479
Comments
sumith-aeropost
changed the title
|
Hi, I just got the same error when using this image. I'm not a Ruby programmer, but I've read somewhere that Fixnum class is deprecated. Maybe there is some Ruby version or GELF plugin version mismatch? If you check https://github.com/graylog-labs/gelf-rb/blob/master/lib/gelf/notifier.rb then you'll see there is Integer there. But the code in container is using Fixnum. I'll try to update stuff in image to newest versions in custom Dockerfile. Maybe this will do the trick. |
|
I've managed to work around this issue via the following Dockerfile + setting |
|
|
This is the chain of related events that led to the disaster:
Good news is that unlucky Fixnum was removed in last 3.0.1 gelf gem version on commit that should prepare it to ruby 2.4 deprecation: |
|
This issue has been automatically marked as stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days |
|
Is this issue resolved? |
Closes: fluent#1479 Feedback from @mszyzdek ref. fluent#1479 (comment) * graylog flavour of fluentd-kubernetes-daemonset uses gelf 3.0.0 and this version of gelf gem has Fixnum in code, graylog-labs/gelf-rb@7cc3cbb * in ruby 3.2 Fixnum was removed after previous deprecation in version 2.4 https://www.ruby-lang.org/en/news/2022/12/25/ruby-3-2-0-released/ * ruby in newest fluentd was upgraded to 3.2 fluent/fluentd-docker-image@4f1d5e8 so it also happened in fluentd-kubernetes-daemonset * gelf 3.0.0 cannot work with ruby 3.2+ so we can see sad error on container start Signed-off-by: Kentaro Hayashi <[email protected]>
Closes: fluent#1479 Feedback from @mszyzdek ref. fluent#1479 (comment) * graylog flavour of fluentd-kubernetes-daemonset uses gelf 3.0.0 and this version of gelf gem has Fixnum in code, graylog-labs/gelf-rb@7cc3cbb * in ruby 3.2 Fixnum was removed after previous deprecation in version 2.4 https://www.ruby-lang.org/en/news/2022/12/25/ruby-3-2-0-released/ * ruby in newest fluentd was upgraded to 3.2 fluent/fluentd-docker-image@4f1d5e8 so it also happened in fluentd-kubernetes-daemonset * gelf 3.0.0 cannot work with ruby 3.2+ so we can see sad error on container start Signed-off-by: Kentaro Hayashi <[email protected]>
Until Fluentd v1.8.0, However, So, we still need #219. Please note that if you are updating |
|
graylog-labs/gelf-rb#93 (comment) It would be better to use gelf_redux. |
Closes: fluent#1479 Feedback from @mszyzdek ref. fluent#1479 (comment) * graylog flavour of fluentd-kubernetes-daemonset uses gelf 3.0.0 and this version of gelf gem has Fixnum in code, graylog-labs/gelf-rb@7cc3cbb * in ruby 3.2 Fixnum was removed after previous deprecation in version 2.4 https://www.ruby-lang.org/en/news/2022/12/25/ruby-3-2-0-released/ * ruby in newest fluentd was upgraded to 3.2 fluent/fluentd-docker-image@4f1d5e8 so it also happened in fluentd-kubernetes-daemonset * gelf 3.0.0 cannot work with ruby 3.2+ so we can see sad error on container start NOTE: Even though gelf was updated to 3.1.0, still it has problem with reloading Fluentd configuration with SIGUSR2. This is known issue since Fluentd 1.8.0. ref. fluent/fluentd#2709 Signed-off-by: Kentaro Hayashi <[email protected]>
Describe the bug
We've installed Fluentd in our AWS EKS cluster, connecting to Graylog, and it was functioning well. However, two days ago, the fluentd worker unexpectedly crashed. Fluentd pod logs consistently display the following messages:
Any help would be appreciated on how we could fix this, can give further logs/code if necessary.
To Reproduce
Fluentd Pod logs
Expected behavior
fluentd needs to connect graylog instance. It was working fine for long time, suddenly crashed.
Your Environment
- Tag of using fluentd-kubernetes-daemonset: v1-debian-graylogYour Configuration
The text was updated successfully, but these errors were encountered: