[JIRA] [build-environment-plugin] (JENKINS-22088) Disk space leak with multiple copies of winstone-XXXX.jar in TEMP folder

732 views
Skip to first unread message

jenkins@plnech.fr (JIRA)

unread,
May 11, 2015, 6:29:01 PM5/11/15
to jenkinsc...@googlegroups.com
PL Nech commented on Bug JENKINS-22088
 
Re: Disk space leak with multiple copies of winstone-XXXX.jar in TEMP folder

Hi there,

I have the same problem with Jenkins ver. 1.612 on Windows 7 64bits.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

jbeeckman@compliancesystems.com (JIRA)

unread,
Oct 12, 2015, 12:19:01 PM10/12/15
to jenkinsc...@googlegroups.com

Same here on 1.627 on Windows 2008 R2 64 Bit. I'm going to manually clear it out, but this should be fixed.

amarasco@vsi-corp.com (JIRA)

unread,
Nov 9, 2015, 6:37:02 AM11/9/15
to jenkinsc...@googlegroups.com

This seems to happen on non-Windows as well; I have a Linux server and have a bunch in /tmp.

koiraladipak@gmail.com (JIRA)

unread,
Jan 8, 2016, 9:55:01 AM1/8/16
to jenkinsc...@googlegroups.com

Is there a workaround yet? Do we need to manually delete all the winstoneXXXXXXXXXXXX.jar? Deleting these jars won't affect anything, right? We have Jenkins ver. 1.613 and facing the same issue. Almost 70 GB space is full within 3 months. And I saw most of the space is taken by winstone.jar in temp folder.

koiraladipak@gmail.com (JIRA)

unread,
Jan 8, 2016, 11:37:03 AM1/8/16
to jenkinsc...@googlegroups.com
Deepak Koirala edited a comment on Bug JENKINS-22088
Is there a workaround yet? Do we need to manually delete all the winstoneXXXXXXXXXXXX.jar? Deleting these jars won't affect anything, right? We have Jenkins ver. 1.613 , installed in windows server  and facing the same issue. Almost 70 GB space is full within 3 months. And I saw most of the space is taken by winstone.jar in temp folder. 

noel@bardelot.fr (JIRA)

unread,
Mar 24, 2016, 10:13:01 AM3/24/16
to jenkinsc...@googlegroups.com

mynewspamaccount@gmx.com (JIRA)

unread,
May 3, 2016, 6:40:03 AM5/3/16
to jenkinsc...@googlegroups.com
Daniel commented on Bug JENKINS-22088

I just stumbled upon this Issue and used https://wiki.jenkins-ci.org/display/JENKINS/Tmp+Cleaner+Plugin as a workaround.
Had to set all mentioned parameters with system properties when starting Jenkins but result was a cleaned /var/tmp after that.
YMMV, but might be a valid workaround. HTH, Daniel

jenkins.js@crypt.se (JIRA)

unread,
Feb 3, 2017, 7:02:01 AM2/3/17
to jenkinsc...@googlegroups.com

I was also affected by this on Windows Server 2008, caused by an old jenkins process lying around while the service started another. A new winstone-XXXX.jar of 2 MB was created once every two seconds. I killed all java processes, deleted all files and restarted the service. Now there's only one of these jar files.

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

jenkins.js@crypt.se (JIRA)

unread,
Feb 3, 2017, 7:05:02 AM2/3/17
to jenkinsc...@googlegroups.com
Johan Svensson edited a comment on Bug JENKINS-22088
I was also affected by this on Windows Server 2008, caused by an old jenkins process lying around while the service started another. A new winstone-XXXX.jar of 2 MB was created once every two seconds. I killed all java processes, deleted all files and restarted the service. Now there's only one of these jar files.


I don't know the inners of jenkins, but there should be some sanity check before creating a new winstone-XXXX.jar.

erwin.mueller@nttdata.com (JIRA)

unread,
Feb 7, 2017, 4:09:01 AM2/7/17
to jenkinsc...@googlegroups.com

Hello. Just run in this issue on our build server.
Jenkins ver. 2.32.1.
Windows Server 2008 R2 Standard 64 Bit.
winstone-XXXX.jar was created and filled up disk space on C:. Solution was to kill all Jenkins/Java processes and restart Jenkins.

juri.strumpflohner@gmail.com (JIRA)

unread,
Mar 23, 2017, 6:51:02 AM3/23/17
to jenkinsc...@googlegroups.com

same here. We just upgraded to 2.32.3 a couple of days ago and now I have this issue. Didn't have it before, at least I did not notice anything.

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

juri.strumpflohner@gmail.com (JIRA)

unread,
Mar 23, 2017, 6:55:02 AM3/23/17
to jenkinsc...@googlegroups.com
Juri Strumpflohner edited a comment on Bug JENKINS-22088
same here. We just upgraded to 2.32.3 a couple of days ago and now I have this issue. Didn't have it before, at least I did not notice anything.


The question is, can I delete them safely?

jenkins.js@crypt.se (JIRA)

unread,
Mar 23, 2017, 7:39:02 AM3/23/17
to jenkinsc...@googlegroups.com

Juri Strumpflohner, you probably have an old process running from the previous version. Close all jenkins processes including any old ones, remove all of the temp files and start it up. That's how I solved it and I'm pretty sure it's safe.

ifernandezcalvo@cloudbees.com (JIRA)

