Service stops automatically - First time setup

[chetanbothra]

Hi Team,

we are trying this setup for the first time.

So we got the setup done successfully, bitcoind is also working and synced successfully
ordhook scan blocks --interval 767430:767753 --mainnet is able to give results too

Ordhook.toml looks like this

[storage]
working_dir = "ordhook"

# The Http Api allows you to register / deregister
# dynamically predicates.
# Disable by default.
#
[http_api]
http_port = 20456

[limits]
max_number_of_bitcoin_predicates = 100
max_number_of_concurrent_bitcoin_scans = 100
max_number_of_processing_threads = 16
bitcoin_concurrent_http_requests_max = 16
max_caching_memory_size_mb = 32000

[network]
mode = "mainnet"
bitcoind_rpc_url = "http://0.0.0.0:8332"
bitcoind_rpc_username = "devnet"
bitcoind_rpc_password = "devnet"
# Bitcoin block events can be received by Chainhook
# either through a Bitcoin node's ZeroMQ interface,
# or through the Stacks node. Zmq is being
# used by default:
bitcoind_zmq_url = "tcp://0.0.0.0:18543"
# but stacks can also be used:
# stacks_node_rpc_url = "http://0.0.0.0:20443"

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

# Disable the following section if the state
# must be built locally
[snapshot]
download_url = "https://archive.hiro.so/mainnet/ordhook/mainnet-ordhook-sqlite-latest.tar.gz"

[logs]
ordinals_internals = true
chainhook_internals = true

OS: ubuntu
Ram : 64GB
CPU : 32core

Problem statement : when we run ordhook service start --config-path=./Ordhook.toml we get few successfully statement and then the process ends,

example of the error

Jun 07 04:35:23.489 INFO Starting service (git_commit = 420579b)...
Jun 07 04:35:23.565 INFO Indexing inscriptions from block #843803 to block #846837
Jun 07 04:35:26.680 INFO Processing 3 blocks
Jun 07 04:35:26.680 INFO Inscriptions data computation for block #843803 started
Jun 07 04:35:26.682 INFO Number of inscriptions in block #843803 to process: 173 (L1 cache hits: 0, queue: [843804, 843805], L1 cache len: 0, L2 cache len: 0)
Jun 07 04:35:27.158 INFO Completed ordinal number retrieval for Satpoint 0x53fbe9fb97cb1bd59d0a2d4a4a15ad255832673ed0c07d07ab2e49b5be58e229:0:0 (block: #840714:268867126, transfers: 13, progress: 1/173, priority queue: true, thread: 7)
.
.
.
.
.
.
Jun 07 04:36:07.217 ERRO Unable to compute inscription's Satoshi: block #842738 not in database (traversing 0x394a1306aa8c36941d38872be940f6c5fad6174f265f6a891deca7fd9675078f / 843803 in progress)
Jun 07 04:36:07.217 INFO Inscriptions data computation for block #843803 collected
Jun 07 04:36:07.217 INFO Inscriptions data computation for block #843803 ended
Jun 07 04:36:07.224 ERRO Unable to retrieve backward traversal result for inscription 0x394a1306aa8c36941d38872be940f6c5fad6174f265f6a891deca7fd9675078f

please advice if Is this service expected to run forever ? or why is it getting terminated in middle due to some other error

[rafaelcr]

Hi @chetanbothra , you might have the same problem as this other issue: #334
If your chainstate is corrupted, you can download a new one from our archives and try again. Can you do that and let me know if it works?

[andresgalante]

@chetanbothra I'll close it and you can reopen it if you have questions