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

ordhook quited with ERRO: Unable to retrieve backward traversal result for inscription #380

Open
phill-beyond opened this issue Dec 24, 2024 · 1 comment

Comments

@phill-beyond
Copy link

I installed newest version of ordhook and started db syncing, but the program has exited with ERRO: Unable to retrieve backward traversal result for inscription.

$ ordhook --version
ordhook-cli 2.0.0

$ ordhook db sync --config-path=./Ordhook.toml
...
Dec 24 13:30:56.897 INFO Inscriptions data computation for block #774656 collected
Dec 24 13:30:56.897 INFO Inscriptions data computation for block #774656 ended
Dec 24 13:30:56.901 INFO Inscription aa52bf43287c659995296fe23a4c6e094f709b256f451509a1dbf294f034167fi0 (#674) detected on Satoshi 1023999480461557 (block #774656, 205 transfers)
Dec 24 13:30:56.901 ERRO Unable to retrieve backward traversal result for inscription 0x7805eb9d8552a595f43a9c110f3e386e40c88fddf0934e92b2ce69403542f4ff

@tegaget
Copy link

tegaget commented Jan 14, 2025

I get this sometimes. I was never able to conclusively determine what causes this error. However, after prolonged running, it seems to turn up when the memory resources get high on this service. Memory slowly climbs beyond reasonable limits. I restart the ordhook service approximately every week.

Usually, the error happens and corrupts my db. Fortunately, I have snapshot backups so I do not need to resync entire db from scratch. The error corrects itself if syncing before the "retrieve backward traversal" error happened on the specific block. If I restart ordhook service without retoring db, it does not seem to be able to get past the error.

I restore both the horde.rocksdb folder and the horde.sqlite
This method has never failed me yet.

As a preventative measure, as I mentioned, I restart the service before the memory resources get too high. Not sure if there is a memory leak or logic to use as much RAM as possible. I have had my kernel forcefully close ordhook because of too much RAM being used.

My current Ordhook.toml section for resources is:

[resources]
ulimit = 2048
cpu_core_available = 4
memory_available = 20
bitcoind_rpc_threads = 4
bitcoind_rpc_timeout = 15
expected_observers_count = 1

Hope some of this helps. Frustrating error to say the least.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants