Umbrel Bitcoin Node Synchronized No Blocks Showing

Hi, my Raspberry Pi 4 Umbrel was shutdown several times due to a power outage. After successfully starting Umbrel, Bitcoin Node App opens but no blocks show. Status is Synchronized. Connections
Mempool Hashrate Blockchain Size flashing blank.
Blockchain SizeUmbrel Version 0.5.1. Is the node bootstrapping? Troubleshoot report states no automatically detected issues.
Electrum server app states: Electrs

Waiting for Bitcoin Node to finish syncing…

bitcoin

tor_server_1 | Sep 20 06:09:38.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
server_1 | at ClientRequest. (/app/node_modules/bitcoind-rpc/lib/index.js:116:7)
tor_server_1 | Sep 20 06:09:39.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_server_1 | Sep 20 06:09:39.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_server_1 | Sep 20 06:09:40.000 [notice] Bootstrapped 100% (done): Done
server_1 | at ClientRequest.emit (events.js:314:20)
server_1 | at Socket.socketErrorListener (_http_client.js:427:9)
server_1 | at Socket.emit (events.js:314:20)
server_1 | at emitErrorNT (internal/streams/destroy.js:92:8)
server_1 | at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
server_1 | at /app/node_modules/async-listener/glue.js:188:31
server_1 | at processTicksAndRejections (internal/process/task_queues.js:84:21)
server_1 | ::ffff:10.21.0.5 - - [Tue, 20 Sep 2022 06:11:46 GMT] “GET /v1/bitcoind/info/stats HTTP/1.1” 500 34 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/105.0.0.0 Safari/537.36 Edg/105.0.1343.42”
server_1 |
server_1 | umbrel-middleware
server_1 | Unable to obtain peer info
server_1 | /v1/bitcoind/info/sync
server_1 | BitcoindError: Unable to obtain peer info
server_1 | at /app/services/bitcoind.js:24:18
server_1 | at ClientRequest. (/app/node_modules/bitcoind-rpc/lib/index.js:116:7)
server_1 | at ClientRequest.emit (events.js:314:20)
server_1 | at Socket.socketErrorListener (_http_client.js:427:9)
server_1 | at Socket.emit (events.js:314:20)
server_1 | at emitErrorNT (internal/streams/destroy.js:92:8)
server_1 | at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
server_1 | at /app/node_modules/async-listener/glue.js:188:31
server_1 | at processTicksAndRejections (internal/process/task_queues.js:84:21)
server_1 | ::ffff:10.21.0.5 - - [Tue, 20 Sep 2022 06:11:49 GMT] “GET /v1/bitcoind/info/sync HTTP/1.1” 500 28 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/105.0.0.0 Safari/537.36 Edg/105.0.1343.42”
server_1 |
server_1 | umbrel-middleware

Hey @svetlyoh! Could you provide the full troubleshooting logs?
You can get it in your Dashboard > Settings > Troubleshoot
Could you also provide the output of the docker ps command?
You can get it by connecting to your machine using a Terminal and typing:
ssh -t umbrel@umbrel.local "docker ps"
You can also know where you are in your bitcoin syncing process by taking a look at the bitcoin logs using:
ssh -t umbrel@umbrel.local "tail -n 100 ~/umbrel/app-data/bitcoin/data/bitcoin/debug.log"

