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

db sync gets stuck #232

Closed
GuutBoy opened this issue Dec 15, 2023 · 2 comments
Closed

db sync gets stuck #232

GuutBoy opened this issue Dec 15, 2023 · 2 comments

Comments

@GuutBoy
Copy link

GuutBoy commented Dec 15, 2023

Running ordhook db sync --config-path=./Ordhook.toml

Seems to get stuck after a few thousand blocks. It outputs like below :

....
Dec 15 10:56:47.970 INFO Block #50072 saved to disk
Dec 15 10:56:47.970 INFO Block #50088 saved to disk
Dec 15 10:56:47.970 INFO Block #50104 saved to disk
Dec 15 10:56:47.970 INFO Block #50120 saved to disk
Dec 15 10:56:47.970 INFO Block #50136 saved to disk
Dec 15 10:56:47.970 INFO Block #50152 saved to disk
Dec 15 10:56:47.971 INFO Block #50167 saved to disk
Dec 15 10:56:47.971 INFO Block #50183 saved to disk
Dec 15 10:56:47.971 INFO Block #50200 saved to disk

But then does not proceed.

I also see this line being output which may be a related problem:

thread 'Block data compression' panicked at 'called `Option::unwrap()` on a `None` value', components/ordhook-core/src/db/mod.rs:1583:59

@4ker-dep
Copy link

4ker-dep commented Dec 15, 2023

You probably need to upgrade your bitcoin core to a newer version that supports RPC method 'getblock' with verbosity with the value of 3. It should work with at least v25 or higher.

@GuutBoy
Copy link
Author

GuutBoy commented Dec 15, 2023

Upgrading to at least v25 seems to have solved this. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants