Process leaked file descriptors error on JENKINS

Question

I am getting this error when I configured a job to do stop and start of tomcat server:

Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information

When i googled it, i got a recommended solution as set BUILD_ID=dontKillMe
Is this the exact solution?
If yes, where do I need to set BUILD_ID? Inside ant/post build script?
Can anyone please clarify this?

score 16 · Answer 1 · edited May 04 '17 at 12:25

16

Yes, creating fake BUILD_ID for process tells Jenkins to ignore this process during detection spawned processes, so this process will be not killed after finishing job.

Usage: Enter BUILD_ID=dontKillMe before your command, for example into Execute shell build step:

 BUILD_ID=dontKillMe nohup ./yourStartScript.sh &

Note: See also nohup

edited May 04 '17 at 12:25

Arpit Aggarwal

27,626
16
90
108

answered Feb 28 '14 at 13:28

lu_ko

4,055
2
26
31

1

it doesn't work for me within a build step... I believe it should be environment variable – Vytalyi Dec 17 '15 at 09:28
1

@Vytalyi I added export BUILD_ID=dontKillMe and it worked for me. – tintin May 30 '17 at 20:37
what should be written for windows? and where ? – Bilbo Baggins Dec 04 '17 at 13:08
`set BUILD_ID=dontKillMe nohup start yourFIle.bat` just add that as one line – Zhivko.Kostadinov Feb 25 '20 at 06:53

NK. · Answer 2 · 2020-03-31T15:38:15.103

11

By default, Jenkins will kill all the spawned process at the completion of build.

To override this, you need to create environment variable BUILD_ID.

Go to Jenkins -> Manage Jenkins -> Configure System.

Now under Global properties section, under Environment variables, click on ADD button to add new Environment variable. Give name=BUILD_ID and value=allow_to_run_as_daemon start_my_service
Click on save button. And you are done.

Now the spawn process will continue to execute even after the build got completed.

edited Mar 31 '20 at 15:38

answered Aug 24 '17 at 10:27

NK.

111
1
5

Beautifully worked for a long-running Angular build – Scar Coder Sep 02 '19 at 20:34
Thanks its works for me in windows and running long bat file – Dhrumil Shah Jun 09 '20 at 13:26

score 6 · Answer 3 · answered Feb 05 '14 at 02:42

6

Add this line as a JAVA_ARGS argument when you start your jenkins server (I put mine on /etc/default/jenkins in my Ubuntu box)

-Dhudson.util.ProcessTree.disable=true

And you're done

answered Feb 05 '14 at 02:42

Arx Cruz

115
1
3

10

The feature is in place to prevent accidental process leak from builds. Turning it off entirely because of one job is unnecessarily dangerous. – Oliver Gondža May 16 '16 at 12:05

Gonen · Answer 4 · 2013-07-23T11:31:32.983

3

You are calling a command from Jenkins that spawns another process -
the tomcat-start command ends, but its child-process is still running
(this is the actual tomcat web-server you attempted to start).

Jenkins sometimes identifies this situation as a possible problem,
but the page you have mentioned also explains how to solve it
(in short: Don't start tomcat from Jenkins unless you know how).

edited Jul 23 '13 at 11:31

answered Jun 10 '13 at 19:52

Gonen

4,005
1
31
39

score 1 · Answer 5 · answered Jun 30 '20 at 03:50

1

Tried different suggestions but none of the options worked for me. Finally I switched to previous version of jenkins and it worked. I switched from 2.3 to 1.581 and it worked.

answered Jun 30 '20 at 03:50

MIM

499
3
11
30

Process leaked file descriptors error on JENKINS

5 Answers5

Linked