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

[BUG] Panic, when I set LOTUS_ENABLE_CHAINSTORE_FALLBACK=1 env and start lotus daemon #6137

Closed
donnol opened this issue Apr 29, 2021 · 4 comments
Labels
kind/bug Kind: Bug

Comments

@donnol
Copy link

donnol commented Apr 29, 2021

Note: For security-related bugs/issues, please follow the security policy.

Describe the bug

Panic, when I set LOTUS_ENABLE_CHAINSTORE_FALLBACK=1 env and start lotus daemon

Version (run lotus version):

Daemon: 1.8.0+mainnet+git.5014d71f+api1.2.0
Local: lotus version 1.8.0+mainnet+git.5014d71f

To Reproduce
Steps to reproduce the behavior:

  1. Run '...'
  2. See error

Expected behavior
lotus daemon run normally

Logs

runtime: goroutine stack exceeds 1000000000-byte limit
runtime: sp=0xc035280398 stack=[0xc035280000, 0xc055280000]
fatal error: stack overflow

runtime stack:
runtime.throw(0x30df25b, 0xe)
/usr/local/go/src/runtime/panic.go:1116 +0x72
runtime.newstack()
/usr/local/go/src/runtime/stack.go:1067 +0x78d
runtime.morestack()
/usr/local/go/src/runtime/asm_amd64.s:449 +0x8f

goroutine 1 [running]:
go.uber.org/dig.(*Container).getProviders(0xc00118d4f0, 0x3575a60, 0x2e7ef80, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
/go/pkg/mod/go.uber.org/dig@v1.10.0/dig.go:340 +0x114 fp=0xc0352803a8 sp=0xc0352803a0 pc=0x14e8794
go.uber.org/dig.(*Container).getValueProviders(0xc00118d4f0, 0x0, 0x0, 0x3575a60, 0x2e7ef80, 0x0, 0x0, 0x0)
/go/pkg/mod/go.uber.org/dig@v1.10.0/dig.go:333 +0xa5 fp=0xc035280438 sp=0xc0352803a8 pc=0x14e8525
go.uber.org/dig.shallowCheckDependencies.func1(0x353bd00, 0xc001523a10, 0x0)
/go/pkg/mod/go.uber.org/dig@v1.10.0/dig.go:749 +0x113 fp=0xc0352805a8 sp=0xc035280438 pc=0x14f93d3
go.uber.org/dig.paramVisitorFunc.Visit(0xc0151d42a0, 0x353bd00, 0xc001523a10, 0x0, 0x0)
/go/pkg/mod/go.uber.org/dig@v1.10.0/param.go:102 +0x3a fp=0xc0352805d0 sp=0xc0352805a8 pc=0x14f0a7a
go.uber.org/dig.walkParam(0x353bd00, 0xc001523a10, 0x3508740, 0xc0151d42a0)
/go/pkg/mod/go.uber.org/dig@v1.10.0/param.go:117 +0x66 fp=0xc0352806e8 sp=0xc0352805d0 pc=0x14f0b26
go.uber.org/dig.walkParam(0x353bc80, 0xc0151d4270, 0x3508740, 0xc0151d42a0)
/go/pkg/mod/go.uber.org/dig@v1.10.0/param.go:131 +0x153 fp=0xc035280800 sp=0xc0352806e8 pc=0x14f0c13
go.uber.org/dig.shallowCheckDependencies(0x355f800, 0xc00118d4f0, 0x353bc80, 0xc0151d4270, 0xf9b5a0a1a889dd01, 0xc0352808a8)
/go/pkg/mod/go.uber.org/dig@v1.10.0/dig.go:743 +0xce fp=0xc035280840 sp=0xc035280800 pc=0x14ebaae
go.uber.org/dig.(*node).Call(0xc001130780, 0x355f800, 0xc00118d4f0, 0x3575a60, 0x2e7ef80)
/go/pkg/mod/go.uber.org/dig@v1.10.0/dig.go:694 +0x7d fp=0xc0352809b8 sp=0xc035280840 pc=0x14eb0fd
go.uber.org/dig.paramSingle.Build(0x0, 0x0, 0x0, 0x3575a60, 0x2e7ef80, 0x355f800, 0xc00118d4f0, 0x1, 0x1, 0x7f9ada7727d0, ...)
/go/pkg/mod/go.uber.org/dig@v1.10.0/param.go:245 +0x2e2 fp=0xc035280ae8 sp=0xc0352809b8 pc=0x14f1aa2
go.uber.org/dig.(*paramSingle).Build(0xc001523a10, 0x355f800, 0xc00118d4f0, 0xc0151d2fa0, 0xc0151d4240, 0xc035280be8, 0x14ebaae, 0x353bc80)

Screenshots

Additional context

@donnol
Copy link
Author

donnol commented Apr 29, 2021

I find the commit, fix the problem, but I can't find it on the v1.8.0 lotus.

So what is the plan?

@jennijuju
Copy link
Member

I find the commit, fix the problem, but I can't find it on the v1.8.0 lotus.

So what is the plan?

You can update to v1.9.0-rc1

@donnol
Copy link
Author

donnol commented Apr 29, 2021

@jennijuju Thanks. I will try it.

@donnol
Copy link
Author

donnol commented May 6, 2021

@jennijuju I run the lotus daemon on v1.9.0-rc1 with LOTUS_ENABLE_CHAINSTORE_FALLBACK=1. But I still got the error: failed to load miner actor: load state tree: failed to load state tree: failed to load hamt node: blockstore: block not found after many times trys. Is there something I miss?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Kind: Bug
Projects
None yet
Development

No branches or pull requests

3 participants