Blockchain sync is way too slow

Support and Troubleshooting
1

Hi guys, I’m having issues with the speed of blockchain sync.

I’ve setup an Umbrel instance on GCP (Ubuntu - 1vcpu - 4GB ram - HDD - us-central). Everything was going ok (and fast) until it reached 30% aprox. Now the sync is way way too slow and I have no idea why.

It’s validates 2 blocks every ~30 seconds, sometimes more.

I’ve got some other umbrel nodes on GCP with different resources and never had an issue.

Don’t think it makes any difference by I’m running it on a preemtible VM, which gracefully stops at least once every 24hs and restarts a couple of minutes later.

Some monitoring of the last 6 hours. Memory and CPU are both under 50% (can’t upload more than one image as I’m new user)

image
image780×812 36.6 KB

Thanks in advance for the support.

PD: Cut the App logs as I excedded maximun chars and I can’t attach it. Don’t think I removed anything meaningful to the issue though.

=====================
= Umbrel debug info =
=====================

Umbrel version
--------------
0.3.14

Memory usage
------------
              total        used        free      shared  buff/cache   available
Mem:           3.9G        1.5G        119M        2.0M        2.3G        2.2G
Swap:            0B          0B          0B

total: 37.6%
bitcoin: 28.4%
system: 3.7%
mempool: 2.3%
btc-rpc-explorer: 1.3%
lnd: 1.2%
tor: 0.7%
electrs: 0%

Memory monitor logs
-------------------
   5876 pts/1    S      0:00 bash ./scripts/memory-monitor
Memory monitor is already running
2021-07-16 16:29:26 Memory monitor running!
2021-07-16 16:34:02 Memory monitor running!
2021-07-19 07:58:10 Memory monitor running!
2021-07-20 08:53:09 Memory monitor running!
2021-07-20 14:14:15 Memory monitor running!
2021-07-20 14:43:42 Memory monitor running!
2021-07-21 10:49:33 Memory monitor running!
2021-07-21 15:29:38 Memory monitor running!

Filesystem information
----------------------
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       485G  147G  338G  31% /
/dev/root       485G  147G  338G  31% /

Karen logs
----------

./karen: line 68: /home/nelsongaldeman/umbrel/events/triggers/: Is a directory
./karen: line 68: /home/nelsongaldeman/umbrel/events/triggers/: Is a directory
Got signal: change-password
karen is getting triggered!
This script must only be run on Umbrel OS
karen is running in /home/nelsongaldeman/umbrel/events
Got signal: change-password
karen is getting triggered!
This script must only be run on Umbrel OS
Got signal: backup
karen is getting triggered!
Deriving keys...
cat: /home/nelsongaldeman/umbrel/db/umbrel-seed/seed: No such file or directory
Missing derivation parameter, this is unsafe, exiting.
Got signal: backup
karen is getting triggered!
Deriving keys...
cat: /home/nelsongaldeman/umbrel/db/umbrel-seed/seed: No such file or directory
Missing derivation parameter, this is unsafe, exiting.
Got signal: change-password
karen is getting triggered!
This script must only be run on Umbrel OS
karen is running in /home/nelsongaldeman/umbrel/events
Got signal: 
karen is getting triggered!
./karen: line 68: /home/nelsongaldeman/umbrel/events/triggers/: Is a directory
Got signal: 
karen is getting triggered!
./karen: line 68: /home/nelsongaldeman/umbrel/events/triggers/: Is a directory
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
karen is running in /home/nelsongaldeman/umbrel/events
Got signal: 
karen is getting triggered!
Got signal: 
karen is getting triggered!
./karen: line 68: /home/nelsongaldeman/umbrel/events/triggers/: Is a directory
./karen: line 68: /home/nelsongaldeman/umbrel/events/triggers/: Is a directory
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!

Docker containers
-----------------
NAMES                    STATUS
mempool_api_1            Up 5 hours
mempool_mariadb_1        Up 5 hours
mempool_web_1            Up 5 hours
btc-rpc-explorer_web_1   Up 5 hours
middleware               Up 5 hours
neutrino-switcher        Up 5 hours
bitcoin                  Up 5 hours
lnd                      Up 5 hours
nginx                    Up 5 hours
manager                  Up 5 hours
dashboard                Up 5 hours
electrs                  Up 5 hours
tor                      Up 5 hours

