在JENKINS上处理泄漏的文件描述符错误 [英] Process leaked file descriptors error on JENKINS

问题描述

我将作业配置为停止和启动tomcat服务器时收到此错误:

处理泄漏的文件描述符.参见 http://wiki.jenkins-ci.org/display/JENKINS/Spawning + processes + from + build 了解更多信息

当我用Google搜索它时，我得到了一个推荐的解决方案，如set BUILD_ID=dontKillMe
这是确切的解决方案吗?
如果是，我需要在哪里设置BUILD_ID?内部ant/post构建脚本?
有人可以澄清一下吗?

解决方案

是的，为进程创建伪造的BUILD_ID会告诉Jenkins在检测到生成的进程期间忽略此进程，因此该进程在完成作业后不会被杀死. >

用法:在命令前输入BUILD_ID=dontKillMe，例如进入Execute shell构建步骤:

 BUILD_ID=dontKillMe nohup ./yourStartScript.sh &

注意:另请参见 nohup

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?

解决方案

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

这篇关于在JENKINS上处理泄漏的文件描述符错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！