# ERR Failed to publish events caused by: write tcp **URL:** \ **Category:** Logstash\ **Created:** [August 9, 2018, 6:15am UTC](https://discuss.elastic.co/t/err-failed-to-publish-events-caused-by-write-tcp/143636 "2018-08-09T06:15:26Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Gaurav\_Rishi](https://avatars.discourse-cdn.com/v4/letter/g/5f9b8f/32.png) [@Gaurav\_Rishi](https://discuss.elastic.co/u/Gaurav_Rishi)\ **Post date:** [August 9, 2018, 6:15am UTC](https://discuss.elastic.co/t/err-failed-to-publish-events-caused-by-write-tcp/143636/1 "2018-08-09T06:15:26Z")
Hi, I am continually getting an error in my file beat. Logs are writing at very very high speed. filebeat configuration ##########start############## filebeat: prospectors: - paths: - /logs/statistics.log document\_type: newlog ``` - paths: - /logs/states.log fields_under_root: true document_type: txnstatus fields: json: true input_type: log - paths: - /logs/instaproxy.log document_type: payment input_type: log - paths: - /var/log/secure document_type: audit-logs input_type: log ``` registry\_file: /var/lib/filebeat/registry output: logstash: hosts: ["10.143.5.41:5044","10.143.5.42:5044","10.143.5.43:5044","10.143.5.44:5044","10.143.5.45:5044","10.143.4.49:5044","10.143.63.47:5044","10.143.63.29:5044","10.143.63.26:5044"] #hosts: ["10.143.5.41:5045"] loadbalance: true worker: 6 shipper: logging: files: path: logs/mybeat name: mybeat.log rotateeverybytes: 524288000 # = 50MB #########END############### 2018-08-09T11:40:12+05:30 ERR Failed to publish events caused by: write tcp 10.143.11.63:34010-\>10.143.63.47:5044: write: connection reset by peer 2018-08-09T11:40:12+05:30 INFO Error publishing events (retrying): write tcp 10.143.11.63:34010-\>10.143.63.47:5044: write: connection reset by peer 2018-08-09T11:40:12+05:30 ERR Failed to publish events caused by: write tcp 10.143.11.63:44212-\>10.143.5.43:5044: write: connection reset by peer 2018-08-09T11:40:12+05:30 INFO Error publishing events (retrying): write tcp 10.143.11.63:44212-\>10.143.5.43:5044: write: connection reset by peer 2018-08-09T11:40:12+05:30 ERR Failed to publish events caused by: write tcp 10.143.11.63:60216-\>10.143.5.44:5044: write: connection reset by peer 2018-08-09T11:40:12+05:30 INFO Error publishing events (retrying): write tcp 10.143.11.63:60216-\>10.143.5.44:5044: write: connection reset by peer 2018-08-09T11:40:12+05:30 ERR Failed to publish events caused by: write tcp 10.143.11.63:35788-\>10.143.63.26:5044: write: connection reset by peer 2018-08-09T11:40:12+05:30 INFO Error publishing events (retrying): write tcp 10.143.11.63:35788-\>10.143.63.26:5044: write: connection reset by peer 2018-08-09T11:40:12+05:30 ERR Failed to publish events caused by: write tcp 10.143.11.63:58490-\>10.143.63.29:5044: write: connection reset by peer 2018-08-09T11:40:12+05:30 INFO Error publishing events (retrying): write tcp 10.143.11.63:58490-\>10.143.63.29:5044: write: connection reset by peer 2018-08-09T11:40:12+05:30 ERR Failed to publish events caused by: write tcp 10.143.11.63:51944-\>10.143.5.41:5044: write: connection reset by peer 2018-08-09T11:40:12+05:30 INFO Error publishing events (retrying): write tcp 10.143.11.63:51944-\>10.143.5.41:5044: write: connection reset by peer 2018-08-09T11:40:12+05:30 ERR Failed to publish events caused by: write tcp 10.143.11.63:51946-\>10.143.5.41:5044: write: connection reset by peer 2018-08-09T11:40:12+05:30 INFO Error publishing events (retrying): write tcp 10.143.11.63:51946-\>10.143.5.41:5044: write: connection reset by peer 2018-08-09T11:40:12+05:30 ERR Failed to publish events caused by: write tcp 10.143.11.63:58496-\>10.143.63.29:5044: write: connection reset by peer 2018-08-09T11:40:12+05:30 INFO Error publishing events (retrying): write tcp 10.143.11.63:58496-\>10.143.63.29:5044: write: connection reset by peer ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [August 9, 2018, 7:40am UTC](https://discuss.elastic.co/t/err-failed-to-publish-events-caused-by-write-tcp/143636/2 "2018-08-09T07:40:13Z")
Perhaps Logstash can't keep up with the event rate? What's in the Logstash log? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 6, 2018, 7:51am UTC](https://discuss.elastic.co/t/err-failed-to-publish-events-caused-by-write-tcp/143636/3 "2018-09-06T07:51:18Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.