On Thu, Jan 7, 2016 at 2:59 PM, David Birdsong <[email protected]> wrote:
> 3242 != 3234 > > Also, make sure these are separate processes with fully configured and > separate share_dirs. > > The same process will quickly spam itself into a tizzy very fast. > Also, be careful w/ wiring two heka's together w/ a message_matcher of 'TRUE'. Some of the internal messages shouldn't be forwarded blindly. I'm having trouble recalling which ones--I think some of the serialized dashboard outputs are bad to forward to other heka's. > > > On Thu, Jan 7, 2016 at 2:55 PM, Emily Gu <[email protected]> wrote: > >> Hi David, >> >> Thanks for your quick reply. My apology that I mixed questions together. >> >> Let's solve this TcpInput issue first. >> >> tcp_input.toml >> ============ >> >> [tcp_in:3242] >> >> type = "TcpInput" >> >> splitter = "HekaFramingSplitter" >> >> decoder = "ProtobufDecoder" >> >> address = ":3242" >> >> >> tcp_output.toml >> >> ============ >> >> >> [tcp_out:3234] >> >> type = "TcpOutput" >> >> message_matcher = "TRUE" >> >> address = "127.0.0.1:3234" >> >> >> [tcp_heka_output_log] >> >> type = "FileOutput" >> >> message_matcher = "TRUE" >> >> path = "/tmp/output.log" >> >> perm = "664" >> >> encoder = "tcp_heka_output_encoder" >> >> >> [tcp_heka_output_encoder] >> >> type = "PayloadEncoder" >> >> append_newlines = false >> >> >> I have the client program to send messages to "127.0.0.1:3234" and no >> content in output.log generated. Am I doing anything wrong? >> >> >> Thanks, >> >> Emily >> >> >> >> >> >> >> On Thu, Jan 7, 2016 at 2:09 PM, David Birdsong <[email protected]> >> wrote: >> >>> 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 <[email protected]> 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]> 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 >>>> [email protected] >>>> https://mail.mozilla.org/listinfo/heka >>>> >>>> >>> >> >
_______________________________________________ Heka mailing list [email protected] https://mail.mozilla.org/listinfo/heka
