Error: Invalid or corrupt peers.dat file

bitcoind container keeps restarting, container log shows:

2022-09-09T09:50:46Z Bitcoin Core version v23.0.0 (release build)
2022-09-09T09:50:46Z InitParameterInteraction: parameter interaction: -proxy set -> setting -upnp=0
2022-09-09T09:50:46Z InitParameterInteraction: parameter interaction: -proxy set -> setting -natpmp=0
2022-09-09T09:50:46Z InitParameterInteraction: parameter interaction: -proxy set -> setting -discover=0
2022-09-09T09:50:46Z Assuming ancestors of block 000000000000000000052d314a259755ca65944e68df6b12a067ea8f1f5a7091 have valid signatures.
2022-09-09T09:50:46Z Setting nMinimumChainWork=00000000000000000000000000000000000000002927cdceccbd5209e81e80db
2022-09-09T09:50:46Z Using the ‘standard’ SHA256 implementation
2022-09-09T09:50:46Z Default data directory /data/.bitcoin
2022-09-09T09:50:46Z Using data directory /data/.bitcoin
2022-09-09T09:50:46Z Config file: /data/.bitcoin/bitcoin.conf (not found, skipping)
2022-09-09T09:50:46Z Command-line arg: bind=“0.0.0.0:8334=onion”
2022-09-09T09:50:46Z Command-line arg: bind=“10.21.21.8”
2022-09-09T09:50:46Z Command-line arg: blockfilterindex=“1”
2022-09-09T09:50:46Z Command-line arg: chain=“main”
2022-09-09T09:50:46Z Command-line arg: listen=""
2022-09-09T09:50:46Z Command-line arg: peerblockfilters=“1”
2022-09-09T09:50:46Z Command-line arg: peerbloomfilters=“1”
2022-09-09T09:50:46Z Command-line arg: port=“8333”
2022-09-09T09:50:46Z Command-line arg: proxy=“10.21.21.11:9050”
2022-09-09T09:50:46Z Command-line arg: rpcallowip=“10.21.0.0/16”
2022-09-09T09:50:46Z Command-line arg: rpcallowip=“127.0.0.1”
2022-09-09T09:50:46Z Command-line arg: rpcauth=****
2022-09-09T09:50:46Z Command-line arg: rpcbind=****
2022-09-09T09:50:46Z Command-line arg: rpcbind=****
2022-09-09T09:50:46Z Command-line arg: rpcport=“8332”
2022-09-09T09:50:46Z Command-line arg: rpcworkqueue=“128”
2022-09-09T09:50:46Z Command-line arg: txindex=“1”
2022-09-09T09:50:46Z Command-line arg: zmqpubhashblock=“tcp://0.0.0.0:28334”
2022-09-09T09:50:46Z Command-line arg: zmqpubrawblock=“tcp://0.0.0.0:28332”
2022-09-09T09:50:46Z Command-line arg: zmqpubrawtx=“tcp://0.0.0.0:28333”
2022-09-09T09:50:46Z Command-line arg: zmqpubsequence=“tcp://0.0.0.0:28335”
2022-09-09T09:50:46Z Using at most 125 automatic connections (1048576 file descriptors available)
2022-09-09T09:50:46Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2022-09-09T09:50:46Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2022-09-09T09:50:46Z Script verification uses 3 additional threads
2022-09-09T09:50:46Z scheduler thread start
2022-09-09T09:50:46Z HTTP: creating work queue of depth 128
2022-09-09T09:50:46Z Using random cookie authentication.
2022-09-09T09:50:46Z Generated RPC authentication cookie /data/.bitcoin/.cookie
2022-09-09T09:50:46Z Using rpcauth authentication.
2022-09-09T09:50:46Z HTTP: starting 4 worker threads
2022-09-09T09:50:46Z Using wallet directory /data/.bitcoin
2022-09-09T09:50:46Z init message: Verifying wallet(s)…
2022-09-09T09:50:46Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2022-09-09T09:50:46Z Using wallet /data/.bitcoin/wallet.dat
2022-09-09T09:50:46Z BerkeleyEnvironment::Open: LogDir=/data/.bitcoin/database ErrorFile=/data/.bitcoin/db.log
2022-09-09T09:50:46Z Using /16 prefix for IP bucketing
2022-09-09T09:50:46Z init message: Loading P2P addresses…
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-09T09:50:48Z 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-09T09:50:48Z Shutdown: In progress…
2022-09-09T09:50:48Z scheduler thread exit
2022-09-09T09:50:48Z Shutdown: done

=====================

= Umbrel debug info =

Umbrel version

0.5.1

Flashed OS version

v0.2.13

Raspberry Pi Model

Revision : c03111
Serial : 10000000b48aff50
Model : Raspberry Pi 4 Model B Rev 1.1

Firmware

Dec 1 2021 15:01:54
Copyright © 2012 Broadcom
version 71bd3109023a0c8575585ba87cbb374d2eeb038f (clean) (release) (start)

Temperature

temp=44.3’C

Throttling

throttled=0x0

Memory usage

          total        used        free      shared  buff/cache   available

Mem: 3.8G 1.5G 665M 29M 1.6G 2.1G
Swap: 4.1G 0B 4.1G

total: 40.5%
lightning: 16.2%
electrs: 12.8%
nextcloud: 8.8%
btc-rpc-explorer: 6%
bitcoin: 5.9%
ride-the-lightning: 5.7%
lightning-terminal: 4.3%
tailscale: 0.8%
tor: 0.6%
system: 0%
lnd: 0%
electrs: 0%
bitcoin: 0%

Memory monitor logs

2022-09-08 16:26:47 Warning memory usage at 94%
2022-09-08 16:28:03 Warning memory usage at 94%
2022-09-08 16:29:18 Warning memory usage at 94%
2022-09-08 16:30:25 Warning memory usage at 94%
2022-09-08 16:35:02 Memory monitor running!
2022-09-08 17:34:37 Memory monitor running!
2022-09-08 19:17:16 Memory monitor running!
2022-09-08 20:29:50 Memory monitor running!
2022-09-09 06:41:05 Memory monitor running!
2022-09-09 07:52:12 Memory monitor running!

Filesystem information

Filesystem Size Used Avail Use% Mounted on
/dev/root 15G 9.3G 4.4G 68% /
/dev/sda1 880G 550G 286G 66% /home/umbrel/umbrel

Startup service logs

Sep 09 09:38:10 umbrel umbrel startup[1094]: Creating btc-rpc-explorer_web_1 …
Sep 09 09:38:10 umbrel umbrel startup[1094]: Creating btc-rpc-explorer_app_proxy_1 …
Sep 09 09:38:10 umbrel umbrel startup[1094]: Creating lightning-terminal_app_proxy_1 …
Sep 09 09:38:10 umbrel umbrel startup[1094]: Creating electrs_electrs_1 …
Sep 09 09:38:10 umbrel umbrel startup[1094]: Creating electrs_app_proxy_1 …
Sep 09 09:38:10 umbrel umbrel startup[1094]: Creating electrs_tor_server_1 …
Sep 09 09:38:10 umbrel umbrel startup[1094]: Creating lightning-terminal_web_1 …
Sep 09 09:38:11 umbrel umbrel startup[1094]: Creating lightning-terminal_tor_server_1 …
Sep 09 09:38:11 umbrel umbrel startup[1094]: Creating bitcoin_app_proxy_1 …
Sep 09 09:38:11 umbrel umbrel startup[1094]: Creating bitcoin_tor_server_1 …
Sep 09 09:38:11 umbrel umbrel startup[1094]: Creating bitcoin_bitcoind_1 …
Sep 09 09:38:12 umbrel umbrel startup[1094]: Creating lightning_app_1 …
Sep 09 09:38:12 umbrel umbrel startup[1094]: Creating lightning_app_proxy_1 …
Sep 09 09:38:12 umbrel umbrel startup[1094]: Creating lightning_lnd_1 …
Sep 09 09:38:12 umbrel umbrel startup[1094]: Creating lightning_tor_server_1 …
Sep 09 09:38:12 umbrel umbrel startup[1094]: Creating ride-the-lightning_web_1 …
Sep 09 09:38:12 umbrel umbrel startup[1094]: Creating ride-the-lightning_boltz_1 …
Sep 09 09:38:12 umbrel umbrel startup[1094]: Creating ride-the-lightning_tor_server_1 …
Sep 09 09:38:13 umbrel umbrel startup[1094]: Creating ride-the-lightning_app_proxy_1 …
Sep 09 09:38:21 umbrel umbrel startup[1094]: [251B blob data]
Sep 09 09:38:21 umbrel umbrel startup[1094]: Creating nextcloud_cron_1 …
Sep 09 09:38:31 umbrel umbrel startup[1094]: [955B blob data]
Sep 09 09:38:34 umbrel umbrel startup[1094]: [371B blob data]
Sep 09 09:38:41 umbrel umbrel startup[1094]: [212B blob data]
Sep 09 09:38:41 umbrel umbrel startup[1094]: Umbrel is now accessible at
Sep 09 09:38:41 umbrel umbrel startup[1094]: http://umbrel.local
Sep 09 09:38:41 umbrel umbrel startup[1094]: http://192.168.1.156
Sep 09 09:38:41 umbrel systemd[1]: Started Umbrel Startup Service.
Sep 09 09:51:40 umbrel passwd[11676]: pam_unix(passwd:chauthtok): password changed for umbrel

External storage service logs

– Logs begin at Fri 2022-09-09 07:51:47 UTC, end at Fri 2022-09-09 09:52:12 UTC. –
Sep 09 07:51:52 umbrel systemd[1]: Starting External Storage Mounter…
Sep 09 07:51:52 umbrel external storage mounter[479]: Running external storage mount script…
Sep 09 07:51:52 umbrel external storage mounter[479]: Found device “External USB3.0”
Sep 09 07:51:52 umbrel external storage mounter[479]: Blacklisting USB device IDs against UAS driver…
Sep 09 07:51:52 umbrel external storage mounter[479]: Rebinding USB drivers…
Sep 09 07:51:53 umbrel external storage mounter[479]: Checking USB devices are back…
Sep 09 07:51:53 umbrel external storage mounter[479]: Waiting for USB devices…
Sep 09 07:51:54 umbrel external storage mounter[479]: Waiting for USB devices…
Sep 09 07:51:55 umbrel external storage mounter[479]: Checking if the device is ext4…
Sep 09 07:51:55 umbrel external storage mounter[479]: Yes, it is ext4
Sep 09 07:51:55 umbrel external storage mounter[479]: Checking if device contains an Umbrel install…
Sep 09 07:51:55 umbrel external storage mounter[479]: Yes, it contains an Umbrel install
Sep 09 07:51:55 umbrel external storage mounter[479]: Bind mounting external storage over local Umbrel installation…
Sep 09 07:51:55 umbrel external storage mounter[479]: Bind mounting external storage over local Docker data dir…
Sep 09 07:51:55 umbrel external storage mounter[479]: Bind mounting external storage to /swap
Sep 09 07:51:55 umbrel external storage mounter[479]: Bind mounting SD card root at /sd-card…
Sep 09 07:51:55 umbrel external storage mounter[479]: Checking Umbrel root is now on external storage…
Sep 09 07:51:56 umbrel external storage mounter[479]: Checking /var/lib/docker is now on external storage…
Sep 09 07:51:56 umbrel external storage mounter[479]: Checking /swap is now on external storage…
Sep 09 07:51:56 umbrel external storage mounter[479]: Setting up swapfile
Sep 09 07:51:57 umbrel external storage mounter[479]: Setting up swapspace version 1, size = 4 GiB (4294963200 bytes)
Sep 09 07:51:57 umbrel external storage mounter[479]: no label, UUID=1206cee0-1af2-4f01-9e25-9bcf62be9491
Sep 09 07:51:57 umbrel external storage mounter[479]: Checking SD Card root is bind mounted at /sd-root…
Sep 09 07:51:57 umbrel external storage mounter[479]: Starting external drive mount monitor…
Sep 09 07:51:57 umbrel external storage mounter[479]: Mount script completed successfully!
Sep 09 07:51:57 umbrel systemd[1]: Started External Storage Mounter.

External storage SD card update service logs

– Logs begin at Fri 2022-09-09 07:51:47 UTC, end at Fri 2022-09-09 09:52:12 UTC. –
Sep 09 07:52:12 umbrel systemd[1]: Starting External Storage SDcard Updater…
Sep 09 07:52:12 umbrel external storage updater[1017]: Checking if SD card Umbrel is newer than external storage…
Sep 09 07:52:12 umbrel external storage updater[1017]: No, SD version is not newer, exiting.
Sep 09 07:52:12 umbrel systemd[1]: Started External Storage SDcard Updater.

Karen logs

e[3A
Removing bitcoin_bitcoind_1 … done
e[3Be[1A
Removing bitcoin_tor_server_1 … done
e[1BRemoving lightning_app_proxy_1 …

Removing lightning_tor_server_1 …

Removing lightning_lnd_1 …

Removing lightning_app_1 …

e[4A
Removing bitcoin_server_1 … done
e[4Be[2A
Removing bitcoin_app_proxy_1 … done
e[2BGoing to remove bitcoin_server_1, bitcoin_bitcoind_1, bitcoin_app_proxy_1, bitcoin_tor_server_1
e[2A
Removing btc-rpc-explorer_tor_server_1 … done
e[2Be[1A
Removing btc-rpc-explorer_web_1 … done
e[1Be[1A
Removing lightning_app_1 … done
e[1Be[3A
Removing lightning_tor_server_1 … done
e[3Be[2A
Removing lightning_lnd_1 … done
e[2Be[2A
Stopping lightning-terminal_tor_server_1 … done
e[2Be[3A
Removing btc-rpc-explorer_app_proxy_1 … done
e[3BGoing to remove btc-rpc-explorer_app_proxy_1, btc-rpc-explorer_tor_server_1, btc-rpc-explorer_web_1
e[4A
Removing lightning_app_proxy_1 … done
e[4BGoing to remove lightning_app_proxy_1, lightning_tor_server_1, lightning_lnd_1, lightning_app_1
e[3A
Stopping lightning-terminal_app_proxy_1 … done
e[3Be[2A
Stopping electrs_electrs_1 … done
e[2BRemoving electrs_app_1 …

Removing electrs_tor_server_1 …

Removing electrs_electrs_1 …

Removing electrs_app_proxy_1 …

e[4A
Removing electrs_app_1 … done
e[4Be[3A
Removing electrs_tor_server_1 … done
e[3Be[2A
Removing electrs_electrs_1 … done
e[2Be[1A
Removing electrs_app_proxy_1 … done
e[1BGoing to remove electrs_app_1, electrs_tor_server_1, electrs_electrs_1, electrs_app_proxy_1
e[6A
Stopping nextcloud_cron_1 … done
e[6Be[1A
Stopping lightning-terminal_web_1 … done
e[1Be[3A
Stopping nextcloud_redis_1 … done
e[3BRemoving lightning-terminal_app_proxy_1 …

Removing lightning-terminal_tor_server_1 …

Removing lightning-terminal_web_1 …

e[3A
Removing lightning-terminal_app_proxy_1 … done
e[3Be[1A
Removing lightning-terminal_web_1 … done
e[1Be[2A
Removing lightning-terminal_tor_server_1 … done
e[2BGoing to remove lightning-terminal_app_proxy_1, lightning-terminal_tor_server_1, lightning-terminal_web_1
e[4A
Stopping nextcloud_db_1 … done
e[4BRemoving nextcloud_cron_1 …

Removing nextcloud_web_1 …

Removing nextcloud_db_1 …

Removing nextcloud_redis_1 …

Removing nextcloud_app_proxy_1 …

Removing nextcloud_tor_server_1 …

e[3A
Removing nextcloud_redis_1 … done
e[3Be[4A
Removing nextcloud_db_1 … done
e[4Be[1A
Removing nextcloud_tor_server_1 … done
e[1Be[5A
Removing nextcloud_web_1 … done
e[5Be[6A
Removing nextcloud_cron_1 … done
e[6Be[2A
Removing nextcloud_app_proxy_1 … done
e[2BGoing to remove nextcloud_cron_1, nextcloud_web_1, nextcloud_db_1, nextcloud_redis_1, nextcloud_app_proxy_1, nextcloud_tor_server_1

Stopping Docker services…

Stopping nginx …

Stopping manager …

Stopping dashboard …

Stopping tor …

Stopping auth …

e[5A
Stopping nginx … done
e[5Be[1A
Stopping auth … done
e[1Be[3A
Stopping dashboard … done
e[3Be[4A
Stopping manager … done
e[4Be[2A
Stopping tor … done
e[2BRemoving nginx …

Removing manager …

Removing dashboard …

Removing tor …

Removing auth …

e[3A
Removing dashboard … done
e[3Be[5A
Removing nginx … done
e[5Be[1A
Removing auth … done
e[1Be[4A
Removing manager … done
e[4Be[2A
Removing tor … done
e[2BRemoving network umbrel_main_network
Killing background services
karen is running in /home/umbrel/umbrel/events
Got signal:
karen is getting triggered!
Got signal:
karen is getting triggered!
./karen: line 68: /home/umbrel/umbrel/events/triggers/: Is a directory
./karen: line 68: /home/umbrel/umbrel/events/triggers/: Is a directory
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: debug
karen is getting triggered!

Docker containers

NAMES STATUS
bitcoin_server_1 Up 13 minutes
electrs_app_1 Up 13 minutes
nextcloud_web_1 Up 13 minutes
nextcloud_cron_1 Up 13 minutes
ride-the-lightning_app_proxy_1 Up 13 minutes
ride-the-lightning_tor_server_1 Up 13 minutes
ride-the-lightning_web_1 Up 13 minutes
ride-the-lightning_boltz_1 Up 13 minutes
lightning_tor_server_1 Up 13 minutes
lightning_app_1 Up 13 minutes
lightning_lnd_1 Up 13 minutes
lightning_app_proxy_1 Up 13 minutes
bitcoin_tor_server_1 Up 13 minutes
bitcoin_bitcoind_1 Restarting (1) 29 seconds ago
bitcoin_app_proxy_1 Up 13 minutes
lightning-terminal_web_1 Up 13 minutes
lightning-terminal_tor_server_1 Up 13 minutes
electrs_app_proxy_1 Up 13 minutes
electrs_tor_server_1 Up 13 minutes
electrs_electrs_1 Restarting (1) 8 seconds ago
lightning-terminal_app_proxy_1 Up 13 minutes
btc-rpc-explorer_app_proxy_1 Up 13 minutes
btc-rpc-explorer_web_1 Up 13 minutes
btc-rpc-explorer_tor_server_1 Up 13 minutes
tailscale_web_1 Up 14 minutes
tailscale_tor_server_1 Restarting (1) 24 seconds ago
nextcloud_redis_1 Up 14 minutes
nextcloud_tor_server_1 Up 14 minutes
nextcloud_app_proxy_1 Up 13 minutes
nextcloud_db_1 Up 13 minutes
nginx Up 14 minutes
manager Up 2 hours
dashboard Up 2 hours
tor Up 2 hours
auth Up 2 hours

Umbrel logs

Attaching to manager
manager | ::ffff:10.21.21.2 - - [Fri, 09 Sep 2022 09:52:10 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:104.0) Gecko/20100101 Firefox/104.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 09 Sep 2022 09:52:11 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:104.0) Gecko/20100101 Firefox/104.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 09 Sep 2022 09:52:12 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:104.0) Gecko/20100101 Firefox/104.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 09 Sep 2022 09:52:13 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:104.0) Gecko/20100101 Firefox/104.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 09 Sep 2022 09:52:14 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:104.0) Gecko/20100101 Firefox/104.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 09 Sep 2022 09:52:15 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:104.0) Gecko/20100101 Firefox/104.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 09 Sep 2022 09:52:16 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:104.0) Gecko/20100101 Firefox/104.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 09 Sep 2022 09:52:17 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:104.0) Gecko/20100101 Firefox/104.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 09 Sep 2022 09:52:18 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:104.0) Gecko/20100101 Firefox/104.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 09 Sep 2022 09:52:20 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:104.0) Gecko/20100101 Firefox/104.0”
manager |
manager | umbrel-manager

Tor logs

Attaching to tor
tor | Sep 09 09:38:03.000 [notice] Bootstrapped 56% (loading_descriptors): Loading relay descriptors
tor | Sep 09 09:38:03.000 [notice] Bootstrapped 63% (loading_descriptors): Loading relay descriptors
tor | Sep 09 09:38:36.000 [notice] Bootstrapped 68% (loading_descriptors): Loading relay descriptors
tor | Sep 09 09:38:37.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor | Sep 09 09:38:39.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor | Sep 09 09:38:39.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor | Sep 09 09:38:39.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor | Sep 09 09:38:39.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor | Sep 09 09:38:39.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor | Sep 09 09:38:39.000 [notice] Bootstrapped 100% (done): Done

App logs

bitcoin

tor_server_1 | Sep 09 09:38:26.066 [notice] Read configuration file “/etc/tor/torrc”.
tor_server_1 | Sep 09 09:38:26.155 [notice] Opening Socks listener on 127.0.0.1:9050
tor_server_1 | Sep 09 09:38:26.155 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
tor_server_1 | Sep 09 09:38:26.000 [notice] Bootstrapped 0% (starting): Starting
tor_server_1 | Sep 09 09:38:26.000 [notice] Starting with guard context “default”
tor_server_1 | Sep 09 09:38:27.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
tor_server_1 | Sep 09 09:38:27.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
tor_server_1 | Sep 09 09:38:27.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
tor_server_1 | Sep 09 09:39:25.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
tor_server_1 | Sep 09 09:39:25.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
tor_server_1 | Sep 09 09:39:25.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
tor_server_1 | Sep 09 09:39:25.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus
tor_server_1 | Sep 09 09:39:27.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
tor_server_1 | Sep 09 09:39:27.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs
tor_server_1 | Sep 09 09:39:27.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
tor_server_1 | Sep 09 09:39:27.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/6561, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
tor_server_1 | Sep 09 09:39:27.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/6561, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
tor_server_1 | Sep 09 09:39:28.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
tor_server_1 | Sep 09 09:39:29.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.
tor_server_1 | Sep 09 09:39:30.000 [notice] Bootstrapped 56% (loading_descriptors): Loading relay descriptors
tor_server_1 | Sep 09 09:39:37.000 [notice] Bootstrapped 64% (loading_descriptors): Loading relay descriptors
tor_server_1 | Sep 09 09:39:37.000 [notice] Bootstrapped 69% (loading_descriptors): Loading relay descriptors
tor_server_1 | Sep 09 09:39:37.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor_server_1 | Sep 09 09:39:38.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor_server_1 | Sep 09 09:39:38.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor_server_1 | Sep 09 09:39:38.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor_server_1 | Sep 09 09:39:38.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_server_1 | Sep 09 09:39:38.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_server_1 | Sep 09 09:39:38.000 [notice] Bootstrapped 100% (done): Done

================
==== Result ====

The debug script did not automatically detect any issues with your Umbrel.

Solution: delete / rename peers.dat

umbrel@umbrel:~ $ mv /mnt/data/umbrel/app-data/bitcoin/data/bitcoin/peers.dat /mnt/data/umbrel/app-data/bitcoin/data/bitcoin/peers.dat.bad

2 Likes

Any recommendations for those using Windows, Tor and trying to access it remotely?

I had a different problem —my (previously synced) node was now showing a blank “Syncing” message with no progress % Renaming the old peers.dat file and restarting fixed it. Thanks!

That’s a very fine solution. Now finally Bitcoin Node is synchronizing. I waited for this solution for about a month. Thank you community.

Hi All,

I’ve had the same issue (blank syncing screen). I’ve removed the peers.dat file but it reappears literally every day along with the blank sync screen, which means I have to make the same removal, very frustrating!

Any ideas / tips on what I can do to permanently resolve this?

I’m an IT noob btw :slight_smile:

Thanks in advance!

1 Like

The peers.dat should recreate itself. The reason the file is getting corrupted repeatedly is the real issue. Im dealing with same issue and not really sure what is going on. Both times I have shutdown my umbrel in the last few weeks the bitcoin node refuses to start sync again until I deal with the peers.dat file

1 Like

Yep, I’m getting the same corrupted peers.data file issue repeatedly. Delete file, bitcoin comes back, then it just gets corrupted again, sometimes only an hour or two later. What’s causing this? Makes Umbrel unusable if bitcoin itself can’t even stay up.

1 Like

I’m getting the same issue, once peers.dat is deleted, and the system rebooted, everything works as it should.

Until peers.dat returns then the system fails, I think something weird is going on with the process that creates the file, and it’s getting corrupted at that stage.

To get around this, I saved the below script to delete the peers.dat file as soon as it’s created. I called the script “delete_peers.sh” and saved it within ./bitcoin/data/bitcoin. I then passed the script to nohup so that it’ll continue to run after I close the terminal.

#!/bin/bash
DIR="<insert dir here>"   # Replace with the actual path to the directory

while true; do
    FILE=$(inotifywait -q -e create --format "%w%f" "$DIR")
    if [[ "$FILE" == "$DIR/peers.dat" ]]; then
        rm "$FILE"
    fi
done

Off to bed, but hopefully, I’ll still have a fully synced node in the morning.