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
Fluentd worker crashing on startup when connecting to Graylog #1479
Comments
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:
|
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-graylog
Your Configuration
The text was updated successfully, but these errors were encountered: