This is probably not an error. When a new connection is made to a TcpInput, it spins up a goroutine to handle the connection, and, if a decoder is specified and `syncronous_decode` is not set to true in the config, another goroutine to run the decoder. When the connection is closed, the decoder will spin down and both goroutines will exit. This results in the "Decoder '<decoder-identifier>': stopped" message being emitted.
It's likely that the log messages are just an indication that one of the TcpInput's TCP connections has been closed by the upstream sender. -r On 06/07/2016 07:55 PM, 张晔 wrote:
Hello, When collecting log data, I came accoss such error: 6月 07 17:00:32 log1 hekad[18549]: 2016/06/07 17:00:32 Decoder 'eru_tcp_input-JsonDecoder-10.10.188.200': stopped JsonDecoder is one of my self-defined decoder. The WORST is I can't reproduce such error in my test machine and journalctl give so little info I don't know what went wrong. Is there any way to get more error msg for the whole decoder? I don't think use pcall in each statement is a good idea. Cheers, Dantepy _______________________________________________ Heka mailing list [email protected] https://mail.mozilla.org/listinfo/heka
_______________________________________________ Heka mailing list [email protected] https://mail.mozilla.org/listinfo/heka
