Skip to content
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]: CRITICAL! Unable to process chain reorg / too many witness items to fit into max message size #7096

Closed
C-Otto opened this issue Nov 1, 2022 · 19 comments
Labels
bug Unintended code behaviour needs triage

Comments

@C-Otto
Copy link
Contributor

C-Otto commented Nov 1, 2022

Background

lnd does not process new blocks.

lnd:

2022-11-01 12:02:54.658 [ERR] LNWL: Unable to process chain reorg: unable to get block 000000000000000000070742427fa10ec3c66d006160155a704d9f56d090a3ea: MsgTx.BtcDecode: too many witness items to fit into max message size [count 500003, max 500000]

bitcoind:

2022-11-01T10:44:23Z UpdateTip: new best=000000000000000000070742427fa10ec3c66d006160155a704d9f56d090a3ea height=761249 version=0x20a00000 log2_work=93.818550 tx=776743287 date='2022-11-01T10:44:19Z' progress=1.000000 cache=21.2MiB(82459txo)

My bitcoind knows about block height 761255, but lnd and mempool.space are stuck at 761248.

  • lnd v0.15.3-beta
  • bitcoind v23

https://twitter.com/c_otto83/status/1587400648366202880

@C-Otto C-Otto added bug Unintended code behaviour needs triage labels Nov 1, 2022
@C-Otto C-Otto changed the title [bug]: CRITICAL! Unable to process chain reorg [bug]: CRITICAL! Unable to process chain reorg / too many witness items to fit into max message size Nov 1, 2022
@guggero
Copy link
Collaborator

guggero commented Nov 1, 2022

On it.

@indomitorum
Copy link

Same here.

2022-11-01 11:10:13.912 [ERR] LNWL: Unable to process chain reorg: unable to get block 000000000000000000070742427fa10ec3c66d006160155a704d9f56d090a3ea: MsgTx.BtcDecode: too many witness items to fit into max message size [count 500003, max 500000]

lnd@indomitusbtc:~$ lncli getinfo | grep synced
"synced_to_chain": false,
"synced_to_graph": true,

@C-Otto
Copy link
Contributor Author

C-Otto commented Nov 1, 2022

I'm pretty sure all (recent) lnd installations are affected by this.

@daywalker90
Copy link

https://twitter.com/brqgoo/status/1587397646125260802 he's back

@mutatrum
Copy link

mutatrum commented Nov 1, 2022

btcd issue: btcsuite/btcd#1906

@RandyMcMillan
Copy link
Contributor

😬

@C-Otto
Copy link
Contributor Author

C-Otto commented Nov 1, 2022

Yes, see above.

@b3h3rkz
Copy link

b3h3rkz commented Nov 1, 2022

I'm guessing this is a btcd issue? Everything seems to be fine on bitcoin

@C-Otto
Copy link
Contributor Author

C-Otto commented Nov 1, 2022

Yes, the btcd issue is linked above.

@Stronzo-sky
Copy link

Stronzo-sky commented Nov 1, 2022

also got hte same bug, running lnd-15.3 and bitcoin-22.0:
[ERR] LNWL: Unable to complete chain rescan: MsgTx.BtcDecode: too many witness items to fit into max message size [count 500003, max 500000]

fixed with updating lnd to 0.15.4. Thanks!

@Perlover
Copy link

Perlover commented Nov 1, 2022

Same problem (BTCPay installation)

btcpayserver/btcpayserver#4256

@LNBIG-COM
Copy link

LNBIG-COM commented Nov 1, 2022

Hi,

My all nodes are in a state:

l getinfo|grep synced
    "synced_to_chain": false,
    "synced_to_graph": true,

CRITICAL bug is number # 2 ? :)))

@guggero
Copy link
Collaborator

guggero commented Nov 1, 2022

Fixed by #7098, release binaries and docker images for v0.15.4-beta are going to be available soon (building right now).

@guggero guggero closed this as completed Nov 1, 2022
@Stronzo-sky
Copy link

I'm guessing this is a btcd issue? Everything seems to be fine on bitcoin

no, i`m running bitcoin core v22.0 and having the same issue.

@WalterSmuts
Copy link

I'm running neutrino, and not seeing the issue:

walter@fluffy:~$ lncli  getinfo | grep synced
    "synced_to_chain": true,
    "synced_to_graph": true,
walter@fluffy:~$ lncli  getinfo | grep block
    "block_height": 761264,
    "block_hash": "000000000000000000072cabab0aac7c6b00db0664b82edc77d3252634fcba8a",

@C-Otto
Copy link
Contributor Author

C-Otto commented Nov 1, 2022

Fixed version is available here: https://github.com/lightningnetwork/lnd/releases/tag/v0.15.4-beta

@NicolasDorier
Copy link
Contributor

I bumped to 0.15.4, it fixed the issue. (our own build)

@joostjager
Copy link
Collaborator

Would it be possible to modify lnd so that it skips validation on blocks received from the chain backend? Just reading about Eclair's exposure to this class of bugs: ACINQ/eclair#2473 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unintended code behaviour needs triage
Projects
None yet
Development

No branches or pull requests

15 participants