Bitcoin Core logs
-----------------

Attaching to bitcoin
bitcoin              | 2021-07-21T20:40:26Z Pre-allocating up to position 0x1200000 in rev00882.dat
bitcoin              | 2021-07-21T20:40:26Z UpdateTip: new best=0000000000000000019651106da1f1852a601a5e3dca64b0ed95f367d91c98d9 height=468474 version=0x20000000 log2_work=86.499634 tx=226677257 date='2017-05-28T01:19:28Z' progress=0.342178 cache=38.1MiB(39631txo)
bitcoin              | 2021-07-21T20:40:27Z Pre-allocating up to position 0x100000 in fltr00131.dat
bitcoin              | 2021-07-21T20:40:30Z UpdateTip: new best=000000000000000000eb12858afb17e241cd3f02b43357c3b1ef2126872a866a height=468475 version=0x20000000 log2_work=86.499668 tx=226679302 date='2017-05-28T01:29:53Z' progress=0.342181 cache=39.0MiB(47410txo)
bitcoin              | 2021-07-21T20:40:34Z UpdateTip: new best=000000000000000000e138a9f0a8364055125c08c0ad8b6b2a3d545a5154d1ac height=468476 version=0x20000002 log2_work=86.499702 tx=226681338 date='2017-05-28T01:39:10Z' progress=0.342184 cache=40.0MiB(55212txo)
bitcoin              | 2021-07-21T20:40:45Z UpdateTip: new best=00000000000000000152888d243fda604a6adbbe6d5df786c38ef6c88e7e2ada height=468477 version=0x20000000 log2_work=86.499736 tx=226683031 date='2017-05-28T01:46:10Z' progress=0.342187 cache=40.9MiB(63160txo)
bitcoin              | 2021-07-21T20:40:47Z Socks5() connect to 2001:41d0:700:3f2b:::8333 failed: general failure
bitcoin              | 2021-07-21T20:40:59Z UpdateTip: new best=0000000000000000002786ddc8e68c897387180385bd5c55acd05db11505203f height=468478 version=0x20000000 log2_work=86.499769 tx=226684498 date='2017-05-28T01:49:32Z' progress=0.342189 cache=41.8MiB(70290txo)
bitcoin              | 2021-07-21T20:41:03Z UpdateTip: new best=000000000000000000cdca88fd8db8f5994fcdce424656c3368024742d19b426 height=468479 version=0x20000002 log2_work=86.499803 tx=226686509 date='2017-05-28T02:13:26Z' progress=0.342192 cache=43.1MiB(80791txo)
bitcoin              | 2021-07-21T20:41:06Z UpdateTip: new best=0000000000000000019d7b595966a4c2ebaf677d3847c6c9c22e9870638aceb1 height=468480 version=0x20000000 log2_work=86.499837 tx=226688160 date='2017-05-28T02:29:18Z' progress=0.342194 cache=44.8MiB(94996txo)
bitcoin              | 2021-07-21T20:41:08Z UpdateTip: new best=0000000000000000006af23fb1452aba2c7495bde5364045b2e711a8aafba538 height=468481 version=0x20000000 log2_work=86.499871 tx=226690602 date='2017-05-28T02:37:47Z' progress=0.342198 cache=46.1MiB(105217txo)
bitcoin              | 2021-07-21T20:41:13Z UpdateTip: new best=000000000000000000af5993820f6f04a6ff48b91ee5e5da10dc5ff2c7bd4060 height=468482 version=0x20000000 log2_work=86.499904 tx=226693138 date='2017-05-28T02:55:12Z' progress=0.342202 cache=47.2MiB(114740txo)
bitcoin              | 2021-07-21T20:41:16Z UpdateTip: new best=000000000000000000579d22990060eef9b8c246b02f9cdc4a5af428caf37e31 height=468483 version=0x20000002 log2_work=86.499938 tx=226695420 date='2017-05-28T02:57:38Z' progress=0.342205 cache=47.9MiB(119979txo)
bitcoin              | 2021-07-21T20:41:19Z UpdateTip: new best=0000000000000000015307912dd38b4127434d480bd5f062861ea2fdcb779dbd height=468484 version=0x20000000 log2_work=86.499972 tx=226697012 date='2017-05-28T03:00:40Z' progress=0.342208 cache=48.6MiB(125653txo)
bitcoin              | 2021-07-21T20:41:33Z UpdateTip: new best=000000000000000000b23263d03305c3c41c843a98a42a9d3c4b9ba175e2cbe5 height=468485 version=0x20000000 log2_work=86.500006 tx=226698592 date='2017-05-28T03:03:35Z' progress=0.342210 cache=49.4MiB(132274txo)
bitcoin              | 2021-07-21T20:41:43Z UpdateTip: new best=0000000000000000017e3066acbc87da597aa300b878683fc41330b4b37e44fb height=468486 version=0x20000000 log2_work=86.500039 tx=226700393 date='2017-05-28T03:09:14Z' progress=0.342213 cache=50.5MiB(141549txo)
bitcoin              | 2021-07-21T20:41:54Z Pre-allocating up to position 0x600000 in rev00883.dat
bitcoin              | 2021-07-21T20:41:54Z UpdateTip: new best=000000000000000000818727eea59e47d622f0a8d8448b247e993143e7e8f767 height=468487 version=0x20000000 log2_work=86.500073 tx=226702250 date='2017-05-28T03:11:24Z' progress=0.342216 cache=51.2MiB(147397txo)
bitcoin              | 2021-07-21T20:42:08Z UpdateTip: new best=0000000000000000007ba319a2fe7e87367ccb4442645cea99a9157c7957130e height=468488 version=0x20000000 log2_work=86.500107 tx=226702964 date='2017-05-28T03:13:22Z' progress=0.342217 cache=51.8MiB(151901txo)
bitcoin              | 2021-07-21T20:42:19Z UpdateTip: new best=000000000000000001460955f5d8f9c6e1e4017748befc880252bf76e4b91ef3 height=468489 version=0x20000000 log2_work=86.500141 tx=226704963 date='2017-05-28T03:31:50Z' progress=0.342220 cache=52.4MiB(157359txo)
bitcoin              | 2021-07-21T20:42:21Z UpdateTip: new best=000000000000000000b4c69925b52d066f8c129ccefd75c6d1eef84b0499e31c height=468490 version=0x20000000 log2_work=86.500174 tx=226707068 date='2017-05-28T03:37:54Z' progress=0.342223 cache=52.9MiB(160939txo)
bitcoin              | 2021-07-21T20:42:26Z UpdateTip: new best=000000000000000001352e8e349f1d1395dfafb59815fff54c334c240d610055 height=468491 version=0x20000000 log2_work=86.500208 tx=226709170 date='2017-05-28T03:53:01Z' progress=0.342226 cache=53.5MiB(165662txo)
bitcoin              | 2021-07-21T20:42:33Z UpdateTip: new best=00000000000000000035ce5f741dc3b0e8fa8202bcaaa1c29ae0be6b9b419e89 height=468492 version=0x20000000 log2_work=86.500242 tx=226711109 date='2017-05-28T04:01:58Z' progress=0.342229 cache=54.1MiB(170747txo)
bitcoin              | 2021-07-21T20:42:45Z UpdateTip: new best=000000000000000001986052d00a4b02d29fdc1464d6c013237b702a5d21dc3a height=468493 version=0x20000000 log2_work=86.500276 tx=226711996 date='2017-05-28T04:03:12Z' progress=0.342230 cache=54.8MiB(176885txo)
bitcoin              | 2021-07-21T20:42:55Z UpdateTip: new best=000000000000000001a1c1541385862b1fd5005e99eb3847dc9a2f34fd7c6237 height=468494 version=0x20000000 log2_work=86.500309 tx=226714280 date='2017-05-28T04:13:04Z' progress=0.342234 cache=55.7MiB(184292txo)
bitcoin              | 2021-07-21T20:43:04Z Pre-allocating up to position 0x700000 in rev00883.dat
bitcoin              | 2021-07-21T20:43:04Z UpdateTip: new best=0000000000000000009c052962ef3f85d174c5989ab86029415ee99bae53277c height=468495 version=0x20000002 log2_work=86.500343 tx=226716433 date='2017-05-28T04:20:36Z' progress=0.342237 cache=56.3MiB(188895txo)
bitcoin              | 2021-07-21T20:43:19Z UpdateTip: new best=000000000000000000729c72e1538a6113ef2e451bcade6e5c079107415f4d61 height=468496 version=0x20000002 log2_work=86.500377 tx=226718444 date='2017-05-28T04:26:35Z' progress=0.342240 cache=57.1MiB(195198txo)
bitcoin              | 2021-07-21T20:43:30Z UpdateTip: new best=000000000000000000f2a1fe6f539ca6f072c34aa628f95648abbe92c5e605bd height=468497 version=0x20000002 log2_work=86.500411 tx=226720132 date='2017-05-28T04:34:25Z' progress=0.342242 cache=57.8MiB(201402txo)
bitcoin              | 2021-07-21T20:43:52Z UpdateTip: new best=000000000000000001cafc317443a4eac370eef3f9b32332556b24c9b50fb44d height=468498 version=0x20000000 log2_work=86.500444 tx=226721360 date='2017-05-28T04:36:58Z' progress=0.342244 cache=58.7MiB(208327txo)

