# AWX 19.4/19.5 Error in asyn task

**URL:** <https://forum.ansible.com/t/awx-19-4-19-5-error-in-asyn-task/36309>\
**Category:** AWX Project\
**Tags:** windows, awx, kubernetes\
**Created:** [February 9, 2022, 7:24am UTC](https://forum.ansible.com/t/awx-19-4-19-5-error-in-asyn-task/36309 "2022-02-09T07:24:02Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lars\_Scholtz](https://avatars.discourse-cdn.com/v4/letter/l/a4c791/32.png) [@Lars\_Scholtz](https://forum.ansible.com/u/Lars_Scholtz)\
**Post date:** [February 9, 2022, 7:24am UTC](https://forum.ansible.com/t/awx-19-4-19-5-error-in-asyn-task/36309/1 "2022-02-09T07:24:02Z")

</div>

Hello,

I have observed a strange behavior in AWX 19.4 and AWX 19.5.1. AWX is running on a Kubernetes Cluster. The following changes after exactly 300 seconds to the status error without any response.

- ansible.windows.win\_wait\_for:

path: C:\temp\logtxt

timeout: 1500

register: win\_wait

async: 25200

poll: 0

- name: Check on an async task

async\_status:

jid: “{{ win\_wait.ansible\_job\_id }}”

register: win\_wait\_result

until: win\_wait\_result.finished

retries: 84

delay: 300

I can see that the executing container disappears after 300 seconds. If I change the delay value to 299 this doesn’t happen, and the task works like expected. The problem is on Linux or Windows Remote hosts identical. Back on AWX 15.0.1 on Docker the tasks works with delay 300 fine.

Regards

Lars

---

<div class="post-metadata">

**Author:** ![Rebeccah\_Hunter](https://avatars.discourse-cdn.com/v4/letter/r/4da419/32.png) [@Rebeccah\_Hunter](https://forum.ansible.com/u/Rebeccah_Hunter)\
**Post date:** [February 9, 2022, 9:48pm UTC](https://forum.ansible.com/t/awx-19-4-19-5-error-in-asyn-task/36309/2 "2022-02-09T21:48:54Z")

</div>

Hey Lars,  
We tried to reproduce this on 19.5.2 and was unable to reproduce. Can you provide us more info? What are you getting from the job output?  
Cheers  
AWX team

---

<div class="post-metadata">

**Author:** ![Wei-Yen\_Tan](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/wei-yen_tan/32/4111_2.png) [@Wei-Yen\_Tan](https://forum.ansible.com/u/Wei-Yen_Tan)\
**Post date:** [February 9, 2022, 9:50pm UTC](https://forum.ansible.com/t/awx-19-4-19-5-error-in-asyn-task/36309/3 "2022-02-09T21:50:52Z")

</div>

I remember reading about this. Iirc This has some thing to do with the k8s logs rotation

---

<div class="post-metadata">

**Author:** ![Lars\_Scholtz](https://avatars.discourse-cdn.com/v4/letter/l/a4c791/32.png) [@Lars\_Scholtz](https://forum.ansible.com/u/Lars_Scholtz)\
**Post date:** [February 11, 2022, 1:45pm UTC](https://forum.ansible.com/t/awx-19-4-19-5-error-in-asyn-task/36309/4 "2022-02-11T13:45:31Z")

</div>

Hello,  
the output from the job is really short, its just “Error” on 19.4 and “Job terminated due to error\*\*”\*\* 19.05 .

I have tried it with two different setups of AWX and the mentioned versions. Both show the identical behavior.

Which information you do else need?

Regards  
Lars

---

<div class="post-metadata">

**Author:** ![ffirg](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ffirg/32/10029_2.png) [@ffirg](https://forum.ansible.com/u/ffirg)\
**Post date:** [February 14, 2022, 11:26am UTC](https://forum.ansible.com/t/awx-19-4-19-5-error-in-asyn-task/36309/5 "2022-02-14T11:26:28Z")

</div>

You could be hitting a log rotation issue here, but I suggest you try this workaround as well: [https://github.com/ansible/awx/issues/11521](https://github.com/ansible/awx/issues/11521)

Try setting:  
vars:  
ansible\_async\_dir: ‘/tmp/.ansible\_async’

---

<div class="post-metadata">

**Author:** ![Lars\_Scholtz](https://avatars.discourse-cdn.com/v4/letter/l/a4c791/32.png) [@Lars\_Scholtz](https://forum.ansible.com/u/Lars_Scholtz)\
**Post date:** [February 22, 2022, 10:45am UTC](https://forum.ansible.com/t/awx-19-4-19-5-error-in-asyn-task/36309/6 "2022-02-22T10:45:19Z")

</div>

Hello Phil,

the workaround does not work ☹ . Problem still exists. We can see that after 300 seconds from somewhere the status cancel.

---

<div class="post-metadata">

**Author:** ![Lars\_Scholtz](https://avatars.discourse-cdn.com/v4/letter/l/a4c791/32.png) [@Lars\_Scholtz](https://forum.ansible.com/u/Lars_Scholtz)\
**Post date:** [February 22, 2022, 10:46am UTC](https://forum.ansible.com/t/awx-19-4-19-5-error-in-asyn-task/36309/7 "2022-02-22T10:46:52Z")

</div>

We have found a way to increase the log size. It fix’s some issues but this one still exists.