My node is permanently syncing

Support and Troubleshooting
1

I’ve been meaning to fix this but I have had to take my node offline many times. I’m going to try again but I may have to take it down due to weather this week. The lightning app won’t open and the Bitcoin app is perma syncing. (Sorry for the bad summary, I built the node but I’m not a dev).

I think it’s stuck on parsing JSON files? Here are the errors from the log: How do I fix it? Thanks!

Attaching to bitcoin_server_1, bitcoin_bitcoind_1, bitcoin_tor_1, bitcoin_i2pd_daemon_1, bitcoin_app_proxy_1, bitcoin_tor_server_1
app_proxy_1 | Validating token: 707563c299ce …
app_proxy_1 | Validating token: 707563c299ce …
app_proxy_1 | Validating token: 707563c299ce …
app_proxy_1 | Validating token: 707563c299ce …
app_proxy_1 | Validating token: 707563c299ce …
app_proxy_1 | Validating token: 707563c299ce …
app_proxy_1 | Validating token: 707563c299ce …
app_proxy_1 | Validating token: 707563c299ce …
app_proxy_1 | Validating token: 707563c299ce …
app_proxy_1 | Validating token: 707563c299ce …
bitcoind_1 |
bitcoind_1 | Error: Failed loading settings file:
bitcoind_1 | - Unable to parse settings file /data/.bitcoin/settings.json
bitcoind_1 |
bitcoind_1 | Error: Failed loading settings file:
bitcoind_1 | - Unable to parse settings file /data/.bitcoin/settings.json
bitcoind_1 |
bitcoind_1 | Error: Failed loading settings file:
bitcoind_1 | - Unable to parse settings file /data/.bitcoin/settings.json
bitcoind_1 |
tor_1 | Mar 19 14:44:03.000 [notice] No circuits are opened. Relaxed timeout for circuit 4552 (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. [8 similar message(s) suppressed in last 10140 seconds]
tor_1 | Mar 19 16:04:03.000 [notice] No circuits are opened. Relaxed timeout for circuit 4621 (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. [5 similar message(s) suppressed in last 4800 seconds]
tor_1 | Mar 19 20:34:37.000 [notice] Heartbeat: Tor’s uptime is 3 days 18:00 hours, with 15 circuits open. I’ve sent 68.74 MB and received 63.47 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 50 connections with IPv4 and 0 with IPv6.
tor_1 | Mar 19 20:34:37.000 [notice] While bootstrapping, fetched this many bytes: 607325 (consensus network-status fetch); 14349 (authority cert fetch); 5776010 (microdescriptor fetch)
tor_1 | Mar 19 20:34:37.000 [notice] While not bootstrapping, fetched this many bytes: 2236941 (consensus network-status fetch); 79785 (authority cert fetch); 1670545 (microdescriptor fetch)
tor_1 | Mar 19 20:51:04.000 [notice] No circuits are opened. Relaxed timeout for circuit 4860 (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. [3 similar message(s) suppressed in last 17220 seconds]
tor_1 | Mar 19 22:00:05.000 [notice] No circuits are opened. Relaxed timeout for circuit 4924 (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. [3 similar message(s) suppressed in last 4140 seconds]
tor_1 | Mar 19 23:49:06.000 [notice] No circuits are opened. Relaxed timeout for circuit 5025 (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 6540 seconds]
tor_1 | Mar 20 00:58:01.000 [notice] No circuits are opened. Relaxed timeout for circuit 5060 (a Measuring circuit timeout 4-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [3 similar message(s) suppressed in last 4140 seconds]
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.5 - - [Mon, 20 Mar 2023 01:04:18 GMT] “GET /ping HTTP/1.1” 200 37 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Safari/605.1.15”
server_1 |
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.5 - - [Mon, 20 Mar 2023 01:04:18 GMT] “GET /v1/bitcoind/system/bitcoin-config HTTP/1.1” 200 212 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Safari/605.1.15”
server_1 |
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.5 - - [Mon, 20 Mar 2023 01:04:37 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 200 21 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Safari/605.1.15”
server_1 |
server_1 | umbrel-middleware
i2pd_daemon_1 | 00:05:21@150/error - NetDb: a45rymiF01eP-pSkFhLJRogQJM5UxY4jGoQLnDFec0c= destination requested, but no tunnels found
i2pd_daemon_1 | 00:06:59@150/error - NetDb: og1SF~KTVbb6H5~pWTSQY-T5hhh-iZZ7BbI7CiL47s0= destination requested, but no tunnels found
i2pd_daemon_1 | 00:07:15@150/error - NetDb: og1SF~KTVbb6H5~pWTSQY-T5hhh-iZZ7BbI7CiL47s0= destination requested, but no tunnels found
i2pd_daemon_1 | 00:07:48@560/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 00:08:19@560/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 00:09:59@150/error - NetDb: bUdB8LwUXUNlndH18u7kkIlu-0JtuJ1I90hgIQwEnzE= destination requested, but no tunnels found
i2pd_daemon_1 | 00:11:31@107/error - SSU2: RelayIntro unknown router to introduce
i2pd_daemon_1 | 00:29:50@395/error - Tunnel: Tunnel with id 1653039028 already exists
i2pd_daemon_1 | 00:30:25@395/error - Tunnel: Tunnel with id 195991766 already exists
i2pd_daemon_1 | 00:58:02@395/error - Tunnel: Tunnel with id 517765400 already exists

1 Like
2

Anyone? Bueller?

I had to take the node down again for weather. sigh. I will get this fixed though!

1 Like
3

Did you get this fixed?

I have similar problems. My CPU was runing at 100% all the time, I deleted most unnecessary apps (bitfeed, mempool, etc), and cpu seems to be better now. But I still notice many errors from i2p not connecting.I seem to not find much stuff about i2p online… I’m a bit curious if the proxy constantly validatin token is normal?

Try to address each problem one by one, at some point it will get solved.

4

If you check your debug logs you have the error:

Error: Failed loading settings file:
bitcoind_1 | - Unable to parse settings file /data/.bitcoin/settings.json

To resolve, first connect to your Umbrel device by following the instructions in How to SSH into Umbrel on a Raspberry Pi or by accessing a terminal on your Linux machine here: Official Umbrel Troubleshooting Guide and FAQ

This command is the quickest way to resolve the error, by deleting the file first:

rm ~umbrel/app-data/bitcoin/data/bitcoin/settings.json

Then you should restart Bitcoin:
~/umbrel/scripts/app restart bitcoin

If for any reason when attempting to delete the file you face a permission or other errors that prevent you from doing so, we can also edit the file with this command (performing this step has been more reliable then attempting the file deletion which often returns a permission denied error)

Run this command to edit/create the file:
sudo nano umbrel/app-data/bitcoin/data/bitcoin/settings.json

Then it will take you to a blank file and just type and add two lines like this, with the two curly braces

{
}

then hit CTRL+X to exit, Y to save, and enter to continue.

After completing the edit don’t forget the last step of restarting Bitcoin:
~/umbrel/scripts/app restart bitcoin

You can run that restart bitcoin command or within your Bitcoin Node app you can also click Save and Restart Node in Advanced Settings on the top right.

Upon restarting wait ~5 minutes and this will resolve the error with the settings.json file.

1 Like
5

feel free to share your debug log @beegarcwe can see if it’s the same error or something else