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

Archives AWX Project
1

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.

2

Attached screenshot for reference.

(attachments)

connection reset by peer.jpg

3

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