Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-29198

Console logs get truncated without reason

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Blocker
    • Resolution: Unresolved
    • Component/s: core
    • 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 file system on a RAID 0 setup.
    • Similar Issues:

      Description

      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.

        Attachments

          Activity

          Hide
          camusensei Namikaze Minato added a comment -

          Few Jenkins versions have this bug, just upgrade.

          Show
          camusensei Namikaze Minato added a comment - Few Jenkins versions have this bug, just upgrade.
          Hide
          alok15ee Alok Singh added a comment - - edited

          Namikaze Minato What version do you recommend? I have tried with 2.204.1 and 2.222.3 and I still run into the same issue.

          Show
          alok15ee Alok Singh added a comment - - edited Namikaze Minato What version do you recommend? I have tried with 2.204.1 and 2.222.3 and I still run into the same issue.
          Hide
          camusensei Namikaze Minato added a comment - - edited

          I have no problem on my jenkins servers:

          2.249.1
          2.138
          2.27
          2.26
          2.204.5
          2.235.5
          2.138.1

          You could try to test if the problem is reproducible, like a loop printing messages, e.g.:

          #!/bin/bash
          while sleep 1; do printf '%*s\n' 300 "$SECONDS"; done
          

          Try it and see if your problem always happens after the same time, or if such a simple script does not allow you to reproduce the problem?

           

          Show
          camusensei Namikaze Minato added a comment - - edited I have no problem on my jenkins servers: 2.249.1 2.138 2.27 2.26 2.204.5 2.235.5 2.138.1 You could try to test if the problem is reproducible, like a loop printing messages, e.g.: #!/bin/bash while sleep 1; do printf '%*s\n' 300 "$SECONDS"; done Try it and see if your problem always happens after the same time, or if such a simple script does not allow you to reproduce the problem?  
          Hide
          alok15ee Alok Singh added a comment -

          Namikaze Minato Nope it didn't work either. I think it also depends on the amount of data in one line we write to the BufferedInputStream which is causing this issue to pop up.

          Show
          alok15ee Alok Singh added a comment - Namikaze Minato Nope it didn't work either. I think it also depends on the amount of data in one line we write to the BufferedInputStream which is causing this issue to pop up.
          Hide
          camusensei Namikaze Minato added a comment -

          I think you need to give more information on your problem which seems to be different from the one I used to have. Maybe open a new issue, and describe preciseley anything you can.

          Show
          camusensei Namikaze Minato added a comment - I think you need to give more information on your problem which seems to be different from the one I used to have. Maybe open a new issue, and describe preciseley anything you can.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            camusensei Namikaze Minato
            Votes:
            16 Vote for this issue
            Watchers:
            18 Start watching this issue

              Dates

              Created:
              Updated: