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

Chain sync crash #204

Closed
pcfreak30 opened this issue Dec 13, 2024 · 2 comments · Fixed by #205
Closed

Chain sync crash #204

pcfreak30 opened this issue Dec 13, 2024 · 2 comments · Fixed by #205
Labels
bug Something isn't working

Comments

@pcfreak30
Copy link

Current Behavior

2024-12-13T05:26:32-05:00	INFO	node started	{"syncer": "[::]:9981", "http": "127.0.0.1:9980", "version": "v0.8.0", "commit": "e549203"}
2024-12-13T05:26:32-05:00	PANIC	wallet.sync	failed to sync store	{"error": "failed to subscribe to chain manager: missing block at index 490977::f9b2ba46"}
panic: failed to sync store

goroutine 55 [running]:
go.uber.org/zap/zapcore.CheckWriteAction.OnWrite(0x1?, 0x1?, {0x0?, 0x0?, 0xc00038e080?})
	go.uber.org/[email protected]/zapcore/entry.go:196 +0x54
go.uber.org/zap/zapcore.(*CheckedEntry).Write(0xc0003b01a0, {0xc0003ac040, 0x1, 0x1})
	go.uber.org/[email protected]/zapcore/entry.go:262 +0x24e
go.uber.org/zap.(*Logger).Panic(0x1bcb0c0?, {0xb32c43?, 0x1bcb060?}, {0xc0003ac040, 0x1, 0x1})
	go.uber.org/[email protected]/logger.go:285 +0x51
go.sia.tech/walletd/wallet.NewManager.func2()
	go.sia.tech/walletd/wallet/manager.go:386 +0x653
created by go.sia.tech/walletd/wallet.NewManager in goroutine 1
	go.sia.tech/walletd/wallet/manager.go:363 +0x399

So far I have found it is likely in the sqlite db itself, which is problematic as I cant just delete that without re-importing all accounts. Deleting the consensus db helps none.

Expected Behavior

Walletd to boot normally with my data

Steps to Reproduce

No response

Version

v0.12.2

What operating system did the problem occur on (e.g. Ubuntu 22.04, macOS 12.0, Windows 11)?

Linux Mint

Anything else?

No response

@pcfreak30 pcfreak30 added the bug Something isn't working label Dec 13, 2024
@n8maninger
Copy link
Member

Was there a different panic before you deleted your consensus db?

@pcfreak30
Copy link
Author

no, not that im aware of. before this panic I was having issues with #202.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants