My umbrel node has started behaving funny. When I visit the dashboard at umbrel.local, the UI just animates back and forth for Lightning, Bitcoin Wallet, and Bitcoin Core, but it never really finishes loading.
Has anybody had this problem? What would be a good way to troubleshoot this?
What I tried already when I noticed the problem
I ran the upgrade to 0.3.10 and let it restart. No noticeable change – the UI still animates endlessly.
I SSHed into the umbrel. I ran cd ~/umbrel/bin/ then ./bitcoin-cli getblockchaininfo. It took a few seconds to response, but gave a completely empty response.
I tried checking for error logs via SSH, but couldn’t find any that seemed relevant.
Just had the same thing. I disabled mempool then it said my wallet was locked, so I unlocked it by looking at the 24 secret words. I didn’t even have to enter them. Hope this helps.
I was able to get debug log info by following directions from @blckbx
Error message says that it is most likely a power issue. I tried to get away with a different power supply, which seems to have been foolish. Surprisingly, it managed to sync to about 300,000 block height before failing. Now, upon rebooting the Umbrel, it can’t even seem to connect to the SSD (I was able to log in via SSH and verify it can’t get seem to mount the SSD via the syslog).
So I’m considering this fixed. I have my official 3 amp Raspberry Pi power cord on the way. If that doesn’t do the trick, I’ll post another question in the future. Thanks everyone!
I am having the same problem since 5 hours ago. Then I found this thread, I tried to troubleshoot but it said no problems found. So I thought it needs to take a rest. I shut it down, restarted after one hour, and it’s still the same.
@edward Are you sure there are no error messages contained within the troubleshooting log?
I, too, tried rebooting my node, but because I wasn’t getting enough power to the SSD, it couldn’t even finish loading the web UI after reboot. I was also able to see additional error messages by SSHint into the node and running less /var/log/sysylog. (I may have that path slightly wrong).
If you are still able to get into the web UI after rebooting, then I think your problem might be caused by something different than my problem (though it has some similar symptoms).
Attaching to tor
tor | May 11 15:32:39.000 [notice] Bootstrapped 56% (loading_descriptors): Loading relay descriptors
tor | May 11 15:32:51.000 [notice] Bootstrapped 63% (loading_descriptors): Loading relay descriptors
tor | May 11 15:32:51.000 [notice] Bootstrapped 73% (loading_descriptors): Loading relay descriptors
tor | May 11 15:32:51.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor | May 11 15:32:51.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor | May 11 15:32:51.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor | May 11 15:32:52.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor | May 11 15:32:52.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor | May 11 15:32:52.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor | May 11 15:32:53.000 [notice] Bootstrapped 100% (done): Done
tor | May 11 15:33:01.000 [warn] Guard NTH101 ($B5558CFA70A5308582B25767C9698E6DBE6A90B2) is failing an extremely large amount of circuits. This could indicate a route manipulation attack, extreme network overload, or a bug. Success counts are 3/151. Use counts are 2/2. 3 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
tor | May 11 15:33:01.000 [warn] Guard NTH101 ($B5558CFA70A5308582B25767C9698E6DBE6A90B2) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 60/176. Use counts are 50/50. 60 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
tor | May 11 15:33:07.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 175 buildtimes.
tor | May 11 15:33:13.000 [notice] Guard NTH101 ($B5558CFA70A5308582B25767C9698E6DBE6A90B2) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 172/246. Use counts are 107/107. 172 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
tor | May 11 15:33:18.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:8333. Giving up. (waiting for rendezvous desc)
tor | May 11 15:33:28.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 221 buildtimes.
tor | May 11 15:33:38.000 [notice] We tried for 16 seconds to connect to ‘[scrubbed]’ using exit $6C143720FFF8469EF6A5C5B4066366340CF6C0D1~CalyxInstitute11 [FdTUD/tdltCelNIzLovsjNXKAPcq9mRAe6g1LvmDa0U] at 162.247.74.27. Retrying on a new circuit.
tor | May 11 15:34:06.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $8D912126FA40BD67EE7D5759BD19459450AEBEA1~BTCdonate [eEQWk3aM6dt+lc5MhG2tFf0j7mrj1Rnb4ni2hv47OTQ] at 46.41.148.75. Retrying on a new circuit.
tor | May 11 15:34:22.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $7761DDC7EB1BE26D4155F74A15F12C32A36FE0F2~CalyxInstitute09 [4aRzZCjmx6QGX3dlt+/VsTv4jOssd2aFdKSapiOoDSE] at 162.247.74.217. Retrying on a new circuit.
tor | May 11 15:34:46.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $3C89C80E2699FB6358BBB64FDC9547AFCB5C03F7~F3Netze [l1jD02S9qTqbElak0IR7Ea+Ov+bvuagFT8G53EVDbDY] at 185.220.100.240. Retrying on a new circuit.
tor | May 11 15:35:02.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $09F3067452D8D1DAFD33D0524A41DBF5295D3472~BASIS [BKYa/dCKhERRVp1fkwga8Ugwo1SqLL78IHBKTeck4Rw] at 45.125.65.118. Retrying on a new circuit.
tor | May 11 15:35:02.000 [notice] Tried for 123 seconds to get a connection to [scrubbed]:8333. Giving up.
tor | May 11 15:59:03.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $887CAB501A9DB68A2C44EDF98BF50B0304EED8B6~niftykostchtchie [aOmsqBCzWvW9eV9YaqzEpjf+iVobicNGwngG9OQgyK8] at 185.220.100.249. Retrying on a new circuit.
tor | May 11 15:59:18.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $08B73526414F3716C1CC5555411B35EB8DA50607~Hungary [XU52+RBWDFxttZ1woAJEp+tdRhBcQ4H48UlZWgdCJpE] at 91.219.237.21. Retrying on a new circuit.
tor | May 11 15:59:33.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $883A95D02E7EDE21640937FE74690B76B780DF66~squashbee [dh3xSd00k6MG7KjaMF/lTl+t7mc5K2f/JtzUuhC9Iok] at 51.75.122.240. Retrying on a new circuit.
tor | May 11 15:59:48.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $B0DD527BE01842D46030265FBD9928217A709F28~AccessNow005 [LvDyBh+ChAfMht/nQL5uXBndA78Vlb/6rik5jRAJN0I] at 176.10.99.205. Retrying on a new circuit.
tor | May 11 16:00:03.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $1AD9B8DAAC9CB67AD51D5B3BEE95C29D442FC4C6~CdgExitRelay [OF3l1x/gmJDskLAtIHvcAQucr4DspG3u1PIK3VnJa20] at 195.154.56.235. Retrying on a new circuit.
tor | May 11 16:00:18.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $08CE3DBFDAA27DB6C044A677AF68D7235C2AFC85~DigiGesTor4e4 [1vwKVjDxpr5w8yPeR391Rh7RWo3Zfzl1wEYqJ/EBv2c] at 195.176.3.20. Retrying on a new circuit.
tor | May 11 16:00:37.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $7B87EF57DAC332D7016C04AE82063E93B5162C44~Unnamed [l9j+jEhVfS4sy8SBBZ1m7obFwD256dW0yYrCgSnJluQ] at 51.158.65.243. Retrying on a new circuit.
tor | May 11 16:00:37.000 [notice] Tried for 132 seconds to get a connection to [scrubbed]:8333. Giving up.
==== Result ====
The debug script did not automatically detect any issues with your Umbrel.
This is what it says.
Don’t worry I have no sats inside yet.
Did anyone fix this issue? I am having the same issue as OP. My node stopped synchronizing and now just animates back and forth but doesn’t synch. I tried the reindex command and now the synchronized progress is 0% instead of 99.97%, which is what it was.
