You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
Running
ordhook db sync --config-path=./Ordhook.toml
Seems to get stuck after a few thousand blocks. It outputs like below :
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
The text was updated successfully, but these errors were encountered: