Re: How to resolve "Process leaked file descriptor" issue which caused job failure in Jenkins

[Suhas]

Hi Mark, suffixing 0 to Exit has worked amazingly my issue has resolved. 
You deserve round of applaud. Many thanks Suhas India

On Friday, April 17, 2015 at 1:51:03 AM UTC+5:30, Mark Waite wrote:
>
> I'm surprised if a process leaking a file descriptor would cause a build 
> step to fail.  I've never seen it fail in any of the cases where it was 
> reported on my jobs.
>
> You may want to confirm that the build step did not fail, independent of 
> whether or not there was a leaked file descriptor.  If you're building on 
> Unix, be sure that the build step reports success (exit 0 from a shell 
> script, etc.).
>
> Mark Waite
>
> On Thu, Apr 16, 2015 at 1:49 PM Victoria Wei Lei  > wrote:
>
>> if it is hard to get rid of "Process leaked file descriptors",  is there 
>> anyway I can make Jenkins ignore this failure step (or don't fail it),  so 
>> I can move on next step.  
>> I am looking at Conditional buildstep plugin,  but not able to figure out 
>> how this plugin work and whether it is the right plugin to achieve above 
>> goal? 
>>
>> Please help.
>> Thanks
>> Victoria 
>>
>> On Tuesday, April 14, 2015 at 3:34:39 PM UTC-5, Victoria Wei Lei wrote:
>>>
>>> I need to invoke two window processes in order to start our test after 
>>> Jenkins build is down. They were normally killed after being brought up, 
>>> and I receive "Process leaked file descriptors". I found someone suggest to 
>>> do "set BUILD_ID=dontKillMe " before calling my command to start processes.
>>> Good news is that the processes are able to stay. Bad news is "Process 
>>> leaked file descriptors" still occur and mark Jenkins job failed, hence, I 
>>> can't execute any test steps afterwards
>>>
>>> Any input will be highly appreciated.
>>>
>> -- 
>> 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-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/1b0a16f2-a41d-4037-b793-2727882f64ec%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/69c8b4e3-e36a-4f45-a1b3-5f85569e03f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to resolve "Process leaked file descriptor" issue which caused job failure in Jenkins

[Suhas]

Hi Mark,

Just referred your comments and I have 0 to Exit as you shows below, and to 
my surprise jenkins error has disappeared, thanks a lot  

On Friday, April 17, 2015 at 1:51:03 AM UTC+5:30, Mark Waite wrote:
>
> I'm surprised if a process leaking a file descriptor would cause a build 
> step to fail.  I've never seen it fail in any of the cases where it was 
> reported on my jobs.
>
> You may want to confirm that the build step did not fail, independent of 
> whether or not there was a leaked file descriptor.  If you're building on 
> Unix, be sure that the build step reports success (exit 0 from a shell 
> script, etc.).
>
> Mark Waite
>
> On Thu, Apr 16, 2015 at 1:49 PM Victoria Wei Lei  > wrote:
>
>> if it is hard to get rid of "Process leaked file descriptors",  is there 
>> anyway I can make Jenkins ignore this failure step (or don't fail it),  so 
>> I can move on next step.  
>> I am looking at Conditional buildstep plugin,  but not able to figure out 
>> how this plugin work and whether it is the right plugin to achieve above 
>> goal? 
>>
>> Please help.
>> Thanks
>> Victoria 
>>
>> On Tuesday, April 14, 2015 at 3:34:39 PM UTC-5, Victoria Wei Lei wrote:
>>>
>>> I need to invoke two window processes in order to start our test after 
>>> Jenkins build is down. They were normally killed after being brought up, 
>>> and I receive "Process leaked file descriptors". I found someone suggest to 
>>> do "set BUILD_ID=dontKillMe " before calling my command to start processes.
>>> Good news is that the processes are able to stay. Bad news is "Process 
>>> leaked file descriptors" still occur and mark Jenkins job failed, hence, I 
>>> can't execute any test steps afterwards
>>>
>>> Any input will be highly appreciated.
>>>
>> -- 
>> 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-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/1b0a16f2-a41d-4037-b793-2727882f64ec%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/62dee9f9-1119-4938-bd8e-502e71032633%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to resolve "Process leaked file descriptor" issue which caused job failure in Jenkins

[Mark Waite]

In general, you don't need to fix the message that the process leaked file 
descriptors.  If the process leaks file descriptors, eventually it will 
exhaust the file descriptors, but that is not likely the cause of a problem 
for this specific job.

If you want processes to survive beyond the end of a job, then there are 
additional steps you need to take.  Refer 
to https://wiki.jenkins.io/display/JENKINS/Spawning+processes+from+build 
for techniques to keep a process running after the Jenkins job is complete.

Mark Waite

On Friday, June 23, 2017 at 12:57:19 AM UTC-6, parvatha reddy wrote:
>
>
> mark, 
>
> I did run Jenkins job in executing windows batch command. But Jenkins job 
> itself kill all the child process.due to Runtime Environment will be down. 
> can you please help us, how I can fix process leaked file descriptors 
> issue.
> execute shell the command:
>  N: 
> cd CCOP\REFRESH_SCRIPTS
> rebuild_env.cmd %EnvType%
>  
>
> Process leaked file descriptors. See 
> http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for 
> more information
> Triggering a new build of YP » Runtime stop and restart on ST1 
> 
>  
>
> Finished: SUCCESS 
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/94db626c-2815-489a-b73c-45f2a27b5a8e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to resolve "Process leaked file descriptor" issue which caused job failure in Jenkins

[parvatha reddy]

mark, 

I did run Jenkins job in executing windows batch command. But Jenkins job 
itself kill all the child process.due to Runtime Environment will be down. 
can you please help us, how I can fix process leaked file descriptors issue.
execute shell the command:
 N: 
cd CCOP\REFRESH_SCRIPTS
rebuild_env.cmd %EnvType%
 

Process leaked file descriptors. See 
http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for 
more information
Triggering a new build of YP » Runtime stop and restart on ST1 

 

Finished: SUCCESS 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e75c424b-167a-4d5f-835f-3dbe0ea96de0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to resolve "Process leaked file descriptor" issue which caused job failure in Jenkins

[Victoria Wei Lei]

Super!!

It worked by adding Exit 0 in the end of batch.  The "process leaking file 
descriptor" still there, but Jenkins returns Success. 

Thank you so much, Mark!

Best regards
Victoria 

On Thursday, April 16, 2015 at 5:08:28 PM UTC-5, Mark Waite wrote:
>
> I think those two lines are independent of one another.  The line:
>
> Build step 'Execute Windows batch command' marked build as failure
>
>
> hints that the batch script returned a failure code to its calling 
> environment.  I believe the default exit value for a batch script is the 
> exit value of the last command executed in that script.  If you want to 
> ignore that last return value, add 
>
> EXIT 0
>
> to the end of the first batch script so that it will always return success.
>
> Mark Waite
>
> On Thu, Apr 16, 2015 at 2:39 PM Victoria Wei Lei  > wrote:
>
>> Mark, 
>>
>> the particular step is to call two processes by window batch command, 
>>  those processes are successfully running after I set BUILD_ID=dontKillMe.  
>> Jenkins job was still marked as failure:
>>
>> Process leaked file descriptors. See 
>> http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for 
>> more information
>> Build step 'Execute Windows batch command' marked build as failure
>>
>>
>> Thanks
>> On Thursday, April 16, 2015 at 3:21:03 PM UTC-5, Mark Waite wrote:
>>
>>> I'm surprised if a process leaking a file descriptor would cause a build 
>>> step to fail.  I've never seen it fail in any of the cases where it was 
>>> reported on my jobs.
>>>
>>> You may want to confirm that the build step did not fail, independent of 
>>> whether or not there was a leaked file descriptor.  If you're building on 
>>> Unix, be sure that the build step reports success (exit 0 from a shell 
>>> script, etc.).
>>>
>>> Mark Waite
>>>
>>> On Thu, Apr 16, 2015 at 1:49 PM Victoria Wei Lei  
>>> wrote:
>>>
>> if it is hard to get rid of "Process leaked file descriptors",  is there 
 anyway I can make Jenkins ignore this failure step (or don't fail it),  so 
 I can move on next step.  
 I am looking at Conditional buildstep plugin,  but not able to figure 
 out how this plugin work and whether it is the right plugin to achieve 
 above goal? 

 Please help.
 Thanks
 Victoria 

 On Tuesday, April 14, 2015 at 3:34:39 PM UTC-5, Victoria Wei Lei wrote:
>
> I need to invoke two window processes in order to start our test after 
> Jenkins build is down. They were normally killed after being brought up, 
> and I receive "Process leaked file descriptors". I found someone suggest 
> to 
> do "set BUILD_ID=dontKillMe " before calling my command to start 
> processes.
> Good news is that the processes are able to stay. Bad news is "Process 
> leaked file descriptors" still occur and mark Jenkins job failed, hence, 
> I 
> can't execute any test steps afterwards
>
> Any input will be highly appreciated.
>
  -- 
 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-use...@googlegroups.com.
>>>
>>>
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-users/1b0a16f2-a41d-4037-b793-2727882f64ec%40googlegroups.com
  
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>>  -- 
>> 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-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/2db1326a-066f-4cfe-9adc-3d5b814dad11%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/67d0e652-0422-49e7-b304-33238fcc4b06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to resolve "Process leaked file descriptor" issue which caused job failure in Jenkins

[Mark Waite]

I think those two lines are independent of one another.  The line:

Build step 'Execute Windows batch command' marked build as failure


hints that the batch script returned a failure code to its calling
environment.  I believe the default exit value for a batch script is the
exit value of the last command executed in that script.  If you want to
ignore that last return value, add

EXIT 0

to the end of the first batch script so that it will always return success.

Mark Waite

On Thu, Apr 16, 2015 at 2:39 PM Victoria Wei Lei  wrote:

> Mark,
>
> the particular step is to call two processes by window batch command,
>  those processes are successfully running after I set BUILD_ID=dontKillMe.
> Jenkins job was still marked as failure:
>
> Process leaked file descriptors. See 
> http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for 
> more information
> Build step 'Execute Windows batch command' marked build as failure
>
>
> Thanks
> On Thursday, April 16, 2015 at 3:21:03 PM UTC-5, Mark Waite wrote:
>
>> I'm surprised if a process leaking a file descriptor would cause a build
>> step to fail.  I've never seen it fail in any of the cases where it was
>> reported on my jobs.
>>
>> You may want to confirm that the build step did not fail, independent of
>> whether or not there was a leaked file descriptor.  If you're building on
>> Unix, be sure that the build step reports success (exit 0 from a shell
>> script, etc.).
>>
>> Mark Waite
>>
>> On Thu, Apr 16, 2015 at 1:49 PM Victoria Wei Lei 
>> wrote:
>>
> if it is hard to get rid of "Process leaked file descriptors",  is there
>>> anyway I can make Jenkins ignore this failure step (or don't fail it),  so
>>> I can move on next step.
>>> I am looking at Conditional buildstep plugin,  but not able to figure
>>> out how this plugin work and whether it is the right plugin to achieve
>>> above goal?
>>>
>>> Please help.
>>> Thanks
>>> Victoria
>>>
>>> On Tuesday, April 14, 2015 at 3:34:39 PM UTC-5, Victoria Wei Lei wrote:

 I need to invoke two window processes in order to start our test after
 Jenkins build is down. They were normally killed after being brought up,
 and I receive "Process leaked file descriptors". I found someone suggest to
 do "set BUILD_ID=dontKillMe " before calling my command to start processes.
 Good news is that the processes are able to stay. Bad news is "Process
 leaked file descriptors" still occur and mark Jenkins job failed, hence, I
 can't execute any test steps afterwards

 Any input will be highly appreciated.

>>>  --
>>> 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-use...@googlegroups.com.
>>
>>
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/1b0a16f2-a41d-4037-b793-2727882f64ec%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>  --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/2db1326a-066f-4cfe-9adc-3d5b814dad11%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEe%3DaBvjTzkU6EHcQ349t4JF5oa%3D7H%3DgJMr978AB6DcQA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to resolve "Process leaked file descriptor" issue which caused job failure in Jenkins

[Victoria Wei Lei]

Mark, 

the particular step is to call two processes by window batch command, 
 those processes are successfully running after I set BUILD_ID=dontKillMe. 
 Jenkins job was still marked as failure:

Process leaked file descriptors. See 
http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for 
more information
Build step 'Execute Windows batch command' marked build as failure


Thanks
On Thursday, April 16, 2015 at 3:21:03 PM UTC-5, Mark Waite wrote:
>
> I'm surprised if a process leaking a file descriptor would cause a build 
> step to fail.  I've never seen it fail in any of the cases where it was 
> reported on my jobs.
>
> You may want to confirm that the build step did not fail, independent of 
> whether or not there was a leaked file descriptor.  If you're building on 
> Unix, be sure that the build step reports success (exit 0 from a shell 
> script, etc.).
>
> Mark Waite
>
> On Thu, Apr 16, 2015 at 1:49 PM Victoria Wei Lei  > wrote:
>
>> if it is hard to get rid of "Process leaked file descriptors",  is there 
>> anyway I can make Jenkins ignore this failure step (or don't fail it),  so 
>> I can move on next step.  
>> I am looking at Conditional buildstep plugin,  but not able to figure out 
>> how this plugin work and whether it is the right plugin to achieve above 
>> goal? 
>>
>> Please help.
>> Thanks
>> Victoria 
>>
>> On Tuesday, April 14, 2015 at 3:34:39 PM UTC-5, Victoria Wei Lei wrote:
>>>
>>> I need to invoke two window processes in order to start our test after 
>>> Jenkins build is down. They were normally killed after being brought up, 
>>> and I receive "Process leaked file descriptors". I found someone suggest to 
>>> do "set BUILD_ID=dontKillMe " before calling my command to start processes.
>>> Good news is that the processes are able to stay. Bad news is "Process 
>>> leaked file descriptors" still occur and mark Jenkins job failed, hence, I 
>>> can't execute any test steps afterwards
>>>
>>> Any input will be highly appreciated.
>>>
>>  -- 
>> 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-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/1b0a16f2-a41d-4037-b793-2727882f64ec%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/2db1326a-066f-4cfe-9adc-3d5b814dad11%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to resolve "Process leaked file descriptor" issue which caused job failure in Jenkins

[Mark Waite]

I'm surprised if a process leaking a file descriptor would cause a build
step to fail.  I've never seen it fail in any of the cases where it was
reported on my jobs.

You may want to confirm that the build step did not fail, independent of
whether or not there was a leaked file descriptor.  If you're building on
Unix, be sure that the build step reports success (exit 0 from a shell
script, etc.).

Mark Waite

On Thu, Apr 16, 2015 at 1:49 PM Victoria Wei Lei  wrote:

> if it is hard to get rid of "Process leaked file descriptors",  is there
> anyway I can make Jenkins ignore this failure step (or don't fail it),  so
> I can move on next step.
> I am looking at Conditional buildstep plugin,  but not able to figure out
> how this plugin work and whether it is the right plugin to achieve above
> goal?
>
> Please help.
> Thanks
> Victoria
>
> On Tuesday, April 14, 2015 at 3:34:39 PM UTC-5, Victoria Wei Lei wrote:
>>
>> I need to invoke two window processes in order to start our test after
>> Jenkins build is down. They were normally killed after being brought up,
>> and I receive "Process leaked file descriptors". I found someone suggest to
>> do "set BUILD_ID=dontKillMe " before calling my command to start processes.
>> Good news is that the processes are able to stay. Bad news is "Process
>> leaked file descriptors" still occur and mark Jenkins job failed, hence, I
>> can't execute any test steps afterwards
>>
>> Any input will be highly appreciated.
>>
>  --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/1b0a16f2-a41d-4037-b793-2727882f64ec%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGmaX1FYmqRf4QbMYRL2B%3D%3DCohwFEJgj5zPogVwZeDCYQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to resolve "Process leaked file descriptor" issue which caused job failure in Jenkins

[Victoria Wei Lei]

if it is hard to get rid of "Process leaked file descriptors",  is there 
anyway I can make Jenkins ignore this failure step (or don't fail it),  so 
I can move on next step.  
I am looking at Conditional buildstep plugin,  but not able to figure out 
how this plugin work and whether it is the right plugin to achieve above 
goal? 

Please help.
Thanks
Victoria 

On Tuesday, April 14, 2015 at 3:34:39 PM UTC-5, Victoria Wei Lei wrote:
>
> I need to invoke two window processes in order to start our test after 
> Jenkins build is down. They were normally killed after being brought up, 
> and I receive "Process leaked file descriptors". I found someone suggest to 
> do "set BUILD_ID=dontKillMe " before calling my command to start processes.
> Good news is that the processes are able to stay. Bad news is "Process 
> leaked file descriptors" still occur and mark Jenkins job failed, hence, I 
> can't execute any test steps afterwards
>
> Any input will be highly appreciated.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1b0a16f2-a41d-4037-b793-2727882f64ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How to resolve "Process leaked file descriptor" issue which caused job failure in Jenkins

[Victoria Wei Lei]

I need to invoke two window processes in order to start our test after 
Jenkins build is down. They were normally killed after being brought up, 
and I receive "Process leaked file descriptors". I found someone suggest to 
do "set BUILD_ID=dontKillMe " before calling my command to start processes.
Good news is that the processes are able to stay. Bad news is "Process 
leaked file descriptors" still occur and mark Jenkins job failed, hence, I 
can't execute any test steps afterwards

Any input will be highly appreciated.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/70e6e7a6-7010-4c4b-9a9a-67d243e41f09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.