-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug]: Channel stuck in inactive state. #9468
Comments
Please share the logs of your node, set the In anyways we need logs to tell whats going on. |
Let me know if you need |
I identified the problem in the btcwallet/neutrino package, seems like we are forgetting to mark a finsihed rescan as done here: This needs a fix in the btcwallet/neutriono package, in the meantime you can try to either use a pruned bitcoind node as a backend or switch off the watchtower client for a bit until the fix is released. |
I don't really understand the problem you are describing but if I follow your suggestion and switch the watchtower client off could I switch it back on again or will the issue return when the watchtower client turns on again? |
So yes for now it seems that you have to switch off the client for now until the fix is out (not restarting the client but keeping it off). Or you switch the backend to maybe bitcoind pruned until the fix is released. Can you provide logs for of the |
Would you be able to run a patched version of your LND node ? |
Hi Ziggie1984, sorry for the slow reply. |
So what would be very helpful in the first place is, that you change the debug level of your LND and provide us with the full logs, you can read more about how to do that in https://docs.lightning.engineering/lightning-network-tools/lnd/debugging_lnd If you have questions feels free to reach out. We need to understand why the rescanning process which is a long-lasting process interrupted. |
Background
Opened a channel to node Kraken (02f1a8c87607f415c8f22c00593002775941dea48869ce23096af27b0cfdcc0b69@52.13.118.208:9735) using lightning terminal.
Channel point https://mempool.space/tx/ed081cd6744ebdcca9a498a22925dcc7bf6ad7cae9f367c59e79fa2b85c94848#vout=0 has received sufficient confirmations that channel should be opened and active.
Channel info is as follows.
{
"active": false,
"remote_pubkey": "02f1a8c87607f415c8f22c00593002775941dea48869ce23096af27b0cfdcc0b69",
"channel_point": "ed081cd6744ebdcca9a498a22925dcc7bf6ad7cae9f367c59e79fa2b85c94848:0",
"chan_id": "969449297852235776",
"capacity": "5000000",
"local_balance": "4997943",
"remote_balance": "0",
"commit_fee": "1727",
"commit_weight": "772",
"fee_per_kw": "1243",
"unsettled_balance": "0",
"total_satoshis_sent": "0",
"total_satoshis_received": "0",
"num_updates": "0",
"pending_htlcs": [],
"csv_delay": 600,
"private": false,
"initiator": true,
"chan_status_flags": "ChanStatusDefault",
"local_chan_reserve_sat": "50000",
"remote_chan_reserve_sat": "50000",
"static_remote_key": false,
"commitment_type": "ANCHORS",
"lifetime": "21136",
"uptime": "21136",
"close_address": "",
"push_amount_sat": "0",
"thaw_height": 0,
"local_constraints": {
"csv_delay": 600,
"chan_reserve_sat": "50000",
"dust_limit_sat": "354",
"max_pending_amt_msat": "4950000000",
"min_htlc_msat": "1000",
"max_accepted_htlcs": 50
},
"remote_constraints": {
"csv_delay": 600,
"chan_reserve_sat": "50000",
"dust_limit_sat": "354",
"max_pending_amt_msat": "4950000000",
"min_htlc_msat": "1",
"max_accepted_htlcs": 483
},
"alias_scids": [],
"zero_conf": false,
"zero_conf_confirmed_scid": "0",
"peer_alias": "Kraken 🐙⚡",
"peer_scid_alias": "0",
"memo": "",
"custom_channel_data": ""
}
Your environment
lncli version 0.18.4-beta commit=lightning-terminal-v0.14.0-alpha
Linux lnl-node 6.8.0-51-generic #52-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 5 13:09:44 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Neutrino backend
Steps to reproduce
Unsure how to reproduce issue.
Expected behaviour
Channel should be active.
Actual behaviour
Channel active state remains false after sufficient confirmations.
The text was updated successfully, but these errors were encountered: