Daijiro Fukuda

One cause of duplicate logs has been clarified and resolved with the following fix: * #4237 Please try v1.16.2 after the package is released. If you still experience duplicate logs...

Just in case, there is still a possibility of duplicate logs: * #4243 but I think it is not related to this issue and this issue is resolved by #4237....

@jamslinger Thanks for your report. Could you tell us some points? * Are the duplicated logs an entire file? or part of a file? * Does the duplication occur around...

We know that such an error occurs when a chunk file is corrupted due to an abnormal outage, etc. We are working on improving the feature for chunk file corruption...

Sorry for the delay. @vguaglione > If the worker is killed, I suspect all the of messages that were in the queue are lost. Is this a correct assumption? We...

@vascoosx I will close this issue as there will be no update for a while. If you are still experiencing this problem and know anything about how to reproduce it,...

We know that such an error occurs when a chunk file is corrupted due to an abnormal outage, etc. We are working on improving the feature for chunk file corruption...

I'm seeing..

Hmm, this log is not outputted. I don't know why... ``` [debug]: #0 fluent/log.rb:309:debug: 0.0s: Async::IO::Socket | Binding to # ``` In master, when launching Fluentd with this config, the...

https://github.com/socketry/async-io/blob/v1.34.3/lib/async/io/socket.rb#L157 At this point, somehow `Console.logger` is `Console::Terminal::Logger`, not `Fluent::Log::ConsoleAdapter`. I'm thinking about the possibility that the logger is not passed to the child task correctly.