LND logs
--------

Attaching to lnd
lnd                  | 2021-07-21 19:12:57.637 [INF] BTCN: Verified 1 filter header in the last 6m57.25s (height 692047, 2021-07-21 19:12:41 +0000 UTC)
lnd                  | 2021-07-21 19:14:11.367 [WRN] BTCN: Banning peer 54.178.155.230:8333: duration=48h0m0s, reason=peer was unable to serve compact filters
lnd                  | 2021-07-21 19:14:11.369 [INF] BTCN: Lost peer 54.178.155.230:8333 (outbound)
lnd                  | 2021-07-21 19:14:12.498 [WRN] BTCN: Banning peer 34.226.136.24:8333: duration=48h0m0s, reason=peer was unable to serve compact filters
lnd                  | 2021-07-21 19:14:12.501 [INF] BTCN: Lost peer 34.226.136.24:8333 (outbound)
lnd                  | 2021-07-21 19:14:13.166 [INF] BTCN: New valid peer 135.181.215.237:8333 (outbound) (/Satoshi:0.21.1(@emzy)/)
lnd                  | 2021-07-21 19:37:34.379 [INF] BTCN: Processed 1 block in the last 24m38.52s (height 692048, 2021-07-21 19:36:48 +0000 UTC)
lnd                  | 2021-07-21 19:37:34.399 [INF] BTCN: Attempting to fetch set of un-checkpointed filters at height=692048, hash=0000000000000000000e66577cd3212da05e5137283aa75560ea7ae7989d94c2
lnd                  | 2021-07-21 19:37:35.894 [INF] BTCN: Verified 1 filter header in the last 24m38.25s (height 692048, 2021-07-21 19:36:48 +0000 UTC)
lnd                  | 2021-07-21 19:41:56.192 [INF] BTCN: Processed 1 block in the last 4m21.81s (height 692049, 2021-07-21 19:41:16 +0000 UTC)
lnd                  | 2021-07-21 19:41:56.218 [INF] BTCN: Attempting to fetch set of un-checkpointed filters at height=692049, hash=0000000000000000000f976c8f6dc4ccb797969852c746b051efc51c97f85c86
lnd                  | 2021-07-21 19:42:06.221 [INF] BTCN: Verified 1 filter header in the last 4m30.32s (height 692049, 2021-07-21 19:41:16 +0000 UTC)
lnd                  | 2021-07-21 19:48:49.929 [INF] BTCN: Processed 1 block in the last 6m53.73s (height 692050, 2021-07-21 19:48:26 +0000 UTC)
lnd                  | 2021-07-21 19:48:49.933 [INF] BTCN: Attempting to fetch set of un-checkpointed filters at height=692050, hash=0000000000000000000d1bbe6cb6e989b57c472080a8b38470665e5e7cb3d906
lnd                  | 2021-07-21 19:48:59.940 [INF] BTCN: Verified 1 filter header in the last 6m53.71s (height 692050, 2021-07-21 19:48:26 +0000 UTC)
lnd                  | 2021-07-21 19:53:17.463 [INF] BTCN: Processed 1 block in the last 4m27.53s (height 692051, 2021-07-21 19:53:16 +0000 UTC)
lnd                  | 2021-07-21 19:53:17.465 [INF] BTCN: Attempting to fetch set of un-checkpointed filters at height=692051, hash=0000000000000000000808d1ca85366160b2aa01b6e6b6b81204ab09fd065a83
lnd                  | 2021-07-21 19:53:27.469 [INF] BTCN: Verified 1 filter header in the last 4m27.52s (height 692051, 2021-07-21 19:53:16 +0000 UTC)
lnd                  | 2021-07-21 20:03:33.748 [INF] BTCN: Processed 1 block in the last 10m16.28s (height 692052, 2021-07-21 20:03:27 +0000 UTC)
lnd                  | 2021-07-21 20:03:33.776 [INF] BTCN: Attempting to fetch set of un-checkpointed filters at height=692052, hash=0000000000000000000bafd156d824f10f3da2054aa41114940d931305341b14
lnd                  | 2021-07-21 20:03:35.009 [INF] BTCN: Verified 1 filter header in the last 10m7.54s (height 692052, 2021-07-21 20:03:27 +0000 UTC)
lnd                  | 2021-07-21 20:19:06.429 [INF] BTCN: Processed 1 block in the last 15m32.68s (height 692053, 2021-07-21 20:18:58 +0000 UTC)
lnd                  | 2021-07-21 20:19:06.449 [INF] BTCN: Attempting to fetch set of un-checkpointed filters at height=692053, hash=000000000000000000139835f0661e5bd480bc0805d89c51d7ba29cf860f0fdf
lnd                  | 2021-07-21 20:19:08.486 [INF] BTCN: Verified 1 filter header in the last 15m33.47s (height 692053, 2021-07-21 20:18:58 +0000 UTC)
lnd                  | 2021-07-21 20:34:44.217 [INF] BTCN: Processed 1 block in the last 15m37.78s (height 692054, 2021-07-21 20:34:38 +0000 UTC)
lnd                  | 2021-07-21 20:34:44.221 [INF] BTCN: Attempting to fetch set of un-checkpointed filters at height=692054, hash=0000000000000000000084c989cd1de11fbe30183016edc02142bfc0e3a5b6af
lnd                  | 2021-07-21 20:34:45.582 [INF] BTCN: Verified 1 filter header in the last 15m37.09s (height 692054, 2021-07-21 20:34:38 +0000 UTC)
lnd                  | 2021-07-21 20:38:07.371 [INF] BTCN: Processed 1 block in the last 3m23.15s (height 692055, 2021-07-21 20:38:17 +0000 UTC)
lnd                  | 2021-07-21 20:38:07.386 [INF] BTCN: Attempting to fetch set of un-checkpointed filters at height=692055, hash=0000000000000000000575d3085ed453481b0eadb771b1c31deaafdefb66ea04
lnd                  | 2021-07-21 20:38:17.428 [INF] BTCN: Verified 1 filter header in the last 3m31.84s (height 692055, 2021-07-21 20:38:17 +0000 UTC)

Tor logs
--------

Attaching to tor
tor                  | Jul 21 19:08:48.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $7327876AE79C997DFE311A7B15B4FA875736BBD1~F3Netze [LqeU711tRrsCBctUvVOrCsmTgfp/mAkMj59IiH+B9Xs] at 185.220.100.255. Retrying on a new circuit.
tor                  | Jul 21 19:08:55.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
tor                  | Jul 21 19:10:34.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $BB034C34ED9E60F7709ED93FB432A9BA12A2F2B6~Digitalcourage4ip1b [13ymK6gywgRSdmj87nufw/yWzjJaBK3+as1ndJ1yJNw] at 185.220.102.248. Retrying on a new circuit.
tor                  | Jul 21 19:12:40.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $58BC2CFFA7894FC8F4CC5D8A77E38FDCFDB1DC0E~Digitalcourage4ipba [x8+pg/DZHkzgvoDnm9zieylxP4JgL6iygRJON8s0cKg] at 185.220.102.241. Retrying on a new circuit.
tor                  | Jul 21 19:12:55.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $C688B3EF9AB0354EB2794174519BB9ED9E6467E7~Digitalcourage4ipab [mujgpnbKgD0CxZ3d/Mv0g4nlCHIe9MfWl6QbJ4+zDzI] at 185.220.102.240. Retrying on a new circuit.
tor                  | Jul 21 19:13:10.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $FBFA03C2F18342C7D642108076EDF097570D1F4A~177DusExitRelay [PIF8paLjIdM1AlnN8ATIV6qvIHBHH5Qg/vvGApuAda8] at 5.199.143.202. Retrying on a new circuit.
tor                  | Jul 21 19:13:25.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $563C8868165186D2F7BA1FCF982EB20DEB82B350~EndCensorship [i4yWYhG9ClOgTJN7vFDI7Q5KzDDF0gZlWJr8uSUT8LM] at 107.189.10.237. Retrying on a new circuit.
tor                  | Jul 21 19:13:40.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $14CF04009FFE81448391F3FA626E9D2F114BDE54~hp [qyed3WZVid2Yblrzr2UCJVhgcgZab23IQ97OL16zTrk] at 104.244.74.57. Retrying on a new circuit.
tor                  | Jul 21 19:13:55.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $D315FDE4F81387BC07839BCBBBD20719389A7E02~Ganthet [zeAI/stnuGlCuwL+903LnLpj6Tv3rSa62h76lXxaM6o] at 45.153.160.2. Retrying on a new circuit.
tor                  | Jul 21 19:14:10.000 [notice] We tried for 15 seconds to connect to '[scrubbed]' using exit $1E9B32A00C594B032597D8B6A1DF79B734531530~Digitalcourage4ipdb [QdNw1lImquTa8U/+W16G8Lilim6Gl8RhuLA13NpHWkM] at 185.220.102.243. Retrying on a new circuit.
tor                  | Jul 21 19:14:10.000 [notice] Tried for 133 seconds to get a connection to [scrubbed]:8333. Giving up.
tor                  | Jul 21 19:18:01.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
tor                  | Jul 21 19:18:51.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
tor                  | Jul 21 19:52:50.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
tor                  | Jul 21 19:56:30.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
tor                  | Jul 21 19:56:50.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
tor                  | Jul 21 19:56:51.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
tor                  | Jul 21 20:02:31.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
tor                  | Jul 21 20:02:32.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
tor                  | Jul 21 20:04:37.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
tor                  | Jul 21 20:10:43.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
tor                  | Jul 21 20:12:48.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
tor                  | Jul 21 20:12:50.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
tor                  | Jul 21 20:24:12.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
tor                  | Jul 21 20:27:18.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
tor                  | Jul 21 20:27:49.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
tor                  | Jul 21 20:30:32.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
tor                  | Jul 21 20:33:59.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
tor                  | Jul 21 20:38:39.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
tor                  | Jul 21 20:40:47.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.

================
==== Result ====
================
The debug script did not automatically detect any issues with your Umbrel.
1 Like
2

This is normal. You have to be patient. The first third of the blockchain is very light, because the blocks had barely any transactions, so it syncs fast. Then it starts to slow down. And the last 30% will be very slow indeed.

This is especially true if you use a HDD not an SSD. But once it’s done your HDD will be just fine to run it. You won’t have slowness. It’s only the initial sync that’s very slow.

1 Like
3

Thanks for your reply. Haven’t closely monitored others syncs before but each block being <1MB ~15s on average seems like a lot. I’m connected to 9 peers atm. Could it be because other nodes take long time to find the old blocks I’m requiesting?

Edit: I’ve checked the % is baed on bytes not on block count so I don’t see a reason why the first chunk was quicker as you suggest (around 18-20 hours). I’m currently at 36% so that’s only 6% in more than 24hs. In terms of block count % I’m at ~68%.

I also don’t think the bottleneck here is running an HDD instead of SSD, at an average ~15 per block it has more than enough time to save and index it.

1 Like
4

I tested that with 2 identical nodes a while ago, 1 was running a SSD, and 1 was with an HDD – The HDD took about 19 days to sync, and the SSD only took maybe 45 hours. You’d be better off using a SSD now, then when it’s fully synced, you can move it back to an HDD.

4 Likes
5

Thanks for your feedback. Then it can actually be that :thinking: I’ll setup a new one in paralel ussing an SSD and see if it’s any better! Not sure how hard would be to migrate the data though but that’s a problem of future me lol

Edit: New node is up, same specs the only difference is SSD. Let’s see how they perform.

6

If you have an SSD, stop and start over. If you haven’t opened any channels (which is pretty sure because you haven’t finished syncing), restarting is no problem at all. You can just add the seed and you’re ready to restart syncing.

The reason SSD is better for a node is because SSD as more reliable on the long term which is a huge benefit if you run a lightning node on top of your bitcoin node.

7

Maybe a little bit off-topic here but SSD is not more reliable than a regular HDD, it’s in fact the opposite. SSD’s are better because they are way way waaaaaay faster to do read/write operations than mechanical disks which is quite convenient on a 360GB database like Bitcoin blockchain.

Ok on-topic again: I’ve setup a secondary node using an SSD so I’ve got both and I can messure how long it takes to sync on both!

1 Like
8

Depends on your use case. If it’s in a very stable environment with no vibration and no temperature changes you’re right that HDD can last more than SSD. But in portable devices SSD is much more reliable. So, yeah maybe in an Umbrel node HDD may be better indeed, aside from the speed.

1 Like
9

I have been testing various pi setups and I found these things slow it down.

Things that can be fixed:

Use SSD saves around 20/40%
Use cable over wifi
Use a 8gb pi (2gb is possible but takes ages and 4gb takes about twice as slow)
Make sure you are using an official power supply as if you do not have a monitor plugged in you may not see the under voltage which error which can throttle the CPU

If I am using any of the above I just sync Bitcoin core to another machine (I use an old laptop) and copy the data and blocks folders over to the external hdd either using scp or just plugging it into the laptop itself (make sure umbrel has configured the hdd otherwise it will wipe the data when you plug it back onto the PI)

Things that can’t be fixed

TOR is just slower than HTTP

Out of all of the above sdd and then using an 8gb PI gave me the best improvements.

4 Likes
10

Thanks @cryptokskillz. In this particular case I’m running them on Google Cloud, not on a Pi! I could try increasing the ram though.

11

Is there a way to disable TOR just for the initial sync, then re-enable it once done?

1 Like
12

I have 2Gbps internet and an SSD and mine is still slow! Would be nice to turn off TOR for initial sync. Also would be nice to get more that 10 peers. Please help I need to kill my 2Gbps fiber pipe. :slight_smile:

13

Great advice!
Another “trick” also:
If you have another node in your LAN (local network), you can use it WITHOUT interruption or manually copying the data.
You can connect the new node to your local node IP and sync it from there, faster and locally.
Use the SSH command
bitcoin-cli addnode "192.168.0.6:8333" "onetry" - replace the IP with your “old” node IP and done, you will be taking blocks from your local node, smoothly.

More details here

and here

2 Likes
14

That’s a cool trick. I’ll definitely do that as I do have two nodes currently. I restored a new build with the seed for my first node but oddly its missing the bitcoin in the wallet that I transferred to the first node. The first node isn’t fully synced either as I lit it up 3 days before my new and improved node. Even with it not fully synced it shows the balance though. Wondering if HA is possible as well.

15

I can’t run the command from the main terminal. I’m guessing it’s because it’s being run as a docker container. Anyone know how to get access to the docker container terminal?

16

Here are two guides I wrote for all Umbrel users and you should always have them at hand:

1 Like
17

umbrel@umbrel:~/umbrel $ docker exec bitcoin bitcoin-cli addnode "192.168.1.57:8333" "onetry"

2 Likes
18

Thank you for this information! This seems to almost work for me. When I issue the command, my Umbrel node appears in my other nodes peer list. However, the Network field shows Unroutable and the ping time is 18.5 seconds. I suspect this is because my other node can not rout over tor. Is there a way to disable tor on my Umbrel node temporarily and test this?

19

No need to disable Tor. the node will sync through local IP

20

Good. Thanks for the hint. I must have some other problem I am hunting for.