Closed Ericalvin closed 3 months ago
Hi everyone,
At present, I have observed that the log of the electrs service stops at the following point. Should I wait for it or is there any other way to deal with it? btw, I have restarted once, but it got stuck on the same message.
Many thanks.
3月 05 02:27:53 ip-10-218-25-51.us-west-2.compute.internal cargo[16977]: TRACE - downloading 100000 block headers 3月 05 02:27:57 ip-10-218-25-51.us-west-2.compute.internal cargo[16977]: TRACE - downloading 100000 block headers 3月 05 02:28:01 ip-10-218-25-51.us-west-2.compute.internal cargo[16977]: TRACE - downloading 100000 block headers 3月 05 02:28:05 ip-10-218-25-51.us-west-2.compute.internal cargo[16977]: TRACE - downloading 100000 block headers 3月 05 02:28:09 ip-10-218-25-51.us-west-2.compute.internal cargo[16977]: TRACE - downloading 100000 block headers 3月 05 02:28:12 ip-10-218-25-51.us-west-2.compute.internal cargo[16977]: TRACE - downloading 100000 block headers 3月 05 02:28:16 ip-10-218-25-51.us-west-2.compute.internal cargo[16977]: TRACE - downloading 100000 block headers 3月 05 02:28:19 ip-10-218-25-51.us-west-2.compute.internal cargo[16977]: TRACE - downloading 33182 block headers 3月 05 02:28:23 ip-10-218-25-51.us-west-2.compute.internal cargo[16977]: INFO - best=00000000000000000001aa740ede7df517a2371d2293cf59d7af69debf83745d height=833181 @ 2024-03-05T02:12:35Z (833182 left to process) 3月 05 02:28:23 ip-10-218-25-51.us-west-2.compute.internal cargo[16977]: DEBUG - adding transactions from 29 blocks using Bitcoind 3月 05 02:28:23 ip-10-218-25-51.us-west-2.compute.internal cargo[16977]: DEBUG - best=00000000000000000001aa740ede7df517a2371d2293cf59d7af69debf83745d height=833181 @ 2024-03-05T02:12:35Z (29 new blocks to fetch) 3月 05 02:28:27 ip-10-218-25-51.us-west-2.compute.internal cargo[16977]: DEBUG - writing 384875 rows to RocksDB { path: "./db/mainnet/newindex/txstore" }, flush=Disable 3月 05 02:28:28 ip-10-218-25-51.us-west-2.compute.internal cargo[16977]: DEBUG - indexing history from 29 blocks using Bitcoind 3月 05 02:28:28 ip-10-218-25-51.us-west-2.compute.internal cargo[16977]: DEBUG - best=00000000000000000001aa740ede7df517a2371d2293cf59d7af69debf83745d height=833181 @ 2024-03-05T02:12:35Z (29 new blocks to fetch) 3月 05 02:28:49 ip-10-218-25-51.us-west-2.compute.internal cargo[16977]: DEBUG - writing 592262 rows to RocksDB { path: "./db/mainnet/newindex/history" }, flush=Disable 3月 05 02:28:50 ip-10-218-25-51.us-west-2.compute.internal cargo[16977]: DEBUG - applying 833182 new headers from height 0 3月 05 02:28:50 ip-10-218-25-51.us-west-2.compute.internal cargo[16977]: DEBUG - writing 0 rows to RocksDB { path: "./db/mainnet/newindex/txstore" }, flush=Enable 3月 05 02:28:50 ip-10-218-25-51.us-west-2.compute.internal cargo[16977]: DEBUG - writing 0 rows to RocksDB { path: "./db/mainnet/newindex/history" }, flush=Enable
config:
ExecStart=/home/bitcoin/.cargo/bin/cargo run --release --bin electrs -- -vvvv --daemon-dir /home/bitcoin/bitcoind --http-addr 0.0.0.0:3000 --tx-cache-size 100000 --index-batch-size 1000 --bulk-index-threads 14 --precache-scripts ./contrib/popular-scripts.txt
Since you are using --precache-scripts, it seems that you are using one of the electrs forks (#967).
--precache-scripts
Hi everyone,
At present, I have observed that the log of the electrs service stops at the following point. Should I wait for it or is there any other way to deal with it? btw, I have restarted once, but it got stuck on the same message.
Many thanks.
config: