# receptor: Could not close connection

**URL:** <https://forum.ansible.com/t/receptor-could-not-close-connection/37936>\
**Category:** AWX Project\
**Tags:** awx\
**Created:** [April 26, 2023, 4:25pm UTC](https://forum.ansible.com/t/receptor-could-not-close-connection/37936 "2023-04-26T16:25:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stefan\_Jakobs](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@Stefan\_Jakobs](https://forum.ansible.com/u/Stefan_Jakobs)\
**Post date:** [April 26, 2023, 4:25pm UTC](https://forum.ansible.com/t/receptor-could-not-close-connection/37936/1 "2023-04-26T16:25:55Z")

</div>

Hi list,

receptor logs see the following messages on my AWX hybrid node (not on the exec nodes):

WARNING 2023/04/26 16:15:58 Could not read in control service: read unix /var/run/awx-receptor/receptor.sock-\>@: use of closed network  
connection  
WARNING 2023/04/26 16:15:58 Could not close connection: close unix /var/run/awx-receptor/receptor.sock-\>@: use of closed network conne  
ction  
WARNING 2023/04/26 16:15:58 Could not copy to stdout file /tmp/receptor/awx/Axr4aHpF/stdout: read operation cancelled  
ERROR 2023/04/26 16:16:02 Exceeded retries for reading stdout /tmp/receptor/awx/Rp7f6jsd/stdout

Everything seems to work. Does anyone know what this means or how I can debug this further?  
The receptor.conf can be found [here](https://pastebin.com/7BqnMmaS).

Thanks  
Stefan

---

<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:** [April 28, 2023, 4:10pm UTC](https://forum.ansible.com/t/receptor-could-not-close-connection/37936/2 "2023-04-28T16:10:52Z")

</div>

those warnings messages are usually benign and can probably be ignored (we see them in logs all of the time)

The error message could be an issue, but might be expected if the job was cancelled in awx or similar.

are you having any behavioral issues at the AWX level? i.e. jobs not running, failing, etc.?

AWX Team

---

<div class="post-metadata">

**Author:** ![Stefan\_Jakobs](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@Stefan\_Jakobs](https://forum.ansible.com/u/Stefan_Jakobs)\
**Post date:** [May 3, 2023, 1:15pm UTC](https://forum.ansible.com/t/receptor-could-not-close-connection/37936/3 "2023-05-03T13:15:23Z")

</div>

No, issues at AWX level.

Can I somehow map the receptor id (e.g. “Axr4aHpF”) to a job id?

---

<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 5, 2023, 5:38pm UTC](https://forum.ansible.com/t/receptor-could-not-close-connection/37936/4 "2023-05-05T17:38:40Z")

</div>

you can find the receptor work id in the AWX API, e.g. api/v2/jobs/ look for field “work\_unit\_id”

AWX Team