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

runehook indexing services stops after catching up to the latest block. #45

Open
phill-beyond opened this issue Dec 24, 2024 · 4 comments
Assignees

Comments

@phill-beyond
Copy link

Describe the bug
runehook indexing services stops after catching up to the latest block. Need to restart the process to start the indexing again.

To Reproduce
Steps to reproduce the behavior:
1, start process:
$ runehook service start --config-path Runehook.toml
...
Dec 24 21:02:07.618 INFO Edict DOG•GO•TO•THE•MOON 2399060302 tx: 0xf8216655b88a409d9927eb72a164ae55623d0e8de9202261a5e3ca52fd5e7424 (3627) @876206
Dec 24 21:02:07.633 INFO Flushing DB cache...
Dec 24 21:02:07.633 DEBG Flushing 5 supply changes
Dec 24 21:02:07.810 DEBG Flushing 22 ledger entries
Dec 24 21:02:07.812 DEBG Flushing 9 balance increases
Dec 24 21:02:08.060 DEBG Flushing 8 balance deductions
Dec 24 21:02:08.264 INFO Block 876206 indexed in 15.12s
Dec 24 21:02:08.286 INFO 1 blocks scanned, 1 actions triggered
Dec 24 21:02:08.291 INFO Caught up to bitcoind chain tip at 876206
Dec 24 21:02:08.293 INFO Listening for new blocks via Chainhook SDK
Dec 24 21:02:08.297 INFO Connecting to postgres at localhost:5432

2, After the process caught up to 876206 the indexing stopped. And I see the current block height reached 876,214 already.
I need to kill the process and start the process again to catch up to the newest block.

Expected behavior
I expect the runehook service can listen to the newest block and keep the indexing process going.

@GregorWedlich
Copy link

Hey! The problem is that after picking up the last block we close the loop by returning. I have changed it so that we always have to look after 60 seconds to see if there is a new block available.

My fix:
GregorWedlich@852c9d6

@phill-beyond
Copy link
Author

Thank you for the fix. I am trying it out.

@rafaelcr
Copy link
Collaborator

@phill-beyond are you sure you have the zeromq interface correctly enabled on your Bitcoin node? runehook switches to zeromq when it reaches the chain tip so it can start listening for new blocks as they come. Sounds like this is not working correctly in your setup

@rafaelcr rafaelcr self-assigned this Jan 21, 2025
@rafaelcr rafaelcr moved this from 🆕 New to 📋 Backlog in Ordinals Jan 21, 2025
@GregorWedlich
Copy link

I think zeromq is not intergrated by design in bitcoin node?

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

No branches or pull requests

3 participants