-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: stuck at stopTheWorldWithSema during k8s operations #25207
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
Comments
Please mention the complete repro steps, including how to download and install the package and the commands used to create, delete containers. Also, can you try with latest Go 1.10.2 ? Thanks. |
@agnivade I found the backtrace very strange, maybe any other thread broken the stack?
Thanks for your help! |
Ok, so you are using a python client to interact with a kubernetes cluster ? Please correct me if I am wrong, but this seems more like a kubernetes bug rather than a Go bug. You may get more help filing an issue on the kubernetes repo. |
The stack trace in #25207 (comment) is not a meaningful trace. Frames 77 to 82 are clearly corrupt, so we can trust anything that it reports. We can't draw any conclusions from the |
@agnivade |
I don't have much experience with kubernetes, but since you are using a python client, I believe your stack trace is coming from the kube-agent binary ? Therefore, the issue does not lie in any code you have written. Hence, following that logic, it is an issue with the software and not the programming language it was written in. (Something similar to if you see an issue with nginx, it is likely an issue with nginx and not with C compiler). That does not say it cannot be an issue with Go. It can, but this needs detailed debugging by the kubernetes team or by people having intimate knowledge about it. That's why I suggested to file an issue on the kubernetes repo. |
@agnivade Now I open issue on Go repo rather than kubernetes, because I thank kubernetes should not modify the process stack, and the corrupt stack does not cause the program to crash. |
@ianlancetaylor |
HI @guangyouyu - Did you get any updates from the kubernetes team on this ? Have you tried with 1.10 ? |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version go1.8.3 linux/amd64
Does this issue reproduce with the latest release?
I do not know how to reproduce it. But it occurs triple on different hosts.
What operating system and processor architecture are you using (
go env
)?Linux VM-2-19-ubuntu 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
KVM virtual machine , NUMA
GOARCH="amd64"
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/ubuntu/go"
GOROOT="/opt/go"
GOTOOLDIR="/opt/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build765569602=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
What did you do?
Run Kubelet(Kubernetes agent) ,Create and Delete Container Repeatly
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
What did you expect to see?
The process runs normally.
What did you see instead?
The process is still there but does not respond anymore(and no more logging). When I use curl http://ip:port/debug/pprof/goroutine?debug=1 to check the stack, but it halts. There is nothing useful in stderr or dmesg.(I have core dump but it too big to upload)
i tried gdb it and got following result:
thread,goroutines stack
(Thread 52 (LWP 4987) )sched.stopwait == 1 and stopTheWorldWithSema stuck on
go/src/runtime/proc.go
Line 1029 in 357c914
Thread 6 (LWP 4622) very strange function address
The text was updated successfully, but these errors were encountered: