Warning thrown in server logs when a user visits job console of jobs either not assigned or not started writing to console #6325
The following warning message is thrown if a user visits the job console of a job which is either not assigned or is assigned but hasn't started writing to the console.
Basic environment details
I took a quick look, this is what I found. Once a job is assigned to an agent, the agent starts posting the console logs to the server. While the job is in progress the server keeps writing the logs to a temporary file and upon completion of the job the temporary file contents are are copied over to a permanent console.log file and is stored as an artifact.
For a job which is yet to be assigned the temporary file is not yet created, the above error occurs when trying to read from a non-existent console log.
Yes, as I mentioned earlier the server writes the logs to a temporary file till the job is completed. A request to the raw console logs tries to find the logs in the permanent file which does not exist.
Since we are close to a release I am moving this to 19.5.0
I'd expect that it shows the same log that's being shown in the scrolling logs when that is clicked. Even though it's being updated. We will need to check that it's building and do that, right?
referenced this issue
May 28, 2019
This issue is caused by a combination of a few things -
The ConsoleOutView catches a
More recently, we wrote AccessTokenAuthenticationFilter which has a try-catch block that catches all exceptions. The
For the fix, I have handled the
@arvindsv For the raw console logs, we point to the final console.log file, not the temporary file. As a result, we can't see the raw logs until the build is finished. Not sure if this is existing behaviour or if it was changed accidentally. Nonetheless, it seems unrelated to this issue. We can fix it separately.