Closed anand3493 closed 2 years ago
@ashie Can u plz share the impact because of this error ? Also may I know in which release we can expect this fix?
@ashie Thanks for fixing this issue. Plz share the impact and ETA for this fix
Thanks for your report!
This error will be reproduced only when read_bytes_limit_per_second
is specified.
It's occurred after detecting log rotation and waiting remaining data which might be written by other application.
Probably log lost or duplication won't be occurred.
It will be fixed at v1.14.1 (will be released at the end of Sep.)
@ashie Do you have any word on the v1.14.1 release date?
It will be released end of this month.
@ashie @kenhys I have upgraded the fluentd to v1.14.1 .. On doing so when the new pod is getting started , facing the below error:
can u plz advise. Thanks in advance
Describe the bug
We are using EFK stack for logging with our AWS EKS cluster. We have recently upgrade the fluentd version to 1.13.3 and found this error in fluentd pod logs.
[error]: #0 [in_tail_container_logs] Unexpected error raised. Stopping the timer. title=:in_tail_close_watcher error_class=NoMethodError error="undefined method `eof?' for nil:NilClass"
To Reproduce
The logs are flowing but given a period of time, the mentioned issue is creeping up badly.
Expected behavior
NO error
Your Environment
Your Configuration
Your Error Log
Additional context
No response