-
Bug
-
Resolution: Unresolved
-
Blocker
-
Jenkins ver. 1.553, Chrome browser
Jenkins ver. 2.150.1 from "Official" Docker Image running on Ubuntu 16.04 with jenkins_home mounted from the local file system on a RAID 0 setup.
I have a bug which looks similar to JENKINS-14899:
Sometimes, when a job runs for a long time without anything getting output, the jenkins page stops updating until the job finishes. Then it add the completion lines (SUCCESS or FAILURE) to the job.
The difference is that the number of line does not matter (last bug occurence was on a job that output 264 lines (+ an unknown number of non-output lines)
This results in a truncated /console, /consoleFull and /consoleText.
All files do end with the two lines (if it succeeds):
Notifying upstream projects of job completion
Finished: SUCCESS
but hundreds of lines didn't get stored by jenkins (over 10 minutes of logs for my last job!)
I can often see this bug when I'm running a long impala query, where the output stops before the status line (something like "Returned 0 row(s) in 1987.42s") and the rest of the console logs never get output.
This happens approximately one time out of 20 for the jobs I'm running myself on this Jenkins server.
[JENKINS-29198] Console logs get truncated without reason
Namikaze Minato
created issue -
Please make sure any issues you experience happen on a reasonably recent version of Jenkins. Since it's been more than a year since 1.553 was released, this issue may well be obsolete.
| Workflow | Original: JNJira [ 164066 ] | New: JNJira + In-Review [ 181494 ] |
Namikaze Minato
added a comment - It does not happen with a recent version.
Please close the issue. I am seeing this exact problem today on version 2.121.3
The console output displays to the end, showing Finished: SUCCESS. The consoleText output is truncated (at 4604 lines in the case I'm looking at this moment). The consoleFull output is truncated at exactly the same line as consoleText.
Ben Eng
added a comment - - edited I am seeing this exact problem today on version 2.121.3
The console output displays to the end, showing Finished: SUCCESS. The consoleText output is truncated (at 4604 lines in the case I'm looking at this moment). The consoleFull output is truncated at exactly the same line as consoleText. As of today am also seeing this on version 2.154 I don't see any success or failure messages. I also noticed that loading output for nodes in the blue ocean view seems to give a red console error. (I'm guessing these are somehow loaded from the log which doesn't have the info since it's truncated.)
I am seeing this issue as well on Jenkins 2.150.1 that comes from the "official" Docker image provided from DockerHub. I'm trying to debug an issue with a high level of parallelism and the full logs are truncated. There are logs showing in the BlueOcean view for the individual nodes, but some of those appear truncated as well, but that is difficult to confirm since the full console, consoleText, and consoleFull are truncated.
Additionally, I even got the infamous "Jenkins Devil" bug image directly in the console output a couple of times when trying to watch the logs live as they were output.
Please help provide some insight into what could cause this behavior if it could be a bug in the Pipeline code that can be worked around. Even if a there is a bug in our Pipeline code causing this issue, Jenkins should still show the full console output.
H L
added a comment - - edited I am seeing this issue as well on Jenkins 2.150.1 that comes from the "official" Docker image provided from DockerHub. I'm trying to debug an issue with a high level of parallelism and the full logs are truncated. There are logs showing in the BlueOcean view for the individual nodes, but some of those appear truncated as well, but that is difficult to confirm since the full console, consoleText, and consoleFull are truncated.
Additionally, I even got the infamous "Jenkins Devil" bug image directly in the console output a couple of times when trying to watch the logs live as they were output.
Please help provide some insight into what could cause this behavior if it could be a bug in the Pipeline code that can be worked around. Even if a there is a bug in our Pipeline code causing this issue, Jenkins should still show the full console output. H L
added a comment - Please increase the priority of this issue since this is impossible for a developer to troubleshoot without console output to indicate what the issue is.
Issues causing outages in the console output seems as though they should be treated with the highest priority rather than Minor since there is currently no workaround.
H L
added a comment - Please increase the priority of this issue since this is impossible for a developer to troubleshoot without console output to indicate what the issue is.
Issues causing outages in the console output seems as though they should be treated with the highest priority rather than Minor since there is currently no workaround. H L
added a comment - jetpen rjfenton Please don't forget to vote for this issue if you are getting impacted. I seem to be the only one that has voted for it so far.
H L
added a comment - jetpen rjfenton Please don't forget to vote for this issue if you are getting impacted. I seem to be the only one that has voted for it so far.
Wow, I am just facing this issue at the very moment, in the middle of a map/reduce job. (I can see in the jobtracker this map/reduce job finished a long time ago and my (still running) jenkins job started the next map/reduce)
I opened the console and all progressiveHtml calls were empty. http://prntscr.com/7o0vg9
Things I tried:
Refreshing - same state
Opening another tab/window - same state
Looking at /consoleText - same state
Manually opening /consoleFull - same state
Logging out and logging in in an incognito window - same state
(So "runing for a long time without anything getting output" has nothing to do with this bug)
Number of lines before stopping this time: 3201