Skip to content
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

[ZMQbg/1] can't be killed!!! #4828

Open
wildkid1024 opened this issue Aug 14, 2019 · 3 comments
Open

[ZMQbg/1] can't be killed!!! #4828

wildkid1024 opened this issue Aug 14, 2019 · 3 comments

Comments

@wildkid1024
Copy link

My notebook is running in the backgroud and I use command & to do that.
But when I close a kernel and kill the backgroud process and I use the command kill -9.
Then I find some process named [ZMQbg/1] which is runing, it can't be killed by any command,
and its ppid become init(1). so what should I do to kill it without reboot?

@kevin-bates
Copy link
Member

You should always use kill <pid> or kill -15 <pid> (SIGTERM) when terminating the notebook server, otherwise its signal handler to cleanup (including an attempt to stop any running kernels) will not be invoked.

It's not clear to me under what conditions ZMQbg processes come into play, but getting inherited by init would be consistent with not getting cleaned up on termination.

when I close a kernel

Are you specifically shutting the kernel down or just closing the notebook tab? Just asking since the latter would leave the kernel running along with any supporting processes.

At any rate, try not using -9 (SIGKILL) and see if you still see the zombie ZMQbg processes.

(You'll probably need to reboot to clear up the current zombies since they're owned by init. Please try the kill -15 experiment first so you'd only need to reboot once should it prove unhelpful.)

@ghost
Copy link

ghost commented Dec 16, 2019

I came here because of similar problems. I just had to use sudo then it worked.
(I'm using CoreOS)

@wildkid1024
Copy link
Author

I came here because of similar problems. I just had to use sudo then it worked.
(I'm using CoreOS)

To prevent the same thing,I think that you must close the browser tab(local or remote) before you use command 'kill -9' !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants