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.
Side note: If I try to download the contents of stdout via the button, I simply get the following json string in my browser:
`
{"detail":"Not found."}
`
Anyone else seeing something similar?
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.
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/
Are the events emitted out of order or is it just missing a huge swath of output?
It appears to just be missing big chunks of output.
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.
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.
That did the trick, thanks Chris!