Node constantly syncing

Randomly for the past several days when I log into my Umbrel everything just says syncing. I’ve restarted and no luck, the only change that has happened is I uninstalled an app.

I see issues with overloaded circuits from Tor. Log output below, any ideas?

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

Umbrel version

0.3.14

Networking information
Docker containers

NAMES STATUS
btcpay-server_web_1 Up 6 minutes
bluewallet_lndhub_1 Restarting (3) 50 seconds ago
btcpay-server_postgres_1 Up 6 minutes
btcpay-server_nbxplorer_1 Up 6 minutes
lightning-terminal_web_1 Restarting (1) 15 seconds ago
bluewallet_redis_1 Up 6 minutes
middleware Up 7 minutes
bitcoin Up 27 seconds
lnd Restarting (2) 47 seconds ago
nginx Up 7 minutes
manager Up 7 minutes
dashboard Up 7 minutes
tor Up 7 minutes
electrs Up 7 minutes

bitcoin | 2021-08-01T19:05:31Z init message: Verifying blocks…
bitcoin | 2021-08-01T19:05:31Z Verifying last 6 blocks at level 3
bitcoin | 2021-08-01T19:05:31Z [0%]…LevelDB read failure: Corruption: not an sstable (bad magic number)
bitcoin | 2021-08-01T19:05:31Z Fatal LevelDB error: Corruption: not an sstable (bad magic number)
bitcoin | 2021-08-01T19:05:31Z You can use -debug=leveldb to get more complete diagnostic messages
bitcoin | 2021-08-01T19:05:31Z Fatal LevelDB error: Corruption: not an sstable (bad magic number)
bitcoin | 2021-08-01T19:05:31Z : Error opening block database.
bitcoin | Please restart with -reindex or -reindex-chainstate to recover.
bitcoin | 2021-08-01T19:05:31Z Aborted block database rebuild. Exiting.
bitcoin | 2021-08-01T19:05:31Z Shutdown: In progress…
bitcoin | : Error opening block database.
bitcoin | Please restart with -reindex or -reindex-chainstate to recover.

LND logs

Attaching to lnd
lnd | 2021-08-01 19:02:52.536 [INF] LTND: Opening bbolt database, sync_freelist=false, auto_compact=false
lnd | panic: freepages: failed to get all reachable pages (page 3846: multiple references)
lnd |
lnd | panic: freepages: failed to get all reachable pages (page 3846: multiple references)
lnd |
lnd | goroutine 7 [running]:

lnd | 2021-08-01 19:04:56.368 [INF] LTND: Version: 0.12.1-beta commit=v0.12.1-beta, build=production, logging=default, debuglevel=info
lnd | 2021-08-01 19:04:56.368 [INF] LTND: Active chain: Bitcoin (network=mainnet)
lnd | 2021-08-01 19:04:56.368 [INF] LTND: Opening the main database, this might take a few minutes…
lnd | 2021-08-01 19:04:56.368 [INF] LTND: Opening bbolt database, sync_freelist=false, auto_compact=false
lnd | panic: freepages: failed to get all reachable pages (page 3846: multiple references)

Tor logs

tor | Aug 01 18:58:52.000 [warn] Guard lstorfin7 ($CC4B230B6B74C218E73E959B733DDABF673961A5) is failing an extremely large amount of circuits. This could indicate a route manipulation attack, extreme network overload, or a bug. Success counts are 2/151. Use counts are 0/0. 2 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
tor | Aug 01 18:59:12.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 184 buildtimes.
tor | Aug 01 18:59:13.000 [notice] Guard lstorfin7 ($CC4B230B6B74C218E73E959B733DDABF673961A5) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 184/263. Use counts are 107/107. 184 circuits completed, 0 were unusable, 0 collapsed, and 22 timed out. For reference, your timeout cutoff is 60 seconds.
tor | Aug 01 18:59:13.000 [warn] Guard lstorfin7 ($CC4B230B6B74C218E73E959B733DDABF673961A5) 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 149/299. Use counts are 107/107. 149 circuits completed, 0 were unusable, 0 collapsed, and 6 timed out. For reference, your timeout cutoff is 60 seconds.
tor | Aug 01 18:59:25.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 248 buildtimes.

Been having the same problem for the past couple of days. Syncing is at about 99% but gets to a certain block and then loops back to one 4 blocks previous. Did you manage to resolve this?

1 Like

Exact same issue here! Any solutions or ideas to cause?

Your blockchain is corrupted. Most likely you did a hard, not graceful shutdown like pulling the power plug while the blockchain was writing files to your disk. Try to avoid that in the future.

bitcoin | 2021-08-01T19:05:31Z Fatal LevelDB error: Corruption: not an sstable (bad magic number)
bitcoin | 2021-08-01T19:05:31Z : Error opening block database.
bitcoin | Please restart with -reindex or -reindex-chainstate to recover.

Check out what to do here: Blockchain data is corrupted, how can I fix it?.