[JIRA] [core] (JENKINS-29198) Console logs get truncated without reason

6 views
Skip to first unread message

lloydsensei+jenkins@gmail.com (JIRA)

unread,
Jul 2, 2015, 1:15:05 PM7/2/15
to jenkinsc...@googlegroups.com
Namikaze Minato created an issue
 
Jenkins / Bug JENKINS-29198
Console logs get truncated without reason
Issue Type: Bug Bug
Assignee: Unassigned
Components: core
Created: 02/Jul/15 5:14 PM
Environment: Jenkins ver. 1.553, Chrome browser
Labels: jenkins user-experience
Priority: Minor Minor
Reporter: Namikaze Minato

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.
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

lloydsensei+jenkins@gmail.com (JIRA)

unread,
Jul 2, 2015, 1:53:01 PM7/2/15
to jenkinsc...@googlegroups.com
Namikaze Minato commented on Bug JENKINS-29198
 
Re: Console logs get truncated without reason

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 job finished a long time ago and jenkins started the next one)
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

lloydsensei+jenkins@gmail.com (JIRA)

unread,
Jul 2, 2015, 1:54:01 PM7/2/15
to jenkinsc...@googlegroups.com
Namikaze Minato edited a comment on Bug JENKINS-29198
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  one  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

dbeck@cloudbees.com (JIRA)

unread,
Jul 2, 2015, 5:48:01 PM7/2/15
to jenkinsc...@googlegroups.com

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.

lloydsensei+jenkins@gmail.com (JIRA)

unread,
Oct 19, 2018, 5:35:01 AM10/19/18
to jenkinsc...@googlegroups.com

It does not happen with a recent version.
Please close the issue.
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

ben.eng.1@gmail.com (JIRA)

unread,
Feb 6, 2019, 3:05:02 PM2/6/19
to jenkinsc...@googlegroups.com
Ben Eng commented on Bug JENKINS-29198

I am seeing this exact problem today on version 2.121.3

ben.eng.1@gmail.com (JIRA)

unread,
Feb 6, 2019, 3:08:01 PM2/6/19
to jenkinsc...@googlegroups.com
Ben Eng edited a comment on Bug JENKINS-29198
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).

ben.eng.1@gmail.com (JIRA)

unread,
Feb 6, 2019, 3:09:01 PM2/6/19
to jenkinsc...@googlegroups.com
Ben Eng edited a comment on Bug JENKINS-29198
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.

killspire@gmail.com (JIRA)

unread,
Feb 6, 2019, 4:04:02 PM2/6/19
to jenkinsc...@googlegroups.com

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.)

z.wood23@gmail.com (JIRA)

unread,
Feb 22, 2019, 2:22:02 PM2/22/19
to jenkinsc...@googlegroups.com
H L commented on Bug JENKINS-29198

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.

z.wood23@gmail.com (JIRA)

unread,
Feb 22, 2019, 2:24:03 PM2/22/19
to jenkinsc...@googlegroups.com
H L edited a comment on Bug JENKINS-29198
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.

z.wood23@gmail.com (JIRA)

unread,
Feb 22, 2019, 2:26:01 PM2/22/19
to jenkinsc...@googlegroups.com
H L commented on Bug JENKINS-29198

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.

z.wood23@gmail.com (JIRA)

unread,
Feb 22, 2019, 2:27:02 PM2/22/19
to jenkinsc...@googlegroups.com
H L commented on Bug JENKINS-29198

Ben Eng Ryan Fenton-Garcia 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.

z.wood23@gmail.com (JIRA)

unread,
Feb 22, 2019, 2:28:02 PM2/22/19
to jenkinsc...@googlegroups.com
H L updated an issue
 
Change By: H L
Environment:
Jenkins ver. 1.553, Chrome browser

Jenkins ver. 2.150.1 from "Official" Docker Image

z.wood23@gmail.com (JIRA)

unread,
Feb 22, 2019, 2:29:03 PM2/22/19
to jenkinsc...@googlegroups.com
H L updated an issue
Change By: H L
Environment:
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 filing system on a RAID 0 setup.

z.wood23@gmail.com (JIRA)

unread,
Feb 22, 2019, 2:29:04 PM2/22/19
to jenkinsc...@googlegroups.com
H L updated an issue
Change By: H L
Environment:
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 filing file system on a RAID 0 setup.

z.wood23@gmail.com (JIRA)

unread,
Feb 22, 2019, 2:29:05 PM2/22/19
to jenkinsc...@googlegroups.com
H L updated an issue
Change By: H L
Labels: blocked bug consoleoutput jenkins user-experience

z.wood23@gmail.com (JIRA)

unread,
Feb 22, 2019, 2:30:03 PM2/22/19
to jenkinsc...@googlegroups.com
H L updated an issue
Change By: H L
Labels: 2.150 blocked bug consoleoutput jenkins user-experience

z.wood23@gmail.com (JIRA)

unread,
Feb 22, 2019, 2:30:03 PM2/22/19
to jenkinsc...@googlegroups.com
H L updated an issue
Change By: H L
Priority: Minor Blocker

rizz78@gmail.com (JIRA)

unread,
Mar 18, 2019, 9:05:06 AM3/18/19
to jenkinsc...@googlegroups.com

irc@webratz.de (JIRA)

unread,
Apr 2, 2019, 2:17:03 AM4/2/19
to jenkinsc...@googlegroups.com

We are seeing this issue aswell. Its seems like this happens mostly with pipelines that have multiple parallel steps.

Running on 2.150.3

irc@webratz.de (JIRA)

unread,
Apr 2, 2019, 2:20:03 AM4/2/19
to jenkinsc...@googlegroups.com
We are seeing this issue aswell. Its seems like this happens mostly with pipelines that have multiple parallel steps.

Running on 2.150.3


We are using also the Timestamper plugin, just curious if anybody else facing the issue is using it aswell and if it might be related.

gabi@inosphere.com (JIRA)

unread,
Apr 2, 2019, 4:23:02 AM4/2/19
to jenkinsc...@googlegroups.com

Indeed. For us, this happens when we run like 6 builds in parallel. However, if we break them in two, having only 3 builds run at a time, same setup, just two sequence of 3 builds, we get full logs.

nelson.work@gmail.com (JIRA)

unread,
Oct 23, 2019, 10:50:04 AM10/23/19
to jenkinsc...@googlegroups.com

Recently seen this a couple times on Jenkins 2.193.

 

In our case, it's a multijob that ends like this:

...
Finished Build : #18084 of Job : fvt-worker-5 with status : SUCCESS
Finished Build : #18084 of Job : fvt-worker-20 with status : SUCCESS
Finished Build : #18085 of Job : fvt-worker-7 with status : SUCCESS
Finished Build : #18085 of Job : fvt-worker-23 with status : SUCCESS
Finished Build : #18084 of Job : fvt-worker-8 with status : SUCCESS
Finished Build : Finished Build :

 

It's clear the job finished successfully (including another dozen subjobs that should be listed but aren't), and that it also completed all the publisher steps as expected, but there's about 120 lines of log at the end there that are missing (affects /console, /consoleFull, and /consoleText).

 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

ashok.mohanty@oracle.com (JIRA)

unread,
Nov 28, 2019, 4:55:08 AM11/28/19
to jenkinsc...@googlegroups.com

In our case - "Console logs get truncated when job runs for a long time". Are there any log size limit !?

ashok.mohanty@oracle.com (JIRA)

unread,
Mar 3, 2020, 10:26:03 AM3/3/20
to jenkinsc...@googlegroups.com

We are using core 2.164.3 version. Ay idea, by upgrading to any specific version - will it help !! 

And/or any workaround we can try !!
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages