Jenkins can be running many simultaneous subprocesses each of which consume a few filehandles. We started seeing messages like this, and used a 2 pronged method. First we used ulimit settings to double the allowable open filehandles, then we switched many tasks from shell scripts to other tools that are less likely to use subprocesses so heavily.
typed on my phone expect typos... On 17 Feb 2012 06:59, "Suri" <[email protected]> wrote: > Hi > > When we are using “buildResultTrigger-polling plug-in” we are getting > below error frequently. Jenkins version is 1.411 > > > INFO: opalp05_r1.4_dev_R4_UAT_dotnet #31 main build action completed: > SUCCESS > Feb 16, 2012 7:51:59 PM > org.jenkinsci.plugins.buildresulttrigger.BuildResultTrigger run > SEVERE: Severe Error during the trigger execution /var/lib/jenkins/ > jobs/bcppsgl_r11.11_dev_GLDM_dependency_export/buildResultTrigger- > polling.log (Too many open files) > java.io.FileNotFoundException: /var/lib/jenkins/jobs/ > bcppsgl_r11.11_dev_GLDM_dependency_export/buildResultTrigger- > polling.log (Too many open files) > at java.io.FileOutputStream.open(Native Method) > at java.io.FileOutputStream.<init>(FileOutputStream.java:205) > at java.io.FileOutputStream.<init>(FileOutputStream.java:157) > > > Once the above mentioned error arise, the Jenkins webpage is getting > down. > Can anyone please advise me accordingly. > > >
