-
Notifications
You must be signed in to change notification settings - Fork 912
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
Node crashes on startup, failing RBF in incomplete state #4511
Comments
@jsarenik if this is crashing your node, the included patch should fix it. fix incoming... |
Yes, it is crashing also my node, see jsarenik/clightning-dual-crash-logs#1 |
Recompiling 9825f32 with the patch now... diff --git a/lightningd/channel.c b/lightningd/channel.c
index 094a66eb3..b60a7ef8f 100644
--- a/lightningd/channel.c
+++ b/lightningd/channel.c
@@ -726,15 +726,10 @@ void channel_fail_forget(struct channel *channel, const char *fmt, ...)
struct channel_inflight *
channel_current_inflight(const struct channel *channel)
{
- struct channel_inflight *inflight;
/* The last inflight should always be the one in progress */
- inflight = list_tail(&channel->inflights,
- struct channel_inflight,
- list);
- if (inflight)
- assert(bitcoin_txid_eq(&channel->funding_txid,
- &inflight->funding->txid));
- return inflight;
+ return list_tail(&channel->inflights,
+ struct channel_inflight,
+ list);
}
u32 channel_last_funding_feerate(const struct channel *channel) |
With the patch it is humming merrily. Thanks! |
When we re-populate from disk, we need to know what order to recreate the inflights list in. Fixes ElementsProject#4511
When we re-populate from disk, we need to know what order to recreate the inflights list in. Fixes ElementsProject#4511
When we re-populate from disk, we need to know what order to recreate the inflights list in. Fixes ElementsProject#4511 Changelog-Experimental: Protocol: multiple fixes for dual-funding and rbf crashes.
Running current master |
Although it is not crashing on current master, I see this in the log repeating every few seconds (despite it says that it will try to reconnect in 60 seconds):
I would be happy to increase the fee, but what I know so far does not work. |
When we re-populate from disk, we need to know what order to recreate the inflights list in. Fixes ElementsProject#4511
When we re-populate from disk, we need to know what order to recreate the inflights list in. Fixes ElementsProject#4511
When we re-populate from disk, we need to know what order to recreate the inflights list in. Fixes #4511
@jsarenik and I got most of the way through an RBF attempt before he desisted, now it's crashing my node.
We saved the 'inflight' attempt since we got as far as exchanging commitment sigs, but now the "most recent inflight" doesn't match the funding_txid for the channel (sigs should have been exchanged but failed to broadcast..?)
Worth noting that the initial feerate bump wasn't high enough to pass bitcoind's RBF rules, so broadcasting the tx failed.
Jan decided he didn't want to try again, which is valid. It's entirely a manual process at the moment, could definitely use a nicer/more concise command to bump a channel.
Temp patch to fix:
The text was updated successfully, but these errors were encountered: