Hello everyone,
So I have just recently installed umbrel and began syncing the blockchain in order to setup my own Bitcoin node. However, when I reached around 380GB of data, the sync began looping through blocks. I restarted the container and the machine to no avail. I have tried the troubleshooting guide and removed peers.dat and even reindex=1 after I noticed that I was get messages indicating the chain was corrupt. However, each time either the sync started looping, or the container got stuck in a boot loop. This has happened three times and I am very confused. Any ideas? Should I try a complete fresh install of Umbrel? I have included a copy of my machine logs and the bitcoin app logs. Thanks!
=====================
= Umbrel debug info =
=====================
Umbrel version
--------------
0.5.4
Memory usage
------------
total used free shared buff/cache available
Mem: 15G 1.0G 558M 17M 14G 14G
Swap: 4.1G 331M 3.8G
total: 6.4%
system: 3.7%
bitcoin: 1%
ghostfolio: 0.8%
uptime-kuma: 0.7%
tailscale: 0.2%
Memory monitor logs
-------------------
2023-08-14 22:32:05 Memory monitor running!
2023-08-14 22:52:35 Memory monitor running!
1127 ? R 0:00 bash ./scripts/memory-monitor
1128 ? R 0:00 bash ./scripts/memory-monitor
1129 ? R 0:00 bash ./scripts/memory-monitor
1130 ? R 0:00 bash ./scripts/memory-monitor
Memory monitor is already running
2023-08-15 03:09:41 Memory monitor running!
2023-08-15 12:02:08 Memory monitor running!
2023-08-15 12:06:43 Memory monitor running!
Filesystem information
----------------------
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-ubuntu--lv 914G 145G 731G 17% /
/dev/mapper/ubuntu--vg-ubuntu--lv 914G 145G 731G 17% /
Karen logs
----------
Saving app ghostfolio in DB...
Successfully installed app ghostfolio
Got signal: debug
karen is getting triggered!
Debug result file generated
Got signal: debug
karen is getting triggered!
Debug result file generated
Got signal: change-password
karen is getting triggered!
This script must only be run on Umbrel OS
Got signal: change-password
karen is getting triggered!
This script must only be run on Umbrel OS
Got signal: debug
karen is getting triggered!
Debug result file generated
Got signal: debug
karen is getting triggered!
Debug result file generated
Got signal: change-password
karen is getting triggered!
This script must only be run on Umbrel OS
Got signal: debug
karen is getting triggered!
Debug result file generated
Got signal: backup
karen is getting triggered!
Deriving keys...
Creating backup...
Adding random padding...
1+0 records in
1+0 records out
8587 bytes (8.6 kB, 8.4 KiB) copied, 0.00020626 s, 41.6 MB/s
Creating encrypted tarball...
backup/
backup/.padding
Uploading backup...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0
100 9272 100 146 100 9126 48 3043 0:00:03 0:00:02 0:00:01 3091
100 9272 100 146 100 9126 48 3042 0:00:03 0:00:02 0:00:01 3090
{"message":"Successfully uploaded backup 1692134088705.tar.gz.pgp for backup ID bc81dc59e68b5fc9a2333db2f40bd1321cb3798f37946e4ad10d369e79abdfce"}
=============================
====== Backup success =======
=============================
Got signal: change-password
karen is getting triggered!
This script must only be run on Umbrel OS
Got signal: debug
karen is getting triggered!
Docker containers
-----------------
NAMES STATUS
ghostfolio_server_1 Up 9 hours
ghostfolio_redis_1 Up 9 hours
ghostfolio_postgres_1 Up 9 hours
ghostfolio_app_proxy_1 Up 9 hours
bitcoin_server_1 Up 10 hours
bitcoin_bitcoind_1 Up 2 seconds
bitcoin_i2pd_daemon_1 Up 10 hours
bitcoin_app_proxy_1 Up 10 hours
bitcoin_tor_1 Up 10 hours
uptime-kuma_server_1 Up 10 hours (healthy)
uptime-kuma_app_proxy_1 Up 10 hours
tailscale_web_1 Up 10 hours
nginx Up 10 hours
manager Up 10 hours
tor_proxy Up 10 hours
auth Up 10 hours
dashboard Up 10 hours
Umbrel logs
-----------
Attaching to manager
manager | ::ffff:10.21.0.4 - - [Tue, 15 Aug 2023 21:43:11 GMT] "GET /v1/account/token?token=925593d138dbe0deb083b9001038d018e1a6e5dcc8e62063ef2c4c0127bf5892 HTTP/1.1" 200 16 "-" "app-proxy/0.0.1"
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.4 - - [Tue, 15 Aug 2023 21:43:11 GMT] "GET /v1/account/token?token=925593d138dbe0deb083b9001038d018e1a6e5dcc8e62063ef2c4c0127bf5892 HTTP/1.1" 200 16 "-" "app-proxy/0.0.1"
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 21:43:12 GMT] "GET /v1/system/debug-result HTTP/1.0" 304 - "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36"
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 21:43:12 GMT] "GET /v1/apps?installed=1 HTTP/1.0" 304 - "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36"
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 21:43:12 GMT] "GET /v1/apps HTTP/1.0" 304 - "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36"
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 21:43:12 GMT] "GET /v1/system/storage HTTP/1.0" 200 619 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36"
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 21:43:12 GMT] "GET /v1/system/memory HTTP/1.0" 304 - "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36"
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.4 - - [Tue, 15 Aug 2023 21:43:12 GMT] "GET /v1/account/token?token=925593d138dbe0deb083b9001038d018e1a6e5dcc8e62063ef2c4c0127bf5892 HTTP/1.1" 200 16 "-" "app-proxy/0.0.1"
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 21:43:12 GMT] "GET /v1/system/get-update HTTP/1.0" 304 - "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36"
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Tue, 15 Aug 2023 21:43:13 GMT] "GET /v1/system/debug-result HTTP/1.0" 304 - "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36"
manager |
manager | umbrel-manager
Tor Proxy logs
--------
Attaching to tor_proxy
tor_proxy | Aug 15 12:07:19.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor_proxy | Aug 15 12:07:19.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor_proxy | Aug 15 12:07:19.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor_proxy | Aug 15 12:07:19.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_proxy | Aug 15 12:07:19.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_proxy | Aug 15 12:07:20.000 [notice] Bootstrapped 100% (done): Done
tor_proxy | Aug 15 17:19:17.000 [warn] Received http status code 404 ("Not found") from server 92.205.129.7:21 while fetching "/tor/keys/fp/EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97".
tor_proxy | Aug 15 18:07:11.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, with 0 circuits open. I've sent 1.14 MB and received 12.67 MB. I've received 0 connections on IPv4 and 0 on IPv6. I've made 11 connections with IPv4 and 0 with IPv6.
tor_proxy | Aug 15 18:07:11.000 [notice] While bootstrapping, fetched this many bytes: 679838 (consensus network-status fetch); 14104 (authority cert fetch); 11224359 (microdescriptor fetch)
tor_proxy | Aug 15 18:07:11.000 [notice] While not bootstrapping, fetched this many bytes: 159952 (consensus network-status fetch); 5388 (authority cert fetch)
App logs
--------
bitcoin
Attaching to bitcoin_server_1, bitcoin_bitcoind_1, bitcoin_i2pd_daemon_1, bitcoin_app_proxy_1, bitcoin_tor_1
bitcoind_1 | 2023-08-15T21:43:11Z * Using 610.1 MiB for transaction index database
bitcoind_1 | 2023-08-15T21:43:11Z * Using 533.9 MiB for basic block filter index database
bitcoind_1 | 2023-08-15T21:43:11Z * Using 8.0 MiB for chain state database
bitcoind_1 | 2023-08-15T21:43:11Z * Using 3729.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
bitcoind_1 | 2023-08-15T21:43:11Z init message: Loading block index…
bitcoind_1 | 2023-08-15T21:43:11Z Assuming ancestors of block 000000000000000000035c3f0d31e71a5ee24c5aaf3354689f65bd7b07dee632 have valid signatures.
bitcoind_1 | 2023-08-15T21:43:11Z Setting nMinimumChainWork=000000000000000000000000000000000000000044a50fe819c39ad624021859
bitcoind_1 | 2023-08-15T21:43:11Z Opening LevelDB in /data/.bitcoin/blocks/index
bitcoind_1 | 2023-08-15T21:43:11Z Opened LevelDB successfully
bitcoind_1 | 2023-08-15T21:43:11Z Using obfuscation key for /data/.bitcoin/blocks/index: 0000000000000000
i2pd_daemon_1 | 21:07:44@140/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 21:11:57@94/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 21:12:28@94/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 21:21:43@94/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 21:27:02@880/error - SSU2: RelayIntro unknown router to introduce
i2pd_daemon_1 | 21:29:54@880/error - SSU2: RelayIntro unknown router to introduce
i2pd_daemon_1 | 21:31:51@849/error - Tunnel: Tunnel with id 549600294 already exists
i2pd_daemon_1 | 21:31:52@849/error - Tunnel: Tunnel with id 549600294 already exists
i2pd_daemon_1 | 21:35:28@94/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 21:38:04@140/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message
server_1 | BitcoindError: Unable to obtain peer info
server_1 | at /app/services/bitcoind.js:23:18
server_1 | at IncomingMessage.<anonymous> (/app/node_modules/bitcoind-rpc/lib/index.js:107:7)
server_1 | at IncomingMessage.emit (events.js:326:22)
server_1 | at endReadableNT (_stream_readable.js:1241:12)
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.4 - - [Tue, 15 Aug 2023 21:43:14 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/115.0.0.0 Safari/537.36"
server_1 |
server_1 | umbrel-middleware
tor_1 | Aug 15 12:09:33.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor_1 | Aug 15 12:09:34.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_1 | Aug 15 12:09:34.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_1 | Aug 15 12:09:35.000 [notice] Bootstrapped 100% (done): Done
tor_1 | Aug 15 15:46:32.000 [notice] No circuits are opened. Relaxed timeout for circuit 359 (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.
tor_1 | Aug 15 18:09:25.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, with 15 circuits open. I've sent 6.11 MB and received 16.46 MB. I've received 0 connections on IPv4 and 0 on IPv6. I've made 11 connections with IPv4 and 0 with IPv6.
tor_1 | Aug 15 18:09:25.000 [notice] While bootstrapping, fetched this many bytes: 679838 (consensus network-status fetch); 14357 (authority cert fetch); 11224359 (microdescriptor fetch)
tor_1 | Aug 15 18:09:25.000 [notice] While not bootstrapping, fetched this many bytes: 136874 (consensus network-status fetch); 7100 (authority cert fetch); 221084 (microdescriptor fetch)
tor_1 | Aug 15 20:10:33.000 [notice] No circuits are opened. Relaxed timeout for circuit 613 (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 15840 seconds]
app_proxy_1 | Validating token: 925593d138db ...
app_proxy_1 | Validating token: 925593d138db ...
app_proxy_1 | Validating token: 925593d138db ...
app_proxy_1 | Validating token: 925593d138db ...
app_proxy_1 | Validating token: 925593d138db ...
app_proxy_1 | Validating token: 925593d138db ...
app_proxy_1 | Validating token: 925593d138db ...
app_proxy_1 | Validating token: 925593d138db ...
app_proxy_1 | Validating token: 925593d138db ...
app_proxy_1 | Validating token: 925593d138db ...
This should help, and may also speed up the sync.