unread,
Feb 14, 2018, 5:44:03 PM2/14/18
to jenkinsc...@googlegroups.com

peter.hannon.junk@gmail.com (JIRA)

unread,
Apr 4, 2019, 6:42:02 AM4/4/19
to jenkinsc...@googlegroups.com
Peter Hannon commented on Bug JENKINS-22088
 
Re: Disk space leak with multiple copies of winstone-XXXX.jar in TEMP folder

I am still seeing this issue with Jenkins v 2.121.3. From jenkins release notes I thought this had been fixed in v2.107.1

I noticed recently that there were several winstone jars in my /tmp. I manually removed all but the most recent.  I then did a safeRestart of Jenkins and there were then 2 winstone jars in the /tmp directory of the master Jenkins node.

ls -lrt winstone*.jar
-rw-r--r-- 1 jenkins users 2146767 2019-03-04 12:23 winstone9180695101677339973.jar
-rw-r--r-- 1 jenkins users 2146767 2019-04-04 11:21 winstone8639977864837551161.jar

We are running the Jenkins war directly via a shell script

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

 

I'm not sure if it's related but I am also seeing some empty jetty directories with similar timestamps:

ls -ldrt jetty*
drwxr-xr-x 2 jenkins users 4096 2019-03-04 12:23 jetty-0.0.0.0-8081-war-_-any-2428298004054280574.dir
drwxr-xr-x 2 jenkins users 4096 2019-04-04 11:21 jetty-0.0.0.0-8081-war-_-any-7220745071344149958.dir

 

 

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

peter.hannon.junk@gmail.com (JIRA)

unread,
Apr 4, 2019, 7:01:03 AM4/4/19
to jenkinsc...@googlegroups.com
Peter Hannon edited a comment on Bug JENKINS-22088
I am still seeing this issue with Jenkins v 2.121.3. From   [jenkins release notes|[https://jenkins.io/changelog-stable/#v2.107.1]]   I thought this had been fixed in v2.107.1


I noticed recently that there were several winstone jars in my /tmp. I manually removed all but the most recent.  I then did a safeRestart of Jenkins and there were then 2 winstone jars in the /tmp directory of the master Jenkins node.
{code:java}

ls -lrt winstone*.jar
-rw-r--r-- 1 jenkins users 2146767 2019-03-04 12:23 winstone9180695101677339973.jar
-rw-r--r-- 1 jenkins users 2146767 2019-04-04 11:21 winstone8639977864837551161.jar
{code}

We are running the Jenkins war directly via a shell script
{code:java}

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

 

I'm not sure if it's related but I am also seeing some empty jetty directories with similar timestamps:
{code:java}

ls -ldrt jetty*
drwxr-xr-x 2 jenkins users 4096 2019-03-04 12:23 jetty-0.0.0.0-8081-war-_-any-2428298004054280574.dir
drwxr-xr-x 2 jenkins users 4096 2019-04-04 11:21 jetty-0.0.0.0-8081-war-_-any-7220745071344149958.dir
{code}
 

 

peter.hannon.junk@gmail.com (JIRA)

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

kuisathaverat@gmail.com (JIRA)

unread,
Apr 4, 2019, 9:15:10 AM4/4/19
to jenkinsc...@googlegroups.com

if you only upgrade the Jenkins instance, the issue would be not resolved. The change is in the windows service that launches the Agent, so to resolve the issue you have to uninstall and install again the windows service if not, you would not change anything

peter.hannon.junk@gmail.com (JIRA)

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

Ivan Fernandez Calvo thanks for the reply, if you see my comment (the shell script), I'm running this in linux, so the windows service change is not applicable for me.

Are you saying for a linux environment, this generated winstone jar file needs to be cleaned manually?

kuisathaverat@gmail.com (JIRA)

unread,
Apr 4, 2019, 1:01:02 PM4/4/19
to jenkinsc...@googlegroups.com
~ if you only upgrade the Jenkins instance, the issue would be not resolved. The change is in the windows service that launches the Agent, so to resolve the issue you have to uninstall and install again the windows service if not, you would not change anything ~

kuisathaverat@gmail.com (JIRA)

unread,
Apr 4, 2019, 1:02:03 PM4/4/19
to jenkinsc...@googlegroups.com
Ivan Fernandez Calvo updated an issue
 
Comment: ~if you only upgrade the Jenkins instance, the issue would be not resolved. The change is in the windows service that launches the Agent, so to resolve the issue you have to uninstall and install again the windows service if not, you would not change anything~

kuisathaverat@gmail.com (JIRA)

unread,
Apr 4, 2019, 1:07:03 PM4/4/19
to jenkinsc...@googlegroups.com

peter.hannon.junk@gmail.com (JIRA)

unread,
Apr 5, 2019, 12:12:03 PM4/5/19
to jenkinsc...@googlegroups.com

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!

 

shashank.kulsh@gmail.com (JIRA)

unread,
Aug 14, 2019, 1:51:03 AM8/14/19
to jenkinsc...@googlegroups.com

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

kuisathaverat@gmail.com (JIRA)

unread,
Aug 15, 2019, 2:53:04 PM8/15/19
to jenkinsc...@googlegroups.com

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

mattsbarna@gmail.com (JIRA)

unread,
Nov 11, 2019, 10:03:03 AM11/11/19
to jenkinsc...@googlegroups.com

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.

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages