Hi, I updated to the most recent Umbrel update but am having issues with my Bitcoin node stuck on “Starting”. I’ve tried restarting a couple times but no luck. Here are the logs, appreciate any help!
bitcoin
Attaching to bitcoin_server_1, bitcoin_tor_1, bitcoin_bitcoind_1, bitcoin_app_proxy_1, bitcoin_i2pd_daemon_1, bitcoin_tor_server_1
bitcoind_1 | 2023-07-02T19:15:32Z Using wallet /data/.bitcoin/wallet.dat
bitcoind_1 | 2023-07-02T19:15:32Z BerkeleyEnvironment::Open: LogDir=/data/.bitcoin/database ErrorFile=/data/.bitcoin/db.log
bitcoind_1 | 2023-07-02T19:15:32Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
bitcoind_1 | 2023-07-02T19:15:32Z Using wallet /data/.bitcoin/jam_default/wallet.dat
bitcoind_1 | 2023-07-02T19:15:32Z BerkeleyEnvironment::Open: LogDir=/data/.bitcoin/jam_default/database ErrorFile=/data/.bitcoin/jam_default/db.log
bitcoind_1 | 2023-07-02T19:15:32Z Using /16 prefix for IP bucketing
bitcoind_1 | 2023-07-02T19:15:32Z init message: Loading P2P addresses…
bitcoind_1 | 2023-07-02T19:15:36Z 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.
bitcoind_1 | 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.
bitcoind_1 | 2023-07-02T19:15:36Z Shutdown: In progress...
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.45 - - [Sun, 02 Jul 2023 19:15:32 GMT] "GET /v1/bitcoind/info/status HTTP/1.1" 304 - "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/114.0"
server_1 |
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.45 - - [Sun, 02 Jul 2023 19:15:34 GMT] "GET /v1/bitcoind/info/status HTTP/1.1" 304 - "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/114.0"
server_1 |
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.45 - - [Sun, 02 Jul 2023 19:15:36 GMT] "GET /v1/bitcoind/info/status HTTP/1.1" 304 - "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/114.0"
server_1 |
server_1 | umbrel-middleware
tor_1 | Jul 02 08:44:25.000 [notice] No circuits are opened. Relaxed timeout for circuit 578 (a Hidden service: Uploading HS descriptor 4-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [1 similar message(s) suppressed in last 8820 seconds]
tor_1 | Jul 02 12:04:07.000 [notice] Heartbeat: Tor's uptime is 12:00 hours, with 20 circuits open. I've sent 11.25 MB and received 18.15 MB. I've received 0 connections on IPv4 and 0 on IPv6. I've made 15 connections with IPv4 and 0 with IPv6.
tor_1 | Jul 02 12:04:07.000 [notice] While bootstrapping, fetched this many bytes: 633939 (consensus network-status fetch); 11094 (authority cert fetch); 8388658 (microdescriptor fetch)
tor_1 | Jul 02 12:04:07.000 [notice] While not bootstrapping, fetched this many bytes: 330967 (consensus network-status fetch); 17474 (authority cert fetch); 1113522 (microdescriptor fetch)
tor_1 | Jul 02 13:04:35.000 [notice] No circuits are opened. Relaxed timeout for circuit 849 (a Hidden service: Uploading HS descriptor 4-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [1 similar message(s) suppressed in last 15660 seconds]
tor_1 | Jul 02 18:04:07.000 [notice] Heartbeat: Tor's uptime is 18:00 hours, with 31 circuits open. I've sent 15.50 MB and received 21.59 MB. I've received 0 connections on IPv4 and 0 on IPv6. I've made 16 connections with IPv4 and 0 with IPv6.
tor_1 | Jul 02 18:04:07.000 [notice] While bootstrapping, fetched this many bytes: 633939 (consensus network-status fetch); 11094 (authority cert fetch); 8388658 (microdescriptor fetch)
tor_1 | Jul 02 18:04:07.000 [notice] While not bootstrapping, fetched this many bytes: 467680 (consensus network-status fetch); 22802 (authority cert fetch); 1146279 (microdescriptor fetch)
app_proxy_1 | Validating token: 703f794cba83 ...
app_proxy_1 | Validating token: 703f794cba83 ...
app_proxy_1 | Validating token: 703f794cba83 ...
app_proxy_1 | Validating token: 703f794cba83 ...
app_proxy_1 | Validating token: 703f794cba83 ...
app_proxy_1 | Validating token: 703f794cba83 ...
app_proxy_1 | Validating token: 703f794cba83 ...
app_proxy_1 | Validating token: 703f794cba83 ...
app_proxy_1 | Validating token: 703f794cba83 ...
app_proxy_1 | Validating token: 703f794cba83 ...
i2pd_daemon_1 | 18:59:29@885/error - Tunnels: Can't select next hop for tpMdOb-eqm9kz3oaqG6aZord66du9~XgEtwzybMekyo=
i2pd_daemon_1 | 18:59:29@885/error - Tunnels: Can't create inbound tunnel, no peers available
i2pd_daemon_1 | 19:00:14@885/error - Tunnels: Can't select next hop for wtoKX6F2Z2K~USWY2qQwM-iUYZ4PPKf5HIgNsL1CwA0=
i2pd_daemon_1 | 19:00:14@885/error - Tunnels: Can't create inbound tunnel, no peers available
i2pd_daemon_1 | 19:02:00@885/error - Tunnel: Tunnel with id 526436985 already exists
i2pd_daemon_1 | 19:10:25@311/error - NetDb: jZUfLzSXZXBmi6RmzepxP3BesqZO1CG6pkSKodXLd3k= destination requested, but no tunnels found
i2pd_daemon_1 | 19:10:33@796/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 19:11:29@885/error - Tunnels: Can't select next hop for 1-UVSh2f1pNZy9ao232tlECm69NiWw1foH4ow1JLdsM=
i2pd_daemon_1 | 19:11:29@885/error - Tunnels: Can't create inbound tunnel, no peers available
i2pd_daemon_1 | 19:13:34@991/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message