LND Channels not connecting after reboot

Support and Troubleshooting
1

Can’t seem to get any of my channels to reconnect after a reboot. No changes or updates have been made recently to my node so was surprised to see it not boot right back up.

Bitcoin core seems to be fine and synching successfully and I am able to SSH in as well as access the Umbrel dashboard on my web browser via umbrel.local. Over the last couple of days I’ve worked my way through the Umbrel Troubleshooting guide without any success going as far as even reflashing. Not sure what else to try at this point. Been looking at my umbrel logs (attached) and lnd logs in detail. Any help guidance would be appreciated.

I have done the following with no success:

cd ~/umbrel
sudo ./scripts/stop
sudo ./scripts/start

No luck

cd ~/umbrel && docker-compose restart tor_server
cd ~/umbrel && docker-compose restart lnd

Waited many hours to make sure everything was synched. Still no luck.

  1. Performed a standard Restart from Umbrel Settings page. No luck

  2. Manually backed up my lnd.conf and rebooted letting umbrel generate a new default one. I didn’t make any changes recently to my lnd.conf but wanted to make sure it wasn’t the issue. Still no luck.

sudo systemctl stop umbrel-startup.service && docker system prune --force --all && sudo systemctl start umbrel-startup.service

No luck

  1. Reflashed

Still no luck. All of these bring me to the same point. LND shows ‘Running’, Lighting Wallet shows ‘Active’, but Channel Connections remain ‘0 Active’.

Please see attached log. Appreciate any help.
umbrel-1646061596137-debug.log (35.3 KB)

2 Likes
2

Also ran these two:

~/umbrel/bin/bitcoin-cli -getinfo
~/umbrel/bin/lncli getinfo

Results below. Seeing a ‘False’ for synch to chain…

umbrel@umbrel:~ $ ~/umbrel/bin/bitcoin-cli -getinfo
{
“version”: 220000,
“blocks”: 725305,
“headers”: 725305,
“verificationprogress”: 0.9999993547165158,
“timeoffset”: -3,
“connections”: {
“in”: 1,
“out”: 11,
“total”: 12
},
“proxy”: “10.21.21.11:9050”,
“difficulty”: 27967152532434.23,
“chain”: “main”,
“relayfee”: 0.00001000,
“warnings”: “”
}

umbrel@umbrel:~ $ ~/umbrel/bin/lncli getinfo
{
“version”: “0.14.2-beta commit=v0.14.2-beta”,
“commit_hash”: “1e511be523eb8e97c4e2d9c89a7a263963a3929f”,
“identity_pubkey”: “029ae209ee2fbd90df6551b2929f275631c28908837c9069df137fe28db927062a”,
“alias”: “AZBTC21”,
“color”: “#3399ff”,
“num_pending_channels”: 0,
“num_active_channels”: 0,
“num_inactive_channels”: 47,
“num_peers”: 0,
“block_height”: 725305,
“block_hash”: “00000000000000000008d0f8915f591650ca4950451592511446028f36484843”,
“best_header_timestamp”: “1646066077”,
“synced_to_chain”: false,
“synced_to_graph”: false,
“testnet”: false,
“chains”: [
{
“chain”: “bitcoin”,
“network”: “mainnet”
}
],
“uris”: [
],
“features”: {
“0”: {
“name”: “data-loss-protect”,
“is_required”: true,
“is_known”: true
},
“5”: {
“name”: “upfront-shutdown-script”,
“is_required”: false,
“is_known”: true
},
“7”: {
“name”: “gossip-queries”,
“is_required”: false,
“is_known”: true
},
“9”: {
“name”: “tlv-onion”,
“is_required”: false,
“is_known”: true
},
“12”: {
“name”: “static-remote-key”,
“is_required”: true,
“is_known”: true
},
“14”: {
“name”: “payment-addr”,
“is_required”: true,
“is_known”: true
},
“17”: {
“name”: “multi-path-payments”,
“is_required”: false,
“is_known”: true
},
“19”: {
“name”: “wumbo-channels”,
“is_required”: false,
“is_known”: true
},
“23”: {
“name”: “anchors-zero-fee-htlc-tx”,
“is_required”: false,
“is_known”: true
},
“30”: {
“name”: “amp”,
“is_required”: true,
“is_known”: true
},
“31”: {
“name”: “amp”,
“is_required”: false,
“is_known”: true
},
“45”: {
“name”: “explicit-commitment-type”,
“is_required”: false,
“is_known”: true
},
“2023”: {
“name”: “script-enforced-lease”,
“is_required”: false,
“is_known”: true
}
}
}

1 Like
3

Try disabling WT client from lnd.conf (just add # at the beginning of the lines) and restart lnd
See then how is doing.
If it started fine, just change your WT with another one.
Here is a list

4

Thanks. Trying right now.

5

Unfortunately, disabling the watch towers in lnd.conf and restarting lnd did not work. Same issue remains.

6

Just tried sudo rm -rf lnd/tls* && rm -f lnd/lnd.conf && sudo scripts/configure as well. It is now trying to synchronize for the last 15 minutes. Will be patient and see if it clears.

7

check the logs
SSH
cd umbrel
docker-compose logs bitcoin
docker-compose logs lnd
docker-compose logs electrs

8

Thanks DarthCoin. Checked all three logs. Below is what I have found. Appreciate any thoughts or guidance you have.

  1. electrs - Only information logs similar to below. I don’t believe anything looks suspect:

electrs | [2022-03-01T00:56:28.194Z INFO electrs::index] indexing 1 blocks: [725359…725359]
electrs | [2022-03-01T00:56:28.376Z INFO electrs::chain] chain updated: tip=0000000000000000000926dc2cd9bf8ef002c2a2b162ad5de93687c39d3d50bb, height=725359

  1. lnd - Primarily information logs but do see an error. Although I think it might have occurred a few hours ago before i turned off the watch tower:

lnd | 2022-02-28 21:13:45.793 [ERR] LTND: Unable to lookup witness: no witnesses
lnd | 2022-03-01 00:56:29.903 [INF] UTXN: Attempting to graduate height=725359: num_kids=0, num_babies=0

  1. bitcoin - Seeing some Socks5 general failures. Not sure what to think of them:

-02-28T23:44:10Z’ progress=1.000000 cache=29.1MiB(220505txo)
bitcoin | 2022-02-28T23:46:49Z Socks5() connect to 2001:7d0:82f8:e100:34b7:81ad:a73e:fea1:8333 failed: general failure
bitcoin | 2022-02-28T23:47:10Z Socks5() connect to 67.54.185.35:8333 failed: general failure
bitcoin | 2022-02-28T23:48:28Z Socks5() connect to 2603:6080:a240:1af::117b:8333 failed: general failure
bitcoin | 2022-03-01T00:56:50Z Socks5() connect to 80.255.7.71:8333 failed: connection refused
bitcoin | 2022-03-01T00:58:45Z New outbound peer connected: version: 70015, blocks=725359, peer=61 (block-relay-only)

9

No these are not errors. Nothing to worry about these, are normal.
Look deeper into logs.

10

Hi DarthCoin - Would it be okay to post/attach my logs here for review assistance? Is there anything in these logs that I should not make public? Thanks.

11

Sure, paste them into a 0bin.net and post the link here.
Nothing to worry about privacy or something like that, there’s is no personal data into those logs.

12

DarthCoin - Is there another option than 0bin.net? When I upload the text or even try the file it keeps choking on it and giving a code coloration error which will not resolve.

13

I was able to upload them here. Let me know if you cannot access. Thanks for all your assistance: https://pastebin.com/aJ5SVxMK

14

I don’t see any suspicious thing. Just let it like that for a while.

15

Thanks for checking DarthCoin. I will continue to let it be and hope for the best. It has already been many hours but I will be patient.

16

Hi DarthCoin - Still no change. Issue persists. Any other next steps or suggestions? Thanks.

17

In troubleshooting manual see the sections:

  • One Umbrel App do not start or it can’t be installed
  • After a bad shutdown, the node is not syncing
  • Some docker component fail to start
  • Several docker services could not start - Failed to start containers
  • I updated my Umbrel but it stuck in finish it

All of them are about how to reconfigure the node apps and settings (without losing any user data).
Try those.

18

Working through each of these troubleshooting steps again even though I have already done some of them. I did see many wallet locked entries in lnd log. Here is what it looks like. It does say it opened the wallet but then immediately see a couple of errors. Should this be a concern?

lnd | 2022-03-02 18:34:26.128 [ERR] RPCS: [/lnrpc.Lightning/PendingChannels]: wallet locked, unlock it to enable full RPC access
lnd | 2022-03-02 18:34:26.130 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
lnd | 2022-03-02 18:34:26.196 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: wallet locked, unlock it to enable full RPC access
lnd | 2022-03-02 18:34:26.198 [ERR] RPCS: [/lnrpc.Lightning/PendingChannels]: wallet locked, unlock it to enable full RPC access
lnd | 2022-03-02 18:34:31.618 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
lnd | 2022-03-02 18:34:32.097 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
lnd | 2022-03-02 18:34:32.156 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
lnd | 2022-03-02 18:34:35.445 [INF] LNWL: Opened wallet
lnd | 2022-03-02 18:34:35.774 [INF] CHRE: Primary chain is set to: bitcoin
lnd | 2022-03-02 18:34:36.056 [ERR] LTND: unable to create partial chain control: status code: 401, response: “”
lnd | 2022-03-02 18:34:36.056 [ERR] LTND: Shutting down because error in main method: error creating wallet config: unable to create partial chain control: status code: 401, response: “”
lnd | 2022-03-02 18:34:36.511 [INF] LTND: Shutdown complete
lnd |
lnd | error creating wallet config: unable to create partial chain control: status code: 401, response: “”
lnd | 2022-03-02 18:34:38.355 [INF] LTND: Version: 0.14.2-beta commit=v0.14.2-beta, build=production, logging=default, debuglevel=info
lnd | 2022-03-02 18:34:38.356 [INF] LTND: Active chain: Bitcoin (network=mainnet)
lnd | 2022-03-02 18:34:38.359 [INF] RPCS: RPC server listening on 0.0.0.0:10009
lnd | 2022-03-02 18:34:38.363 [INF] RPCS: gRPC proxy started at 0.0.0.0:8080
lnd | 2022-03-02 18:34:38.363 [INF] LTND: Opening the main database, this might take a few minutes…
lnd | 2022-03-02 18:34:38.363 [INF] LTND: Opening bbolt database, sync_freelist=false, auto_compact=false
lnd | 2022-03-02 18:34:39.073 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd | 2022-03-02 18:34:41.187 [ERR] RPCS: [/lnrpc.Lightning/WalletBalance]: waiting to start, RPC services not available
lnd | 2022-03-02 18:34:41.255 [ERR] RPCS: [/lnrpc.Lightning/GetTransactions]: waiting to start, RPC services not available
lnd | 2022-03-02 18:34:41.257 [ERR] RPCS: [/lnrpc.Lightning/PendingChannels]: waiting to start, RPC services not available
lnd | 2022-03-02 18:34:41.257 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: waiting to start, RPC services not available
lnd | 2022-03-02 18:34:41.258 [ERR] RPCS: [/lnrpc.Lightning/ListInvoices]: waiting to start, RPC services not available
lnd | 2022-03-02 18:34:41.259 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd | 2022-03-02 18:34:41.334 [ERR] RPCS: [/lnrpc.Lightning/ListPayments]: waiting to start, RPC services not available

19

Seems like it was definitely locked. So I ran the instructed bash command and lncli. Unfortunately it wouldn’t unlock so ran:

Make a backup of your current lnd.conf

cp ~/umbrel/lnd/lnd.conf ~/umbrel/lnd/lnd.bak

Delete your current lnd.conf, re-configure Umbrel and restart the node

rm ~/umbrel/lnd/lnd.conf && ~/umbrel/scripts/configure && sudo reboot

I’m rebooted now and no longer have the wallet lock issue. However, still no channels connecting. Will continue working my way through the other troubleshooting sections you provided.

20

Hi DarthCoin,

Ok I have gone through and successfully executed all five items from the troubleshooting manual you suggested:

  • One Umbrel App do not start or it can’t be installed
  • After a bad shutdown, the node is not syncing
  • Some docker component fail to start
  • Several docker services could not start - Failed to start containers
  • I updated my Umbrel but it stuck in finish it

At one point I did have a wallet locking issue which I was also able to resolve and get past using the instructions in the troubleshooting manual.

Unfortunately, my issue still remains. Bitcoin Core is running fine and LND is stuck with zero channels connecting… The Umbrel log says everything checks out ok and the Umbrel dashboard for Bitcoin/LND all say running, active, and synchronized. All to the latest block height on both Bitcoin and LND against the latest mempool block.

What are the next steps or suggestions you have? Thanks for all your guidance. Really appreciate it.