I followed the guide to convert from bitcoin core to knots, and all seems to have worked well.
Bitcoin Knots shows as running and no issues, however, Electrs does not seem to finish Starting, and the same with LND.
LND Logs are just filled with: Waiting for bitcoin RPC…
Electrs Logs also repeats the same thing:
2025-05-09T10:09:55+02:00 Starting electrs 0.10.9 on aarch64 linux with Config { network: Bitcoin, db_path: “./db/bitcoin”, db_log_dir: None, db_parallelism: 1, daemon_auth: UserPass(“bitcoin”, “”), daemon_rpc_addr: 172.18.0.3:8332, daemon_p2p_addr: 172.18.0.3:8333, electrum_rpc_addr: 0.0.0.0:50001, monitoring_addr: 127.0.0.1:4224, wait_duration: 10s, jsonrpc_timeout: 15s, index_batch_size: 10, index_lookup_limit: None, reindex_last_blocks: 0, auto_reindex: true, ignore_mempool: false, sync_once: false, skip_block_download_wait: false, disable_electrum_rpc: false, server_banner: “Welcome to electrs 0.10.9 (Electrum Rust Server)!”, signet_magic: f9beb4d9 }
2025-05-09T10:09:55+02:00 [2025-05-09T08:09:55.082Z INFO electrs::metrics::metrics_impl] serving Prometheus metrics on 127.0.0.1:4224
2025-05-09T10:09:55+02:00 [2025-05-09T08:09:55.082Z INFO electrs::server] serving Electrum RPC on 0.0.0.0:50001
2025-05-09T10:09:55+02:00 [2025-05-09T08:09:55.362Z INFO electrs::db] “./db/bitcoin”: 233 SST files, 54.178796191 GB, 6.754006971 Grows
2025-05-09T10:09:57+02:00 thread ‘main’ panicked at src/db.rs:408:39:
2025-05-09T10:09:57+02:00 DB scan failed: Error { message: “IO error: While pread offset 20819968 len 3269: ./db/bitcoin/226372.sst: Input/output error” }
2025-05-09T10:09:57+02:00 note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
2025-05-09T10:09:57+02:00 [2025-05-09T08:09:57.394Z INFO electrs::db] closing DB at ./db/bitcoin
This goes on over and over.
How can I fix this? Any ideas? Do I need to change any settings in these now that I ‘downgraded’ core to knots?
I’d check if there’s a corresponding error in Knots logs that shows Electrs failing to connect. (If so, open config on Electrs and hit save)
Ultimately Electrs is not a huge deal, depending on hardware it’s easy to sync it again if you want to remove it and reinstall rather than troubleshoot.
It seems that only worked for a few days. I did have a storm come through and cause some issues where this DIY server wouldn’t boot up correctly. Now it does boot up, but still not starting everything. Doesn’t give an error, just reloads and tries again for Bitcoin Knots, and the other services. @StuPleb I tried doing what you mentioned again, as well as restart Start9, but doesn’t seem to fix it this time.
There will be an error in the logs. The logs are found in Bitcoin Knots → Logs. The error will tell you what the issue is.
Hopefully you haven’t damaged the drive from the storm… I assume the server is unprotected? With Knots the action under Bitcoin Knots → Actions are more limited that those of Core, so you might have to just suck it up and reindex, depending on the error.
@StuPleb , here is some of the logs. I saw "Please restart with -reindex or -reindex-chainstate to recover.
I saw something along those lines in the GUI for reindexing. Is that what I need to do? Or does that mean launch knots like: bitcoin-knots -reindex ?
Some Errors
2025-06-20T08:03:41-05:00 : Error initializing block database.
2025-06-20T08:03:41-05:00 Please restart with -reindex or -reindex-chainstate to recover.
Some warnings:
WARNING: the RPC server is not safe to expose to untrusted networks such as the public internet
2025-06-20T08:03:34-05:00 2025-06-20T13:03:34Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation.