I can only receive data when the Socket connection is broken.

[tzqtzq]

• Version: 6.3
• Operating System: Linux
• Config File (if you have sensitive info, please remove it):
  input {
  tcp{
  host => "XX.XXX.XXX.XX"
  port => "514"
  codec => plain{
  charset=> "UTF-8"
  }
  }
  }
  output {
  stdout {codec => rubydebug}
  }

When I use TelnetClient to write data to port 514 or re-acquire each socket to see the data in the console, if I always use a Socket, the logstah console will not output the content unless I break the write process. The data will be output. Logstash-input-tpc How to handle the data in a long connection is a message in logstash

[SpencerLN]

Seeing a similar issue with:
Logstash version 6.5.4
Operating System: Linux (running in a Docker container)
Config File (if you have sensitive info, please remove it):

input {
  udp {
    port => 5144
    tags => ["${LS_NODE_NAME}-received","kafka-receiver", "input-5144-udp"]
  }
  tcp {
    port => 5144
    tags => ["${LS_NODE_NAME}-received","kafka-receiver", "input-5144-tcp"]
  }
  udp {
    port => 5145
    tags => ["${LS_NODE_NAME}-received","kafka-receiver", "input-5145-udp"]
  }
  tcp {
    port => 5145
    tags => ["${LS_NODE_NAME}-received","kafka-asa-receiver", "input-5145-tcp"]
  }
  udp {
    port => 5146
    tags => ["${LS_NODE_NAME}-received","kafka-asa-receiver", "input-5146-udp"]
  }
  tcp {
    port => 5146
    tags => ["${LS_NODE_NAME}-received","kafka-asa-receiver", "input-5146-tcp"]
  }
}
filter {
}
output {
  kafka {
    bootstrap_servers => "${LS_NODE_NAME}:9092"
    topic_id => "raw"
    codec => "json"
  }
}

[2019-01-11T15:52:25,337][ERROR][logstash.inputs.tcp ] Error in Netty pipeline: java.io.IOException: Connection reset by peer
[2019-01-11T15:52:26,723][ERROR][logstash.inputs.tcp ] Error in Netty pipeline: java.io.IOException: Connection reset by peer
[2019-01-11T15:52:26,857][ERROR][logstash.inputs.tcp ] Error in Netty pipeline: java.io.IOException: Connection reset by peer
[2019-01-11T15:52:28,447][ERROR][logstash.inputs.tcp ] Error in Netty pipeline: java.io.IOException: Connection reset by peer
[2019-01-11T15:52:29,375][ERROR][logstash.inputs.tcp ] Error in Netty pipeline: java.io.IOException: Connection reset by peer
[2019-01-11T15:52:31,250][ERROR][logstash.inputs.tcp ] Error in Netty pipeline: java.io.IOException: Connection reset by peer
[2019-01-11T15:52:33,882][ERROR][logstash.inputs.tcp ] Error in Netty pipeline: java.io.IOException: Connection reset by peer
[2019-01-11T15:54:05,729][ERROR][logstash.inputs.tcp ] Error in Netty pipeline: java.io.IOException: Connection reset by peer

[jsvd]

Hi folks, can you try updating the tcp plugin to 5.2.2 ? #142 should fix this

[georgejdanforth]

Hi, I am also experiencing the same issue as @tzqtzq on version 6.0.6 of the tcp plugin. Any solutions here?

• Logstash version: 7.11.1
• OS: Linux (docker)
• conf:

input {
    tcp {
        mode => "server"
        port => 9563
    }
}

output {
    stdout { }
}

[georgejdanforth]

Hmm nevermind, after poking around a bit and reading this issue, appending \n to my data seems to get things moving.