This is expected. A new decoder will be spun up for every TCP connection
made, and when the connection is closed then the decoder will be shut
down. Four connections made and closed would emit four "Decoder stopped"
messages such as you're seeing.
-r
On 01/07/2016 02:04 PM, Emily Gu wrote:
Actually after I changed the port and ran TcpInput, I saw the following
in the console output:
2016/01/07 13:49:54 Input started: tcp_in:5656
2016/01/07 13:56:53 Decoder 'tcp_in:5656-ProtobufDecoder-127.0.0.1': stopped
2016/01/07 13:56:53 Decoder 'tcp_in:5656-ProtobufDecoder-127.0.0.1': stopped
2016/01/07 14:00:16 Decoder 'tcp_in:5656-ProtobufDecoder-127.0.0.1': stopped
2016/01/07 14:00:16 Decoder 'tcp_in:5656-ProtobufDecoder-127.0.0.1': stopped
Is the above alright? I'm programmally writing to TCP port 5656 and
would like to see the output in a file.
Thanks,
Emily
On Thu, Jan 7, 2016 at 1:09 PM, Emily Gu <[email protected]
<mailto:[email protected]>> wrote:
Dear Heka,
The example of TcpOutput plugin worked before. Now it stops working.
The error I got is:
2016/01/07 13:04:25 Plugin 'tcp_out:9612' error: can't send record:
can't connect: dial tcp 127.0.0.1:9612 <http://127.0.0.1:9612>:
getsockopt: connection refused
The config I used is:
[tcp_out:9612]
type = "TcpOutput"
message_matcher = "TRUE"
address = "127.0.0.1:9612 <http://127.0.0.1:9612>"
Thanks for your timely help!
Emily
_______________________________________________
Heka mailing list
[email protected]
https://mail.mozilla.org/listinfo/heka
_______________________________________________
Heka mailing list
[email protected]
https://mail.mozilla.org/listinfo/heka
