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

Disk space leak with multiple copies of winstone-XXXX.jar in TEMP folder

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: core
    • Labels:
    • Environment:
      Windows 8.1 x64, JDK 1.7.0_51, Jenkins 1.553
    • Similar Issues:

      Description

      Continued operation of Jenkins creates multiple copies of "winstone.jar" with a numeric suffix in TEMP folder (winstone12343543634634.jar). We had about 800Gb of these accumulated, slowing down the host system.

      We are currently running Jenkins directly (`java -jar jenkins.jar`) via Windows scheduled task.

        Attachments

          Activity

          Hide
          ptha Peter Hannon added a comment -

          Ivan Fernandez Calvo thanks again!

          As per your suggestion, I updated my start shell script to:

           

          #!/bin/bash
          nohup /home/jenkins/jdk8/bin/java -jar /home/jenkins/jenkins.war --httpPort=8081 --extractedFilesFolder=/tmp > /home/jenkins/jenkins.log 2>&1 &
          

          Now the extra winstone jars are cleaned up on startup, I also tested a safeRestart and again there was only 1 winstone jar file (for the running Jenkins).

          So it's solved for me, cheers!

           

          Show
          ptha Peter Hannon added a comment - Ivan Fernandez Calvo  thanks again! As per your suggestion, I updated my start shell script to:   #!/bin/bash nohup /home/jenkins/jdk8/bin/java -jar /home/jenkins/jenkins.war --httpPort=8081 --extractedFilesFolder=/tmp > /home/jenkins/jenkins.log 2>&1 & Now the extra winstone jars are cleaned up on startup, I also tested a safeRestart and again there was only 1 winstone jar file (for the running Jenkins). So it's solved for me, cheers!  
          Hide
          shashankkulsh Shashank Kulshrestha added a comment -

          This issue is happening with my current Jenkins build 2.156 on windows. Is there any solution for windows for this. 

          Disk is getting full, due to so many winstone*.jar in C:\...\AppData\Local\Temp folder

          Show
          shashankkulsh Shashank Kulshrestha added a comment - This issue is happening with my current Jenkins build 2.156 on windows. Is there any solution for windows for this.  Disk is getting full, due to so many winstone*.jar in C:\...\AppData\Local\Temp folder
          Hide
          ifernandezcalvo Ivan Fernandez Calvo added a comment -

          Shashank Kulshrestha Did you read the comment before yours? there you have the solution *--extractedFilesFolder=c:\TMP-FOLDER-PATH*

          Show
          ifernandezcalvo Ivan Fernandez Calvo added a comment - Shashank Kulshrestha Did you read the comment before yours? there you have the solution * --extractedFilesFolder=c:\TMP-FOLDER-PATH *
          Hide
          barna10 Matt Barna added a comment -

          Is there any plan to fix this? Seems wonky that Jenkins knows where to write the jar, but not where to go to delete it.

          Show
          barna10 Matt Barna added a comment - Is there any plan to fix this? Seems wonky that Jenkins knows where to write the jar, but not where to go to delete it.
          Hide
          smd Stefan Drissen added a comment -

          I just had my Windows 2012R2 Jenkins 2.257 server fall to its knees for the second time in a week after something threw a spanner at Jenkins (started as a service). Jenkins was convinced that it needed to restart itself, which failed due to address already in use, so try again and again and again, dumping a new copy of winstone#.jar each time until out of disk space.

          This bizarre behavior seems to be the result of how the Jenkins service is created by default, first failure: restart, second failure: restart, subsequent failures: restart.

          For now I've set subsequent failures to 'take no action' - hopefully this will ease the pain.

          Show
          smd Stefan Drissen added a comment - I just had my Windows 2012R2 Jenkins 2.257 server fall to its knees for the second time in a week after something threw a spanner at Jenkins (started as a service). Jenkins was convinced that it needed to restart itself, which failed due to address already in use, so try again and again and again, dumping a new copy of winstone#.jar each time until out of disk space. This bizarre behavior seems to be the result of how the Jenkins service is created by default, first failure: restart, second failure: restart, subsequent failures: restart. For now I've set subsequent failures to 'take no action' - hopefully this will ease the pain.

            People

            Assignee:
            ifernandezcalvo Ivan Fernandez Calvo
            Reporter:
            t0yv0 Anton Tayanovskyy
            Votes:
            20 Vote for this issue
            Watchers:
            34 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: