You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Start a fresh lnd node, point at suitable neutrino forked btcd node and sync chain to tip.
Actual behavior:
Lnd crashed after roughly 500k blocks due to panic from boltdb. From issues linked below this seems to be a race condition with respect to boltdb access.
Referring to discussion in lightningnetwork/lnd#1107, looks like one of the byte slices passed to the db transaction gets changed during the transaction?
The filter is fetched asynchronous from the peers, so it is a potential candidate:
Expected behavior:
Start a fresh lnd node, point at suitable neutrino forked btcd node and sync chain to tip.
Actual behavior:
Lnd crashed after roughly 500k blocks due to panic from boltdb. From issues linked below this seems to be a race condition with respect to boltdb access.
Affects:
LND commit 2a61ccec
BTCD commit 0dcaa7f9
Running on Ubuntu 16.04 (in Docker)
More detailed log excepts can be found here
Related boltdb issues
boltdb/bolt#731
etcd-io/bbolt#72
Note: this occurs only on mainnet and not on testnet
The text was updated successfully, but these errors were encountered: