Bitcoin Node stuck “Starting”

[merkel]

Hello,

After i updated Bitcoin Core to version 25.0 my node is stuck in starting.
Already tried this: Bitcoin Node stuck "Starting" which didn’t work, also deleted the peers.dat file.

Attaching to bitcoin_server_1, bitcoin_bitcoind_1, bitcoin_app_proxy_1, bitcoin_i2pd_daemon_1, bitcoin_tor_1, bitcoin_tor_server_1
app_proxy_1 | yarn run v1.22.19
app_proxy_1 | $ node ./bin/www
app_proxy_1 | [HPM] Proxy created: / → http://10.21.22.2:3005
app_proxy_1 | Waiting for 10.21.22.2:3005 to open…
app_proxy_1 | Bitcoin Node is now ready…
app_proxy_1 | Listening on port: 2100
bitcoind_1 | 2023-08-03T14:21:05Z P2P peers available. Skipped DNS seeding.
bitcoind_1 | 2023-08-03T14:21:05Z dnsseed thread exit
bitcoind_1 | 2023-08-03T14:21:49Z New outbound peer connected: version: 70016, blocks=801522, peer=4 (outbound-full-relay)
bitcoind_1 | 2023-08-03T14:21:53Z New outbound peer connected: version: 70015, blocks=801522, peer=6 (outbound-full-relay)
bitcoind_1 | 2023-08-03T14:21:54Z New outbound peer connected: version: 70016, blocks=801520, peer=5 (outbound-full-relay)
bitcoind_1 | 2023-08-03T14:21:59Z New outbound peer connected: version: 70016, blocks=801520, peer=7 (outbound-full-relay)
bitcoind_1 | 2023-08-03T14:21:59Z Socks5() connect to 156.146.57.54:8333 failed: general failure
bitcoind_1 | 2023-08-03T14:22:03Z Socks5() connect to 103.211.229.164:8333 failed: general failure
bitcoind_1 | 2023-08-03T14:22:13Z New outbound peer connected: version: 70016, blocks=801522, peer=8 (outbound-full-relay)
bitcoind_1 | 2023-08-03T14:22:15Z New outbound peer connected: version: 70016, blocks=801522, peer=9 (outbound-full-relay)
i2pd_daemon_1 | 14:15:59@245/error - Tunnels: Can’t select next hop for 27wfI1wBkp-5jDSPmtCiOuIBacgMxFbW0QxYpK1GpII=
i2pd_daemon_1 | 14:15:59@245/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 14:16:04@245/error - Tunnels: Can’t select next hop for cpmWqPCbXtSErUYtHJOvFRgmwAmWi3SEhJu2gWkkA~o=
i2pd_daemon_1 | 14:16:04@245/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 14:16:15@245/error - Tunnels: Can’t select next hop for SyxHJSTkTWOJtL5y4cLoXXmv2DPGN93MGxrROW3wDgk=
i2pd_daemon_1 | 14:16:15@245/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 14:16:49@245/error - Tunnels: Can’t select next hop for F0uj0A491am6CvTOWFkLEA1MwnEosiV5XjtybUPeiQo=
i2pd_daemon_1 | 14:16:49@245/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 14:20:55@485/error - SAM: Read error: End of file
i2pd_daemon_1 | 14:21:20@485/error - Destination: Can’t publish LeaseSet. Destination is not ready
server_1 | yarn run v1.22.18
server_1 | $ node ./bin/www
server_1 | Thu, 03 Aug 2023 14:16:05 GMT morgan deprecated morgan(options): use morgan(“default”, options) instead at app.js:33:9
server_1 | Thu, 03 Aug 2023 14:16:05 GMT morgan deprecated default format: use combined format at app.js:33:9
server_1 | Listening on port 3005
tor_1 | Aug 03 14:16:19.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor_1 | Aug 03 14:16:19.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor_1 | Aug 03 14:16:19.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor_1 | Aug 03 14:16:19.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor_1 | Aug 03 14:16:19.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_1 | Aug 03 14:16:19.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_1 | Aug 03 14:16:24.000 [notice] Bootstrapped 100% (done): Done
tor_1 | Aug 03 14:20:59.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor_1 | Aug 03 14:21:59.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor_1 | Aug 03 14:22:03.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.

How can i fix this?

[smolgrrr]

Nothing stands out here, any chance you could share the full logs (guide here)

sudo ~/umbrel/scripts/debug

This issue is usually one of the following errors

@usernameisJim

LevelDB read failure: Corruption: block checksum mismatch: /data/.bitcoin/chainstate/1066593.ldb

