# Truncated stdout in AWX display **URL:** \ **Category:** AWX Project\ **Tags:** awx\ **Created:** [November 7, 2017, 10:45pm UTC](https://forum.ansible.com/t/truncated-stdout-in-awx-display/25954 "2017-11-07T22:45:09Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Cody\_John](https://avatars.discourse-cdn.com/v4/letter/c/8e7dd6/32.png) [@Cody\_John](https://forum.ansible.com/u/Cody_John)\ **Post date:** [November 7, 2017, 10:45pm UTC](https://forum.ansible.com/t/truncated-stdout-in-awx-display/25954/1 "2017-11-07T22:45:09Z")
I have noticed that on playbook runs with very long stdout, AWX seems to truncate it and arbitrarily insert a series of periods and then skips lines. I can’t find a way to get it to display the entire contents. [![](https://lh3.googleusercontent.com/-UxTdwxCFiMk/WgI3MyrCmEI/AAAAAAAAGrQ/DR_Bd7lG4_A1u7SI2SDF6naF0atN0K2GACLcBGAs/s1600/Screen%2BShot%2B2017-11-07%2Bat%2B2.38.07%2BPM.png)](https://lh3.googleusercontent.com/-UxTdwxCFiMk/WgI3MyrCmEI/AAAAAAAAGrQ/DR_Bd7lG4_A1u7SI2SDF6naF0atN0K2GACLcBGAs/s1600/Screen%2BShot%2B2017-11-07%2Bat%2B2.38.07%2BPM.png) Side note: If I try to download the contents of stdout via the button, I simply get the following json string in my browser: ` ```auto {"detail":"Not found."} ``` ` Anyone else seeing something similar? ---
**Author:** ![Robert\_Arko](https://avatars.discourse-cdn.com/v4/letter/r/65b543/32.png) [@Robert\_Arko](https://forum.ansible.com/u/Robert_Arko)\ **Post date:** [November 7, 2017, 11:52pm UTC](https://forum.ansible.com/t/truncated-stdout-in-awx-display/25954/2 "2017-11-07T23:52:32Z")
Yeah I get something similar (I think). When I first start up AWX, and run a Job, it reports Status=Successful and shows the correct # of Plays, Tasks, and Hosts with the log of stdout . After that, on all subsequent runs, it still reports Status=Successful but shows 0 Plays/Tasks/Hosts and an empty stdout window. The only way to recover is to restart AWX. Bob PS. I’m running the Docker version, with a remote SQL database. ---
**Author:** ![Christopher\_Meyers](https://avatars.discourse-cdn.com/v4/letter/c/3e96dc/32.png) [@Christopher\_Meyers](https://forum.ansible.com/u/Christopher_Meyers)\ **Post date:** [November 8, 2017, 12:27pm UTC](https://forum.ansible.com/t/truncated-stdout-in-awx-display/25954/3 "2017-11-08T12:27:29Z")
Tower had a configurable for the max data size of a job event allowed via MAX\_EVENT\_RES\_DATA . You can override the default by laying down a .py file in /etc/tower/conf.d/ ---
**Author:** ![matburt](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/matburt/32/3612_2.png) [@matburt](https://forum.ansible.com/u/matburt)\ **Post date:** [November 9, 2017, 8:58pm UTC](https://forum.ansible.com/t/truncated-stdout-in-awx-display/25954/4 "2017-11-09T20:58:44Z")
Are the events emitted out of order or is it just missing a huge swath of output? ---
**Author:** ![Cody\_John](https://avatars.discourse-cdn.com/v4/letter/c/8e7dd6/32.png) [@Cody\_John](https://forum.ansible.com/u/Cody_John)\ **Post date:** [November 16, 2017, 3:56pm UTC](https://forum.ansible.com/t/truncated-stdout-in-awx-display/25954/5 "2017-11-16T15:56:53Z")
It appears to just be missing big chunks of output. ---
**Author:** ![Cody\_John](https://avatars.discourse-cdn.com/v4/letter/c/8e7dd6/32.png) [@Cody\_John](https://forum.ansible.com/u/Cody_John)\ **Post date:** [February 20, 2018, 8:59pm UTC](https://forum.ansible.com/t/truncated-stdout-in-awx-display/25954/6 "2018-02-20T20:59:21Z")
This still happens on pretty much all of my jobs. Here is a screenshot, notice the trailing ellipsis at the end of line 227, and then a jump straight to line 330. This is being run with the ‘–check’ flag so we can evaluate the changes before pushing them, and it’s basically useless if that output is cut off. [![](https://lh3.googleusercontent.com/--wBT9fFtoVA/WoyMA7JC-MI/AAAAAAAAGv4/YF6tHl4SESQjkGT5rrmWujvh78d-JMwkwCLcBGAs/s320/Screen%2BShot%2B2018-02-20%2Bat%2B1.48.33%2BPM.png)](https://lh3.googleusercontent.com/--wBT9fFtoVA/WoyMA7JC-MI/AAAAAAAAGv4/YF6tHl4SESQjkGT5rrmWujvh78d-JMwkwCLcBGAs/s1600/Screen%2BShot%2B2018-02-20%2Bat%2B1.48.33%2BPM.png) ---
**Author:** ![Chris\_Church](https://avatars.discourse-cdn.com/v4/letter/c/f475e1/32.png) [@Chris\_Church](https://forum.ansible.com/u/Chris_Church)\ **Post date:** [February 20, 2018, 9:18pm UTC](https://forum.ansible.com/t/truncated-stdout-in-awx-display/25954/7 "2018-02-20T21:18:26Z")
While not editable in the UI, you can update EVENT\_STDOUT\_MAX\_BYTES\_DISPLAY via /api/v2/settings/jobs/ to see if that allows you to see more of the output. Also check /api/v2/jobs/N/events/ to see if certain job events span more than one line (i.e. (end\_line - start\_line) \> 1). If a single event’s stdout spans multiple lines and is longer than the configured max bytes to display, that would explain why you are seeing large gaps in the line numbers. ---
**Author:** ![Cody\_John](https://avatars.discourse-cdn.com/v4/letter/c/8e7dd6/32.png) [@Cody\_John](https://forum.ansible.com/u/Cody_John)\ **Post date:** [February 20, 2018, 9:42pm UTC](https://forum.ansible.com/t/truncated-stdout-in-awx-display/25954/8 "2018-02-20T21:42:54Z")
That did the trick, thanks Chris!