-
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]: CRITICAL! Unable to process chain reorg / too many witness items to fit into max message size #7096
Comments
On it. |
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 |
I'm pretty sure all (recent) lnd installations are affected by this. |
btcd issue: btcsuite/btcd#1906 |
😬 |
Yes, see above. |
I'm guessing this is a btcd issue? Everything seems to be fine on bitcoin |
Yes, the btcd issue is linked above. |
also got hte same bug, running lnd-15.3 and bitcoin-22.0: fixed with updating lnd to 0.15.4. Thanks! |
Same problem (BTCPay installation) |
Hi, My all nodes are in a state:
CRITICAL bug is number # 2 ? :))) |
Fixed by #7098, release binaries and docker images for |
no, i`m running bitcoin core v22.0 and having the same issue. |
I'm running neutrino, and not seeing the issue:
|
Fixed version is available here: https://github.com/lightningnetwork/lnd/releases/tag/v0.15.4-beta |
I bumped to 0.15.4, it fixed the issue. (our own build) |
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) |
Updated LND guide to the last release due to bug found: lightningnetwork/lnd#7096
Background
lnd does not process new blocks.
lnd:
bitcoind:
My bitcoind knows about block height 761255, but lnd and mempool.space are stuck at 761248.
https://twitter.com/c_otto83/status/1587400648366202880
The text was updated successfully, but these errors were encountered: