-
-
Notifications
You must be signed in to change notification settings - Fork 223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
defunct sh and sleep processes when running on slave-jnlp #714
Comments
Likely it is a Pipeline issue, not the container one. Would you be able to try it on a similar environment without containers? |
This could happen if the Java process dies abruptly without reaping children |
I was not able to reproduce this using a jnlp connected agent running on a ubuntu vm. The java process did not die in any instance. I guess that is why the master is being started with /bin/tini so that java does not use process id 1. I will try to create an image where java is not running as PID1 and retry the test. |
when running the jenkins/jnlp-slave:latest container interactively with bash and then running java does not result in defunct processes, so adding another process should solve it. |
with tini as PID 1 I am not getting defunct processes, solved that in my image.
|
Closing as the PR were refused (and the defunct process are not reproducible anymore) |
Hello,
When running multiple sh commands within a pipeline, I am receiving multiple defunct sh and sleep processes, if the job runs within a jenkins/jnlp-slave:latest docker container.
The master is running on the same host using jenkins/jenkins:lts-alpine and if the jobs runs on the master, I cannot find any defunct processes.
Setup
Repro
The simplest pipeline to reproduce the problem may be:
And after running the job list the defunct proccesses on the host:
$
ps aux | grep defunct | grep -v grep
The text was updated successfully, but these errors were encountered: