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
When we upgraded from 0.12.32 to 0.12.33 of fluentd, the fluent-plugin-s3 was no longer able to start, throwing a NoMethodError exception during check_apikeys. Downgrading back to 0.12.32 resolves the issue. Removing log_level trace, or setting it to a lesser level (debug) also resolve the issue.
Evidently, there has been some change or regression by 0.12.33 that makes this plugin fail with log_level set to trace.
I am able to reproduce this on 3 different machines.
Running fluentd with --dry-run does not raise this exception.
Version 0.12.34 still exhibits this issue.
When we upgraded from 0.12.32 to 0.12.33 of fluentd, the fluent-plugin-s3 was no longer able to start, throwing a NoMethodError exception during check_apikeys. Downgrading back to 0.12.32 resolves the issue. Removing
log_level trace
, or setting it to a lesser level (debug
) also resolve the issue.Evidently, there has been some change or regression by 0.12.33 that makes this plugin fail with
log_level
set to trace.I am able to reproduce this on 3 different machines.
Running fluentd with
--dry-run
does not raise this exception.Version 0.12.34 still exhibits this issue.
Looking at the changes between 0.12.32 and 0.12.33, it appears to be caused by this issue fluent/fluentd#1478 and commit fluent/fluentd@6fc58dd
As for what aspect of the aws-sdk is attempting to call
#write
or#<<
and why#write
is undefined remains a mystery to me.Gem versions:
Configuration section:
The text was updated successfully, but these errors were encountered: