Pending channel with negative blocks_til_maturity #1610
Comments
|
Seems related to #1571. |
|
@vpecinka do you know if the sweep transaction is being broadcast? Has the problem persisted across restarts? Can you try restarting LND and looking for these logs with UTXN prefix? The latter is probably returning an error If you didn't initiate that payment, then someone probably routed a payment through you. |
|
Looking on chain, all outputs have been swept at this point. Is your lnd node still getting notifications from the chain backend? Are you using a bitcoind backend? If so, is it remote? |
|
I only see the first stage being confirmed, but the second layer sweep hasn't shown up, which seems consistent with the output in pendingchannels |
|
@cfromknecht I would guess my lnd and bitcoind are working fine. Both run locally under same user. How or where else can I verify it receives notifications? I also tried to restart LND, still having this pending channel. Output of all logs I have now: and for the second one: For context, I have |
|
This unconfirmed balance is related? I didn't notice it before lnd restart, however, I'm not sure. Maybe it was there... |
|
Here is all related to closing_txid and also this multiline dumps: and later one: |
|
@vpecinka thank you for your detailed logs, helped a bunch in figuring out what was going on have you had any luck since getting this sweep to confirm? |
|
@cfromknecht you're welcome. Unfortunately, it is still pending - I updated lnd to the I don't know if this helps and is related: this is from log in context of |
|
Have you tried lowering your |
|
Same issue here. I have |
|
I have minrelaytxfee=0 in my bitcoin.conf |
|
Working on a fix so that we can get these 2nd stage sweeps resigned and broadcast @brndnmtthws are you also seeing "min relay fee not met"? Is anyone else getting this with other backends? |
|
@brndnmtthws on restart, do you see |
|
@Roasbeef here's the log after restarting lnd: https://gist.github.com/brndnmtthws/ec67de5c57dbe09998cf903c60c426fc |
|
Logs show a rebroadcast by the nursery. Are you running |
|
@Roasbeef not running in blocks only mode. The tx appears to be in the mempool: |
|
@cfromknecht yes, I can see this: |
|
This is still a problem for me. It would appear that the issue is that the fee for the TX is too low, and won't be accepted by any other Bitcoin nodes. Here's the raw tx: Is there a way to force lnd to create a new tx with an appropriate fee? |
|
@brndnmtthws this is a problem at the latest version of |
|
Yes, latest. I tried and they all failed.
…On Thu, Aug 30, 2018, 20:06 Olaoluwa Osuntokun ***@***.***> wrote:
@brndnmtthws <https://github.com/brndnmtthws> this is a problem at the
*latest* version of lnd? You can take that raw tx and try to use the
existing API services that will push the tx for free (like blockchain.info
).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1610 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC-_BTv_YxrDOry2QMJCW476RIDxgGeSks5uWG_wgaJpZM4VbUnX>
.
|
|
@Roasbeef how can I get the raw tx? pending channels: but when asking bitcoind for the closing transaction or txid from pending_htlss, I get nothing. |
|
So is there a way to get lnd to regenerate the TX? I'm currently stuck because no other bitcoin nodes will relay the TX, thus the TX will never confirm (because the fee is below the default min relay fee). It's been stuck in this state for months, meaning I have a completely useless node where I can't transact, and there's about ~2 BTC locked up on it. |
|
@brndnmtthws 2 BTC? Every single one of you channels was closed before the fee floor was activated? Or is it that you have dependent spends from each of them? This PR implements logic for on-demand fee bumping when signing #1704 @vpecinka in order to get the transaction, you need to lower the min fee rate on your bitcoind node. Only at that point will it be accepted into the mempool. |
|
@Roasbeef Sweet, that PR looks like what I need. I haven't actually explicitly closed any channels myself, I've just let lnd run and do its thing. |
|
Oh gotcha. I mean that the channel you linked above was older, and was broadcast at the point where we didn't properly apply the fee floor. So if you close them now the fee floor will be properly enforced. I was getting at this comment:
You can't move the funds or send funds out of the wallet as is? |
|
@Roasbeef that's right, if I try to use Trying to force the channel to close again results in an error: |
|
The missing inputs is a distinct issue solved in master and can be
recovered if you're already afflicted by using the dropwtxmgr tool.
If the channel isn't found, then possibly check that you're targeting the
correct outpoint. As the channel has already been closed, it can't be
closed again in the db.
…On Wed, Sep 26, 2018, 2:40 PM Brenden Matthews ***@***.***> wrote:
@Roasbeef <https://github.com/Roasbeef> that's right, if I try to use lncli
sendcoins it fails because of missing inputs.
Trying to force the channel to close again results in an error:
***@***.***:/lnd# lncli closechannel --force 6bb225f1a7c4a1575bfe42342b4d8436b9a48cd64e32751d486e09fa3f819a90 1
[lncli] rpc error: code = Unknown desc = unable to find channel
***@***.***:/lnd#
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1610 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA87LnqD-i5e78DxIGBcwVoJEaROGjUzks5ue_RRgaJpZM4VbUnX>
.
|
|
I tried all the channel points and the result was the same: Is there a different way to determine the channel point? |
|
You can't force close channels that are already closed.
…On Wed, Sep 26, 2018, 3:11 PM Brenden Matthews ***@***.***> wrote:
I tried all the channel points and the result was the same:
***@***.***:/lnd# lncli pendingchannels
{
"total_limbo_balance": "4346",
"pending_open_channels": [
],
"pending_closing_channels": [
],
"pending_force_closing_channels": [
{
"channel": {
"remote_node_pub": "03e28223dc9b962d824c4a41dd6a2d178a72004594b87aa28cbfdf63e551fbef33",
"channel_point": "6bb225f1a7c4a1575bfe42342b4d8436b9a48cd64e32751d486e09fa3f819a90:1",
"capacity": "340000",
"local_balance": "3467",
"remote_balance": "0"
},
"closing_txid": "2db99f4220628fe1ea048176b5c4393ef1aac8b42f3f0275bd880e2769c98088",
"limbo_balance": "4346",
"maturity_height": 531032,
"blocks_til_maturity": -12182,
"recovered_balance": "3467",
"pending_htlcs": [
{
"incoming": false,
"amount": "2173",
"outpoint": "9762c96c8eab23c660d287eb3c65e8dc7ab53bfb49817d5a5ed4cfb011313745:0",
"maturity_height": 531041,
"blocks_til_maturity": -12173,
"stage": 2
},
{
"incoming": false,
"amount": "2173",
"outpoint": "dc36145b1bf6db7f68a2b23ef225bbcf257b3605d3298c54ac3018c29b069e60:0",
"maturity_height": 531041,
"blocks_til_maturity": -12173,
"stage": 2
}
]
}
],
"waiting_close_channels": [
]
}
***@***.***:/lnd# lncli closechannel --force 6bb225f1a7c4a1575bfe42342b4d8436b9a48cd64e32751d486e09fa3f819a90 1
[lncli] rpc error: code = Unknown desc = unable to find channel
***@***.***:/lnd# lncli closechannel --force 9762c96c8eab23c660d287eb3c65e8dc7ab53bfb49817d5a5ed4cfb011313745 0
[lncli] rpc error: code = Unknown desc = unable to find channel
***@***.***:/lnd# lncli closechannel --force dc36145b1bf6db7f68a2b23ef225bbcf257b3605d3298c54ac3018c29b069e60 0
[lncli] rpc error: code = Unknown desc = unable to find channel
***@***.***:/lnd#
Is there a different way to determine the channel point?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1610 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA87LmqresqWiDdq1YSuPEE4CC6Dp6sHks5ue_t_gaJpZM4VbUnX>
.
|
|
@Roasbeef I see. I understood your comment to mean "try closing them again to generate a new TX" or something of that nature. |
|
Just letting you know that I don't have pending channels any more... I don't know when and how it happend, however. I noticed it now after power outage and server reboot. Anyway, thanks a lot! |
|
I'm seeing this issue now too, apparently on a very old transaction that was confirmed a long time ago. Any ideas? Should I open a new issue? |
|
After having tried everything in this thread, the TX is still stuck: Strangely there's another TX ( What are my options here? How do I get this thing unstuck? Should I open another issue? FWIW, I'm able to send other transactions again (no longer getting the "missing inputs" error). |
|
@halseth Sorry I didn't see your message when you first posted. Do I need to be on debug level logging to see it on startup? I don't see anything like that with info. As an update, I do still have this pending force close channel running the latest from master |
|
I think I'm having a similar issue here, with The closing tx is broadcast and seems valid, just not sure if
|
|
@sangaman Yes, try setting @davidknezic Seems like the HTLC spend does not get confirmed. Can you also try setting |
|
Hi @halseth, thanks for helping out!
|
|
@davidknezic That's weird, looks like Could be a fee issues, but then we should see an error. Do you have access to you bitcoin full node logs, to see how it handles the tx when it receives it? |
|
Which backend are you using btw? |
|
Bumping this thread to notify y'all that #1960 has been merged which should unstick the outputs! |
|
Can confirm, appears to be fixed. Thanks for the fine work. This is gentlemen. |
|
Great! My stuck pending channels are gone too. It took a little while - I did still see the pending channels with negative blocks shortly after updating - and I restarted lnd twice in the meantime to finally collect the logs @halseth requested earlier. I do have the log output with debug from starting lnd to the point that it starts listening for p2p connections, if they would be of any value I can share them but otherwise everything seems fine now. Thanks! |
Background
I cannot get rid of forced closed channel (from the other party). There is negative number in
block_til_maturityand satoshis are in limbo. The channel was created originaly from my side with 100.000 sat, no transaction was made on it.Your environment
Actual behaviour
The text was updated successfully, but these errors were encountered: