# Could not receive data from client Connection reset by peer(dispatcher service creating idle connections)

**URL:** <https://forum.ansible.com/t/could-not-receive-data-from-client-connection-reset-by-peer-dispatcher-service-creating-idle-connections/37945>\
**Category:** AWX Project\
**Tags:** awx\
**Created:** [May 1, 2023, 3:33pm UTC](https://forum.ansible.com/t/could-not-receive-data-from-client-connection-reset-by-peer-dispatcher-service-creating-idle-connections/37945 "2023-05-01T15:33:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Imran\_Khan](https://avatars.discourse-cdn.com/v4/letter/i/e8c25b/32.png) [@Imran\_Khan](https://forum.ansible.com/u/Imran_Khan)\
**Post date:** [May 1, 2023, 3:33pm UTC](https://forum.ansible.com/t/could-not-receive-data-from-client-connection-reset-by-peer-dispatcher-service-creating-idle-connections/37945/1 "2023-05-01T15:33:50Z")

</div>

Hello Team,

I have posted the same question in an old thread by subject: Setting max\_connections in Postgres deployed through AWX operator 0.13.0 with AWX 19.3.0  
as my issue is the same. I see a lot of idle connections from the dispatcher service and due to this I see frequent alerts for “could not receive data from client: Connection reset by peer”. We are using Postgresql database with awx.

Point to note is that due to this behavior I am seeing a rise in memory usage as every second we get this message in the logs.

My question is:

1. How can I stop this behavior and do not see so many frequent logs for “could not receive data from client: Connection reset by peer”?
2. Is this normal behavior of dispatcher service to create idle sessions every second?

AWX version is : 21.0.0

It(AWX) is a pod running in openshift.

---

<div class="post-metadata">

**Author:** ![Imran\_Khan](https://avatars.discourse-cdn.com/v4/letter/i/e8c25b/32.png) [@Imran\_Khan](https://forum.ansible.com/u/Imran_Khan)\
**Post date:** [May 1, 2023, 3:36pm UTC](https://forum.ansible.com/t/could-not-receive-data-from-client-connection-reset-by-peer-dispatcher-service-creating-idle-connections/37945/2 "2023-05-01T15:36:22Z")

</div>

Attached screenshot for reference.

> **(attachments)**
>
> ![connection reset by peer.jpg](https://us1.discourse-cdn.com/ansible/optimized/2X/5/5b72673a63ecd8aabab685546c9739a6fbdcae32_2_690x39.jpeg)

---

<div class="post-metadata">

**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\
**Post date:** [May 3, 2023, 6:51pm UTC](https://forum.ansible.com/t/could-not-receive-data-from-client-connection-reset-by-peer-dispatcher-service-creating-idle-connections/37945/3 "2023-05-03T18:51:01Z")

</div>

No it is not normal behavior.  
what is your setup? are you using an external postgres? is it running through a proxy server? “connection reset by peer” logs usually indicate a load-balancer type of issue

AWX Team