You will need to supply more of your toml since you've asked about TcpOutput but then follow up asking about TcpInput.
Also, make sure you are not sending and receiving on the same heka instance. "that would be bad" On Thu, Jan 7, 2016 at 2:04 PM, Emily Gu <77.e...@gmail.com> 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 <77.e...@gmail.com> 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: getsockopt: connection refused >> >> >> The config I used is: >> >> [tcp_out:9612] >> >> type = "TcpOutput" >> >> message_matcher = "TRUE" >> >> address = "127.0.0.1:9612" >> >> >> Thanks for your timely help! >> >> Emily >> > > > _______________________________________________ > Heka mailing list > Heka@mozilla.org > https://mail.mozilla.org/listinfo/heka > >
_______________________________________________ Heka mailing list Heka@mozilla.org https://mail.mozilla.org/listinfo/heka