Solution is here under “Resolving Corrupted Blockchain Issues”

A peers.dat error can be resolved with these steps

Or a settings.json error can be resolved with these steps

[my_bitcoin]

sometimes the settings.json gets corrupted too. post up your logs like the other person mentioned

[merkel]

Thanks for your reply.

So yesterday i figured out that there was something with i2pd:
i2pd_daemon_1 | 17:14:07@529/none - i2pd v2.44.0 (0.9.56) starting…
i2pd_daemon_1 | 17:14:19@315/error - Tunnels: Can’t select next hop for bzIGdwRKxGwy09U~S8mTl9~RMsDjFy5W-c2O-sojBs0=
i2pd_daemon_1 | 17:14:19@315/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 17:14:19@315/error - Tunnels: Can’t select next hop for bzIGdwRKxGwy09U~S8mTl9~RMsDjFy5W-c2O-sojBs0=
i2pd_daemon_1 | 17:14:19@315/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 17:14:19@315/error - Tunnels: Can’t select next hop for bzIGdwRKxGwy09U~S8mTl9~RMsDjFy5W-c2O-sojBs0=
app_proxy_1 | Validating token: 7f34e5ecc39b …
app_proxy_1 | Validating token: 7f34e5ecc39b …
app_proxy_1 | Validating token: 7f34e5ecc39b …
app_proxy_1 | Validating token: 7f34e5ecc39b …
app_proxy_1 | Validating token: 7f34e5ecc39b …
app_proxy_1 | Validating token: 7f34e5ecc39b …
i2pd_daemon_1 | 17:14:19@315/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 17:15:05@128/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
app_proxy_1 | Validating token: 7f34e5ecc39b …
app_proxy_1 | Validating token: 7f34e5ecc39b …

So i deleted the i2pd container. Now Bitcoin Core is not starting at all.

Here are the logs:

= Umbrel debug info =Umbrel version0.5.4Flashed OS versionv0.5.4Ra -...

[smolgrrr]

try running sudo ./scripts/app update bitcoin and then rebooting your Umbrel after it’s done

[merkel]

Thanks for your reply. When i run that command i get: ‘‘command not found’’ What is the right command?

[smolgrrr]

Apologies, you need to change directory first.

cd umbrel
sudo ./scripts/app update bitcoin

[merkel]

Thanks, when i run that command i got the following errors:

Do you know what i should do with those errors, remove them manual?

[smolgrrr]

That’s fine, if you reboot your node (sudo reboot) and try to open the Bitcoin app does it work now?

[merkel]

Thanks, that worked. I can see my on-chain balance now. The strange thing is that the channels are force closed (happened when i try to recover it in Blix Wallet).

mempool - Bitcoin Explorer

But somehow LND is unable to find the node according to the logs: ====================== Umbrel debug info ======================Umbrel ve - Pastebin.com

[smolgrrr]

Ah yeah that sucks, you can double check but Blixt probably closed them.

@usernameisJim

You can prepend all commands for lncli like so:
sudo ~/umbrel/scripts/app compose lightning exec lnd lncli

You can use this command to see status of channels:
~/umbrel/scripts/app compose lightning exec lnd lncli pendingchannels

Any channels stuck in waiting close with a problematic peer you can attempt to force close: ~/umbrel/scripts/app compose lightning exec lnd lncli closechannel --force

Steps for Waiting Close Channels and Unconfirmed Transactions

Please share your best tips on resolving Waite Close and Unconfirmed Transactions! Here’s some helpful ways, This is typically the process to bump/get funds out of waiting close channels: You can prepend all commands for lncli like so: sudo ~/umbrel/scripts/app compose lightning exec lnd lncli For details on “accessing the lncli” (which is what we’re doing here to interact with LND) As well as details on how to run the commands on your Umbrel you can reference instructions under “How to …

[merkel]

Thanks, when i do lncli listchannels i see the 4 channels.

So i tried to force close one, and i got: [lncli] rpc error: code = Unknown desc = server is still in the process of starting

That indicates to me that there is still something wrong, do you know what it could be?

Also according to on-chain data the channels are allready closed

[usernameisJim]

Hey @merkel is your application still stuck on “Starting” and won’t open, or opens and is blank?

Can you reshare a new debug log and also share the output of this command?

~/umbrel/scripts/app compose bitcoin logs --tail 600

It will be a lot of text so can upload as a text file/ or paste it to pastebin.com and share a link for easier review

Can you recall the steps you took in Blixt wallet to confirm, and we can make sure Bitcoin and Lightning Node app are running to see what’s going on with the channels now, let us know and we can try and rescue those channels!