I have similar problems: Every evening my jenkins server dies: It uses the whole memory allocated (2GB out of 12GB) and the garbage collector starts running. From then on, i am not able to reach the webinterface any more.
<https://lh6.googleusercontent.com/-PpJ8u3onuNI/UxRD2OfRtQI/AAAAAAAANSw/HgurO9jTlo8/s1600/Bildschirmfoto+2014-03-03+um+9.55.38.png> <https://lh4.googleusercontent.com/-pGRAmTxI0ng/UxRDyk-VIMI/AAAAAAAANSo/97qmycBxA9c/s1600/Bildschirmfoto+2014-03-03+um+9.55.54.png> The log shows two kinds of errors: 28.02.2014 18:05:45 jenkins.diagnostics.ooom.Problem$Inspector scan WARNUNG: Failed to inspect /var/lib/jenkins/jobs/(BUILD) mp-modules master integration/builds/1956: /var/lib/jenkins/jobs/(BUILD) mp-modules master integration/builds/1956/build.xml doesn't exist 28.02.2014 18:05:45 jenkins.diagnostics.ooom.Problem$Inspector scan WARNUNG: Failed to inspect /var/lib/jenkins/jobs/(BUILD) mp-modules master integration/builds/1991: /var/lib/jenkins/jobs/(BUILD) mp-modules master integration/builds/1991/build.xml doesn't exist 28.02.2014 18:05:45 jenkins.diagnostics.ooom.Problem$Inspector scan WARNUNG: Failed to inspect /var/lib/jenkins/jobs/(BUILD) mp-modules master integration/builds/2115: /var/lib/jenkins/jobs/(BUILD) mp-modules master integration/builds/2115/build.xml doesn't exist and 28.02.2014 18:05:08 hudson.Proc$LocalProc join WARNUNG: Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information java.lang.Exception at hudson.Proc$LocalProc.join(Proc.java:329) at hudson.Proc.joinWithTimeout(Proc.java:168) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1169) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1150) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1146) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:962) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:972) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.setRemoteUrl(CliGitAPIImpl.java:684) at hudson.plugins.git.GitAPI.setRemoteUrl(GitAPI.java:120) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:611) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:531) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:455) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1602) at hudson.model.AbstractProject._poll(AbstractProject.java:1572) at hudson.model.AbstractProject.poll(AbstractProject.java:1490) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:462) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:491) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) 28.02.2014 18:05:08 hudson.Proc$LocalProc join WARNUNG: Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information java.lang.Exception at hudson.Proc$LocalProc.join(Proc.java:329) at hudson.Proc.joinWithTimeout(Proc.java:168) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1169) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1150) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1146) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:962) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:972) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.hasGitRepo(CliGitAPIImpl.java:124) at hudson.plugins.git.GitAPI.hasGitRepo(GitAPI.java:186) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:525) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:455) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1602) at hudson.model.AbstractProject._poll(AbstractProject.java:1572) at hudson.model.AbstractProject.poll(AbstractProject.java:1490) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:462) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:491) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) Am Dienstag, 4. Februar 2014 09:13:22 UTC+1 schrieb Vincent Massol: > > Hi guys, > > Since I've upgraded our jenkins to 1.549 we're having a lot of trouble. It > seems jenkins dies every day so every morning I need to restart it and it > takes 15-20 minute to start up. > > I've checked the log file today and I've noticed tons of the following > kinds of messages: > > Feb 4, 2014 8:07:39 AM jenkins.diagnostics.ooom.Problem$Inspector scan > > WARNING: Failed to inspect > /home/maven/.hudson/jobs/xwiki-platform-core-site-job/modules/org.xwiki.platform$xwiki-platform-wysiwyg-war/builds/53: > > /home/maven/.hudson/jobs/xwiki-platform-core-site-job/modules/org.xwiki.platform$xwiki-platform-wysiwyg-war/builds/53/build.xml > > doesn't exist > > Feb 4, 2014 8:07:49 AM jenkins.diagnostics.ooom.Problem$Inspector scan > > WARNING: Failed to inspect > /home/maven/.hudson/jobs/xwiki-platform-core-site-job/modules/org.xwiki.platform$xwiki-platform-xml/builds/54: > > /home/maven/.hudson/jobs/xwiki-platform-core-site-job/modules/org.xwiki.platform$xwiki-platform-xml/builds/54/build.xml > > doesn't exist > > I have 2 questions: > > > - Are these important and how to fix our jenkins install so that we > don't have these anymore? > - Could they impact performances of our jenkins insance (which is very > slow at times, more often than not)? > > Thanks a lot > > -Vincent > > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
