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

localkube leaving 'wc' zombies #940

Closed
ankon opened this issue Dec 20, 2016 · 3 comments
Closed

localkube leaving 'wc' zombies #940

ankon opened this issue Dec 20, 2016 · 3 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@ankon
Copy link
Contributor

ankon commented Dec 20, 2016

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

BUG REPORT.

Minikube version (use minikube version):
minikube version: v0.14.0

Environment:

  • OS (e.g. from /etc/os-release): Fedora 25 x86_64
  • VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName): kvm
  • Docker version (e.g. docker -v): Docker version 1.12.5, build 6009905/1.12.5

Noticed the issue both with minikube v0.14.0 and v0.13.1, cannot remember whether I saw it with earlier versions.

What happened:

I'm looking inside the VM with top, and I see a lot of wc processes in Z state, under the localkube process. Watching it for a while: There is a du process that quickly goes away, and then a wc, which sometimes but not always doesn't seem to get reaped. Eventually the VM can have hundreds of these zombies.

What you expected to happen:

Zombie-free environment :)

How to reproduce it (as minimally and precisely as possible):

For me it just happens when running the VM with some pods in it, nothing "special" is done.

Anything else do we need to know:

Guess: It's somewhere in vendor/github.com/google/cadvisor/fs/fs.go, which seems to talk about du and wc processes. My go-foo isn't anywhere close to knowing how to debug it further.

screen-minikube-wc-zombies

@r2d4
Copy link
Contributor

r2d4 commented Dec 20, 2016

This has already been fixed in the new ISO
http://storage.googleapis.com/minikube/iso/buildroot/minikube-v1.0.1.iso

However, we haven't backported a fix to the b2d ISO yet.

ref #923

When find exits with an error, the wait for the wc process never happens and wc becomes a zombie. On systems without GNU find, these zombies can accrue quickly.

This PR looks like it fixes the problem upstream google/cadvisor#1558

@r2d4 r2d4 added kind/bug Categorizes issue or PR as related to a bug. iso/b2d labels Dec 20, 2016
@ankon
Copy link
Contributor Author

ankon commented Dec 21, 2016

Thanks for the reply.

Quickly tested it with minikube start --vm-driver virtualbox --iso-url https://storage.googleapis.com/minikube/iso/minikube-v1.0.1.iso --kubernetes-version v1.4.5 --memory 4096, looks good!

@dlorenc
Copy link
Contributor

dlorenc commented Jan 5, 2017

We're not going to backport this to the old iso, this will be fixed in the new ISO in our next release.

@dlorenc dlorenc closed this as completed Jan 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

3 participants