Output from docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
aeb531d052e6 bluewalletorganization/lndhub:v1.4.1 “docker-entrypoin t.s…” 4 hours ago Restarting (4) 2 seconds ago bluewallet_lndhub_1
d809f282b1a4 getumbrel/umbrel-electrs:v1.0.2 “docker-entrypoin t.s…” 4 hours ago Up 4 hours 3006/tcp electrs_app_1
c364dcd53500 getumbrel/umbrel-bitcoin:v0.3.0 “docker-entrypoin t.s…” 4 hours ago Up 4 hours 3006/tcp bitcoin_server_1
340f26a80b43 lncm/tor:0.4.7.8 “tor” 4 hours ago Up 4 hours 9050-9051/tcp, 29050-29051 /tcp lightning-terminal_tor_server_1
983f70cad678 lncm/tor:0.4.7.8 “tor” 4 hours ago Up 4 hours 9050-9051/tcp, 29050-29051 /tcp bluewallet_tor_server_1
e81f2931cb4a getumbrel/app-proxy:v0.5.1 “docker-entrypoin t.s…” 4 hours ago Up 4 hours 0.0.0.0:3008->3008/tcp, :: :3008->3008/tcp bluewallet_app_proxy_1
aa18756cf69d redis:6.2.2-buster “docker-entrypoin t.s…” 4 hours ago Up 4 hours 6379/tcp bluewallet_redis_1
e815c67a12c1 getumbrel/app-proxy:v0.5.1 “docker-entrypoin t.s…” 4 hours ago Up 4 hours 0.0.0.0:3004->3004/tcp, :: :3004->3004/tcp lightning-terminal_app_proxy_1
cd11c6dea077 lightninglabs/lightning-terminal:v0.8.0-alpha “litd --uipasswor d_e…” 4 hours ago Up 4 hours 8443/tcp, 9735/tcp, 10009/ tcp lightning-terminal_web_1
25520d9f2c67 lncm/tor:0.4.7.8 “tor” 4 hours ago Up 4 hours 9050-9051/tcp, 29050-29051 /tcp lightning_tor_server_1
d6c4810186ae getumbrel/app-proxy:v0.5.1 “docker-entrypoin t.s…” 4 hours ago Up 4 hours 0.0.0.0:2101->2101/tcp, :: :2101->2101/tcp lightning_app_proxy_1
429eef929915 getumbrel/umbrel-lightning:v1.0.4 “docker-entrypoin t.s…” 4 hours ago Up 4 hours 3006/tcp lightning_app_1
7b86d6b9a01e lightninglabs/lnd:v0.15.1-beta “lnd --listen=0.0 .0.…” 4 hours ago Up 4 hours 0.0.0.0:8080->8080/tcp, :: :8080->8080/tcp, 0.0.0.0:9735->9735/tcp, :::9735->9735/tcp, 0.0.0.0:10009->10009 /tcp, :::10009->10009/tcp lightning_lnd_1
6e866e8a8c8e lncm/tor:0.4.7.8 “tor” 4 hours ago Up 4 hours 9050-9051/tcp, 29050-29051 /tcp electrs_tor_server_1
bee8be44bfd9 getumbrel/app-proxy:v0.5.1 “docker-entrypoin t.s…” 4 hours ago Up 4 hours 0.0.0.0:2102->2102/tcp, :: :2102->2102/tcp electrs_app_proxy_1
bb886072d127 getumbrel/electrs:v0.9.4 “electrs” 4 hours ago Restarting (1) 1 second ago electrs_electrs_1
e7191d629482 lncm/tor:0.4.7.8 “tor” 4 hours ago Up 4 hours 9050-9051/tcp, 29050-29051 /tcp thunderhub_tor_server_1
7013844dbc6f apotdevin/thunderhub:v0.13.15 “docker-entrypoin t.s…” 4 hours ago Up 4 hours 3000/tcp thunderhub_web_1
860a618399a7 getumbrel/app-proxy:v0.5.1 “docker-entrypoin t.s…” 4 hours ago Up 4 hours 0.0.0.0:3000->3000/tcp, :: :3000->3000/tcp thunderhub_app_proxy_1
7628259393a7 lncm/bitcoind:v23.0 “bitcoind -chain= mai…” 4 hours ago Restarting (1) 39 seconds ago bitcoin_bitcoind_1
11e3f7926f71 lncm/tor:0.4.7.8 “tor” 4 hours ago Up 4 hours 9050-9051/tcp, 29050-29051 /tcp bitcoin_tor_server_1
e07173e9361f getumbrel/app-proxy:v0.5.1 “docker-entrypoin t.s…” 4 hours ago Up 4 hours 0.0.0.0:2100->2100/tcp, :: :2100->2100/tcp bitcoin_app_proxy_1
8ff25fd807cf nginx:1.17.8 “nginx -g 'daemon of…” 4 hours ago Up 4 hours 0.0.0.0:80->80/tcp, :::80- >80/tcp nginx
fe76b3a10a2e getumbrel/manager:v0.5.0 “docker-entrypoin t.s…” 4 hours ago Up 4 hours 3006/tcp manager
3310e0c2553e getumbrel/auth-server:v0.5.1 “docker-entrypoin t.s…” 4 hours ago Up 4 hours 0.0.0.0:2000->2000/tcp, :: :2000->2000/tcp auth
bf6f23537089 lncm/tor:0.4.7.8 “tor” 4 hours ago Up 4 hours 9051/tcp, 127.0.0.1:9050-> 9050/tcp, 29050-29051/tcp tor
0d8e833665c9 getumbrel/dashboard:v0.5.4 “docker-entrypoin t.s…” 4 hours ago Up 4 hours 3004/tcp dashboard

Also, there is an error in the peers.dat file. Perhaps that is the only issue now? This makes sense as initial error upon 0.5.1 update was peer connections. Any ideas how to fix this? Thank you.

2022-09-20T11:49:33Z Bitcoin Core version v23.0.0 (release build)
2022-09-20T11:49:33Z InitParameterInteraction: parameter interaction: -proxy set -> setting -upnp=0
2022-09-20T11:49:33Z InitParameterInteraction: parameter interaction: -proxy set -> setting -natpmp=0
2022-09-20T11:49:33Z InitParameterInteraction: parameter interaction: -proxy set -> setting -discover=0
2022-09-20T11:49:33Z Assuming ancestors of block 000000000000000000052d314a259755ca65944e68df6b12a067ea8f1f5a7091 have valid signatures.
2022-09-20T11:49:33Z Setting nMinimumChainWork=00000000000000000000000000000000000000002927cdceccbd5209e81e80db
2022-09-20T11:49:33Z Using the ‘standard’ SHA256 implementation
2022-09-20T11:49:33Z Default data directory /data/.bitcoin
2022-09-20T11:49:33Z Using data directory /data/.bitcoin
2022-09-20T11:49:33Z Config file: /data/.bitcoin/bitcoin.conf
2022-09-20T11:49:33Z Config file arg: reindex=“1”
2022-09-20T11:49:33Z Command-line arg: bind=“0.0.0.0:8334=onion”
2022-09-20T11:49:33Z Command-line arg: bind=“10.21.21.8”
2022-09-20T11:49:33Z Command-line arg: blockfilterindex=“1”
2022-09-20T11:49:33Z Command-line arg: chain=“main”
2022-09-20T11:49:33Z Command-line arg: listen=""
2022-09-20T11:49:33Z Command-line arg: peerblockfilters=“1”
2022-09-20T11:49:33Z Command-line arg: peerbloomfilters=“1”
2022-09-20T11:49:33Z Command-line arg: port=“8333”
2022-09-20T11:49:33Z Command-line arg: proxy=“10.21.21.11:9050”
2022-09-20T11:49:33Z Command-line arg: rpcallowip=“10.21.0.0/16”
2022-09-20T11:49:33Z Command-line arg: rpcallowip=“127.0.0.1”
2022-09-20T11:49:33Z Command-line arg: rpcauth=****
2022-09-20T11:49:33Z Command-line arg: rpcbind=****
2022-09-20T11:49:33Z Command-line arg: rpcbind=****
2022-09-20T11:49:33Z Command-line arg: rpcport=“8332”
2022-09-20T11:49:33Z Command-line arg: rpcworkqueue=“128”
2022-09-20T11:49:33Z Command-line arg: txindex=“1”
2022-09-20T11:49:33Z Command-line arg: zmqpubhashblock=“tcp://0.0.0.0:28334”
2022-09-20T11:49:33Z Command-line arg: zmqpubrawblock=“tcp://0.0.0.0:28332”
2022-09-20T11:49:33Z Command-line arg: zmqpubrawtx=“tcp://0.0.0.0:28333”
2022-09-20T11:49:33Z Command-line arg: zmqpubsequence=“tcp://0.0.0.0:28335”
2022-09-20T11:49:33Z Using at most 125 automatic connections (1048576 file descriptors available)
2022-09-20T11:49:33Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2022-09-20T11:49:33Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2022-09-20T11:49:33Z Script verification uses 3 additional threads
2022-09-20T11:49:33Z scheduler thread start
2022-09-20T11:49:33Z HTTP: creating work queue of depth 128
2022-09-20T11:49:33Z Using random cookie authentication.
2022-09-20T11:49:33Z Generated RPC authentication cookie /data/.bitcoin/.cookie
2022-09-20T11:49:33Z Using rpcauth authentication.
2022-09-20T11:49:33Z HTTP: starting 4 worker threads
2022-09-20T11:49:33Z Using wallet directory /data/.bitcoin
2022-09-20T11:49:33Z init message: Verifying wallet(s)…
2022-09-20T11:49:33Z Using /16 prefix for IP bucketing
2022-09-20T11:49:33Z init message: Loading P2P addresses…
2022-09-20T11:49:35Z Error: Invalid or corrupt peers.dat (Checksum mismatch, data corrupted). If you believe this is a bug, please report it to https://github.com/bitcoin/bitcoin/issues. As a workaround, you can move the file ("/data/.bitcoin/peers.dat") out of the way (rename, move, or delete ) to have a new one created on the next start.
2022-09-20T11:49:35Z Shutdown: In progress…
2022-09-20T11:49:35Z scheduler thread exit
2022-09-20T11:49:35Z Shutdown: done

Spotted on! It seems that the problem comes from the peers.dat file.
You can erase/rename the peers.dat file so that bitcoin recreates a new one
First of all, you’ll need to stop the bitcoin app:
sudo ~/umbrel/scripts/app/stop bitcoin
then remove the faulty file:
rm ~/umbrel/app-data/bitcoin/data/bitcoin/peers.dat

(in the case you want to keep a trace of the faulty file you can rename it) :
mv ~/umbrel/app-data/bitcoin/data/bitcoin/peers.dat ~/umbrel/app-data/bitcoin/data/bitcoin/peers.dat.bad

Then you can restart the bitcoin app using :
sudo ~/umbrel/scripts/app/start bitcoin

Tell us if the Bitcoin app UI is back to normal after that :pray:

Thank you once again! Just one more question. I have lightning channels. Will deleting the peers.dat file somehow impact the lightning channels (each associated with a peer)? I will keep a copy of the current peers.dat file of course.

Sorry for the delay ! Don’t worry, the peers.dat is only related to bitcoin core it does not contain the lightning peers.
The peers.dat file contains a database of peers and is used by bitcoin core to establish connections.