# Closing (Connection reset by peer) keeps being logged on logstash logs **URL:** \ **Category:** Logstash\ **Created:** [August 12, 2022, 8:52am UTC](https://discuss.elastic.co/t/closing-connection-reset-by-peer-keeps-being-logged-on-logstash-logs/311992 "2022-08-12T08:52:31Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Thuunder7](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thuunder7/32/97482_2.png) [@Thuunder7](https://discuss.elastic.co/u/Thuunder7)\ **Post date:** [August 12, 2022, 8:52am UTC](https://discuss.elastic.co/t/closing-connection-reset-by-peer-keeps-being-logged-on-logstash-logs/311992/1 "2022-08-12T08:52:31Z")
Hello, Since i upgraded my two logstash instances from 7.16.3 to 8.3.1 i am seeing the appearence of the above logs: ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1abf64e017d8f64bc6fe8b3e83b2818338dbe22c.png) Does someone know why this could be happening? I didnt had these INFO logs before on the previous version. Thank you, ---
**Author:** ![cheshirecat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cheshirecat/32/109532_2.png) [@cheshirecat](https://discuss.elastic.co/u/cheshirecat)\ **Post date:** [August 12, 2022, 1:14pm UTC](https://discuss.elastic.co/t/closing-connection-reset-by-peer-keeps-being-logged-on-logstash-logs/311992/2 "2022-08-12T13:14:56Z")
Hello @Thuunder7 please tell me why there is a picture instead of code tag... Could you please post your logstash config file (using code tags - otherwise I will not analyze it). ---
**Author:** ![Thuunder7](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thuunder7/32/97482_2.png) [@Thuunder7](https://discuss.elastic.co/u/Thuunder7)\ **Post date:** [August 12, 2022, 1:25pm UTC](https://discuss.elastic.co/t/closing-connection-reset-by-peer-keeps-being-logged-on-logstash-logs/311992/3 "2022-08-12T13:25:11Z")
@cheshirecat Sorry, of course i can do that. I just posted the picture because it is always the same log. Below is my logstash config file: ```auto node: name: loganprdap01l path: data: /usr/share/logstash/path_data logs: /usr/share/logstash/logs pipeline.ecs_compatibility: disabled monitoring: enabled: false cluster_uuid: kRR0E9ojS8q7DqJJBaYVow ``` ---
**Author:** ![cheshirecat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cheshirecat/32/109532_2.png) [@cheshirecat](https://discuss.elastic.co/u/cheshirecat)\ **Post date:** [August 17, 2022, 7:19am UTC](https://discuss.elastic.co/t/closing-connection-reset-by-peer-keeps-being-logged-on-logstash-logs/311992/4 "2022-08-17T07:19:25Z")
@Thuunder7 why is there a local address 0.0.0.0? ---
**Author:** ![Thuunder7](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thuunder7/32/97482_2.png) [@Thuunder7](https://discuss.elastic.co/u/Thuunder7)\ **Post date:** [August 18, 2022, 2:30pm UTC](https://discuss.elastic.co/t/closing-connection-reset-by-peer-keeps-being-logged-on-logstash-logs/311992/5 "2022-08-18T14:30:24Z")
Because i didn't specify the host parameter on the pipeline. Is letting logstash listen to all interfaces an issue? ---
**Author:** ![cheshirecat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cheshirecat/32/109532_2.png) [@cheshirecat](https://discuss.elastic.co/u/cheshirecat)\ **Post date:** [August 19, 2022, 7:21am UTC](https://discuss.elastic.co/t/closing-connection-reset-by-peer-keeps-being-logged-on-logstash-logs/311992/6 "2022-08-19T07:21:08Z")
For sure it's security issue but still it should work fine. ---
**Author:** ![Thuunder7](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thuunder7/32/97482_2.png) [@Thuunder7](https://discuss.elastic.co/u/Thuunder7)\ **Post date:** [August 22, 2022, 11:13am UTC](https://discuss.elastic.co/t/closing-connection-reset-by-peer-keeps-being-logged-on-logstash-logs/311992/7 "2022-08-22T11:13:06Z")
I am still not really sure what is causing this behavior... Sometimes it stops, sometimes it starts again. What do you think it can be? At first i thought that it could be a port scanner, but when i resolve the IP i get a host that i clearly know that it is not a port scanner... ---
**Author:** ![cheshirecat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cheshirecat/32/109532_2.png) [@cheshirecat](https://discuss.elastic.co/u/cheshirecat)\ **Post date:** [August 23, 2022, 7:19am UTC](https://discuss.elastic.co/t/closing-connection-reset-by-peer-keeps-being-logged-on-logstash-logs/311992/8 "2022-08-23T07:19:02Z")
Hello, Is this stopping/restarting regular? ---
**Author:** ![Thuunder7](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thuunder7/32/97482_2.png) [@Thuunder7](https://discuss.elastic.co/u/Thuunder7)\ **Post date:** [August 29, 2022, 9:09am UTC](https://discuss.elastic.co/t/closing-connection-reset-by-peer-keeps-being-logged-on-logstash-logs/311992/9 "2022-08-29T09:09:20Z")
Hi @cheshirecat , Yes, from 20 to 20 min i see a new log like the described , probably there is something wrong with the machine that is connecting to logstash. I don't see any other machines now, with that behavior. ---
**Author:** ![cheshirecat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cheshirecat/32/109532_2.png) [@cheshirecat](https://discuss.elastic.co/u/cheshirecat)\ **Post date:** [August 29, 2022, 9:23am UTC](https://discuss.elastic.co/t/closing-connection-reset-by-peer-keeps-being-logged-on-logstash-logs/311992/10 "2022-08-29T09:23:37Z")
Beat versions, SSL/TLS, and other things are same on machines? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 26, 2022, 9:24am UTC](https://discuss.elastic.co/t/closing-connection-reset-by-peer-keeps-being-logged-on-logstash-logs/311992/11 "2022-09-26T09:24:08Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.