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

[panic] restart pouchd with the newest code panic #1421

Closed
HusterWan opened this issue May 27, 2018 · 1 comment · Fixed by #1422
Closed

[panic] restart pouchd with the newest code panic #1421

HusterWan opened this issue May 27, 2018 · 1 comment · Fixed by #1422
Labels
kind/panic priority/P1 this is high priority that all maintainers should stop to handle this issue

Comments

@HusterWan
Copy link
Contributor

Ⅰ. Issue Description

when i restart pouchd, i got panic error:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x48 pc=0x17d2e14]

goroutine 47 [running]:
github.com/alibaba/pouch/daemon/mgr.(*ContainerManager).markStoppedAndRelease(0xc4200e03f0, 0xc4203a6000, 0x0, 0x1, 0x1)
	/tmp/pouchbuild/src/github.com/alibaba/pouch/daemon/mgr/container.go:1643 +0x324
github.com/alibaba/pouch/daemon/mgr.(*ContainerManager).Restore.func1(0x26b4a40, 0xc4203a6000, 0x9b6, 0x1c12bc0)
	/tmp/pouchbuild/src/github.com/alibaba/pouch/daemon/mgr/container.go:212 +0x5cf
github.com/alibaba/pouch/pkg/meta.(*Store).ForEach(0xc420297020, 0xc420288d00, 0xc420561cb0, 0xc420561ca0)
	/tmp/pouchbuild/src/github.com/alibaba/pouch/pkg/meta/store.go:197 +0x1e9
github.com/alibaba/pouch/daemon/mgr.(*ContainerManager).Restore(0xc4200e03f0, 0x26c9280, 0xc4201e6240, 0x1, 0xc4202fa990)
	/tmp/pouchbuild/src/github.com/alibaba/pouch/daemon/mgr/container.go:224 +0x8f
github.com/alibaba/pouch/daemon/mgr.NewContainerManager(0x26c9280, 0xc4201e6240, 0xc420297020, 0x26d34e0, 0xc420390140, 0x26ce480, 0xc4201e62c0, 0x26ce4e0, 0xc42000e0a0, 0x271a960, ...)
	/tmp/pouchbuild/src/github.com/alibaba/pouch/daemon/mgr/container.go:179 +0x509
github.com/alibaba/pouch/internal.GenContainerMgr(0x26c9280, 0xc4201e6240, 0x26cee40, 0xc420341540, 0xc42000e0a0, 0x0, 0x0, 0x0)
	/tmp/pouchbuild/src/github.com/alibaba/pouch/internal/generator.go:28 +0x1c7
github.com/alibaba/pouch/daemon.(*Daemon).Run(0xc420341540, 0x0, 0x0)
	/tmp/pouchbuild/src/github.com/alibaba/pouch/daemon/daemon.go:166 +0x22b
main.runDaemon.func2(0xc420296f00, 0xc420341540)
	/tmp/pouchbuild/src/github.com/alibaba/pouch/main.go:202 +0x2b
created by main.runDaemon
	/tmp/pouchbuild/src/github.com/alibaba/pouch/main.go:200 +0x5aa
  • how to replay the panic
    • first run a container
    root@osboxes:wanziren -> pouch ps
    Name       ID       Status         Created      Image                                       Runtime
    for-test   9d123f   Up 4 seconds   6 days ago   reg.docker.alibaba-inc.com/busybox:latest   runc
    
    • stop pouchd and kill the container process
    • start pouchd, now you can get the same panic error

Ⅱ. Describe what happened

Ⅲ. Describe what you expected to happen

Ⅳ. How to reproduce it (as minimally and precisely as possible)

Ⅴ. Anything else we need to know?

Ⅵ. Environment:

  • pouch version (use pouch version):
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:
@pouchrobot pouchrobot added kind/panic priority/P1 this is high priority that all maintainers should stop to handle this issue labels May 27, 2018
@pouchrobot
Copy link
Collaborator

Thanks for your report, @HusterWan
😱 This is a priority/P1 issue which is highest.
Seems to be severe enough.
ping @alibaba/pouch , PTAL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/panic priority/P1 this is high priority that all maintainers should stop to handle this issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants