lnd: [bug]: LND Suddenly lots of force closes, `Error while broadcasting transaction`

Background

Nothing in particular happened. Updated to 0.17.0-rc1 shortly it came out. In the last few days, my node has seen a massive amount of force-closes.

Your environment

  • version of lnd: LND 0.17.0-rc1
  • which operating system (uname -a on *Nix): Linux 5.15.0-46-SMP x86_64 x86_64 x86_64 GNU/Linux
  • backend: bitcoind

Steps to reproduce

Unknown.

Logs:

During the FC:

[INF] CNCT: ChannelArbitrator(<id>:31): starting state=StateDefault, trigger=chainTrigger, triggerHeight=<block>
[INF] CNCT: ChannelArbitrator(<id>:31): fail dangling htlc=<id> from local/remote commitments diff
[INF] CNCT: ChannelArbitrator(<id>:31): force closing chan
[INF] CNCT: Broadcasting force close transaction <tx_id>, ChannelPoint(<id>:31): (*wire.MsgTx)(0xc004525980)({
Version: (int32) 2,
TxIn: ([]*wire.TxIn) (len=1 cap=1) {
...

Maybe related:

[ERR] WTCL: (anchor) SessionQueue(<id>) failed to ack update: unable to ack seqnum=99: channel not registered
[ERR] WTCL: (anchor) SessionQueue(<id>) unable to send state update: unable to ack seqnum=99: channel not registered
...
[WRN] LTND: Error while broadcasting transaction: mempool fee not met: -26: mempool min fee not met, 550 < 4208
(this error repeats many times)
....
[ERR] BTCN: Unable to rebroadcast transaction <txid>: double spend: -25: bad-txns-inputs-missingorspent

More errors (update: 11.09.2023)

[INF] PEER: Peer(<id1>): unable to read message from peer: read next header: EOF
[INF] PEER: Peer(<id1>): disconnecting 02c4a7390c5c0e28eff5d8034a49d724900b196948f5723fecd887512b2f0020f3@82.164.75.19:5750, reason: read handler closed
[WRN] HSWC: ChannelLink(<id2>:2): error when syncing channel states: first message sent to sync should be ChannelReestablish, instead received: *lnwire.Error
[ERR] HSWC: ChannelLink(<id2>:2): failing link: unable to synchronize channel states: first message sent to sync should be ChannelReestablish, instead received: *lnwire.Error with error: unable to resume channel, recovery required
[INF] HSWC: ChannelLink(<id2>:2): exited
[INF] NTFN: Cancelling epoch notification, epoch_id=75
[ERR] WTCL: (anchor) SessionQueue(<id1>) unable to send state update: unable to ack seqnum=176: channel not registered
[ERR] WTCL: (anchor) SessionQueue(<id2>) failed to ack update: unable to ack seqnum=155: channel not registered
[ERR] WTCL: (anchor) SessionQueue(<id2>) unable to send state update: unable to ack seqnum=155: channel not registered
[ERR] WTCL: (anchor) SessionQueue(<id3>) failed to ack update: unable to ack seqnum=600: channel not registered
[ERR] WTCL: (anchor) SessionQueue(<id3>) unable to send state update: unable to ack seqnum=600: channel not registered
[ERR] BTCN: Unable to rebroadcast transaction <id>: unable to replace transaction: -26: insufficient fee, rejecting replacement <id>; new feerate 0.00001011 BTC/kvB <= old feerate 0.00004684 BTC/kvB
[ERR] BTCN: Unable to rebroadcast transaction <id>: unable to replace transaction: -26: insufficient fee, rejecting replacement <id>; new feerate 0.00001011 BTC/kvB <= old feerate 0.00004508 BTC/kvB
[ERR] BTCN: Unable to rebroadcast transaction <id>: unable to replace transaction: -26: insufficient fee, rejecting replacement <id>; new feerate 0.00001011 BTC/kvB <= old feerate 0.00004684 BTC/kvB

About this issue

  • Original URL
  • State: open
  • Created 10 months ago
  • Comments: 18 (5 by maintainers)

Most upvoted comments

Privately communicated LND logs to @ziggie1984 for further analysis.

I will share full logs soon.