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

Large console logs cause infinite loops in slave

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Component/s: pipeline, remoting
    • Labels:
    • Environment:
      We run Jenkins using the official docker image version 2.46.2, docker version 17.03.1-ce, Amazon EC2 plugin 1.36, Ubuntu 14.04, Oracle java version 1.8.0_131 for the slave.jar process
    • Similar Issues:

      Description

      I have just been investigating a problem in our jenkins setup that I think might be related to JENKINS-25218. We're using the EC2 plugin and running builds that generate quite large logs (230 MB). At some point during the build, the master loses track of the log and just starts logging the same block of text from the log over and over as long as I let it. The build completes successfully on the slave and nothing bad appears in the Node log in the jenkins UI. But the master continues to fill up the filesystem with the same repeated text forever. I changed the build to log much less and now this isn't happening. We're running 2.46.2. Could this potentially be one of the edge cases?

        Attachments

          Issue Links

            Activity

            Hide
            gdcrocx George Davis added a comment -

            Hi, Is there an update if this issue was fixed along with the release of JENKINS-38381?. Could you confirm with the release / build number? I am still seeing large log files on our Jenkins master for Pipeline jobs.

            Show
            gdcrocx George Davis added a comment - Hi, Is there an update if this issue was fixed along with the release of JENKINS-38381 ?. Could you confirm with the release / build number? I am still seeing large log files on our Jenkins master for Pipeline jobs.
            Hide
            sudhakar_1066 sudhakar natarajan added a comment -

            I too get this issue. Our pipeline logs will be more than 250 mb. This happens for slaves which we connect to a different domain than master. Same jenkinsfile works on slaves within same domain as master.

            Show
            sudhakar_1066 sudhakar natarajan added a comment - I too get this issue. Our pipeline logs will be more than 250 mb. This happens for slaves which we connect to a different domain than master. Same jenkinsfile works on slaves within same domain as master.
            Hide
            jglick Jesse Glick added a comment -

            Likely a dupe.

            Show
            jglick Jesse Glick added a comment - Likely a dupe.
            Hide
            shahmishal mishal shah added a comment -

            is there any workaround to this issue? 

            Show
            shahmishal mishal shah added a comment - is there any workaround to this issue? 
            Hide
            parlapiano_paolo Paolo Parlapiano added a comment -

            Hi all,

            please help me with another occurrence of this issue: I've just moved a C.I. environment from Jenkins 2.204.2, remoting 3.36.1, and slaves launched manually via JNLP, to a new environment with Jenkins 2.249.1, remoting 4.5, and slaves launched using the EC2 plugin.

            Our jobs run on both Windows and Linux slaves. Since we moved to the new environment, we are almost regularly experiencing the very same issue on Windows slaves: endless jobs that collect several GB of repeated output from the slave. Going to the slave box, the job has completed all the stuff to do.

            Any idea why we are experiencing the same issue using the latest Jenkins LTS and remoting 4.5?

            Thanks

            Regards,

            Paolo

            Show
            parlapiano_paolo Paolo Parlapiano added a comment - Hi all, please help me with another occurrence of this issue: I've just moved a C.I. environment from Jenkins 2.204.2, remoting 3.36.1, and slaves launched manually via JNLP, to a new environment with Jenkins 2.249.1, remoting 4.5, and slaves launched using the EC2 plugin. Our jobs run on both Windows and Linux slaves. Since we moved to the new environment, we are almost regularly experiencing the very same issue on Windows slaves: endless jobs that collect several GB of repeated output from the slave. Going to the slave box, the job has completed all the stuff to do. Any idea why we are experiencing the same issue using the latest Jenkins LTS and remoting 4.5? Thanks Regards, Paolo

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              chris_phillips Chris Phillips
              Votes:
              4 Vote for this issue
              Watchers:
              16 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: