Closed augustresende closed 2 years ago
Does this recur on restart? (unable to resume)
Are you running the 32bit version of lnd? How large is your channel.db
?
Try compacting the DB (db.bolt.auto-compact=true
in your config, then restart lnd).
I have a similar issue on Raspbian (PI 4, 8GB), channel.db is about 1GB, has SSD on USB 3:
2021-10-30 16:41:13.953 [INF] LTND: Version: 0.13.3-beta commit=v0.13.3-beta, build=production, logging=default, debuglevel=CNCT=debug,CRTR=debug,HSWC=debug,NTFN=debug,RPCS=debug
2021-10-30 16:41:13.954 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2021-10-30 16:41:13.957 [INF] RPCS: RPC server listening on 0.0.0.0:10009
2021-10-30 16:41:13.961 [INF] RPCS: gRPC proxy started at 127.0.0.1:8080
2021-10-30 16:41:13.962 [INF] LTND: Opening the main database, this might take a few minutes...
2021-10-30 16:41:13.962 [INF] LTND: Opening bbolt database, sync_freelist=true, auto_compact=true
2021-10-30 16:41:13.962 [INF] CHDB: Compacting database file at /home/btc/.lnd/data/graph/mainnet/channel.db
2021-10-30 16:41:13.962 [INF] CHDB: Found old temp DB @ /home/btc/.lnd/data/graph/mainnet/temp-dont-use.db, removing before swap
unexpected fault address 0x22aad040
fatal error: fault
[signal SIGSEGV: segmentation violation code=0x1 addr=0x22aad040 pc=0x5035a4]
goroutine 1 [running]:
runtime.throw(0xe1e702, 0x5)
runtime/panic.go:1117 +0x5c fp=0x26e0ecc sp=0x26e0eb8 pc=0x47dbc
runtime.sigpanic()
runtime/signal_unix.go:741 +0x1bc fp=0x26e0ee4 sp=0x26e0ecc pc=0x602f0
go.etcd.io/bbolt.(*DB).meta(0x24a8140, 0x37e)
go.etcd.io/bbolt@v1.3.5-0.20200615073812-232d8fc87f50/db.go:901 +0x1c fp=0x26e0f00 sp=0x26e0ee8 pc=0x5035a4
go.etcd.io/bbolt.(*DB).hasSyncedFreelist(...)
go.etcd.io/bbolt@v1.3.5-0.20200615073812-232d8fc87f50/db.go:323
Are you on the 64bit version of lnd? If yes, then this probably means that your database file got corrupted. If not, try running the linux-arm64
version of lnd
(or simply upgrade RaspiBlitz to the latest version if this is RaspiBlitz).
@guggero I am using this image: https://github.com/lightningnetwork/lnd/releases/download/v0.13.3-beta/lnd-linux-armv7-v0.13.3-beta.tar.gz on Linux btc02 5.10.60-v7l+ #1449 SMP Wed Aug 25 15:00:44 BST 2021 armv7l GNU/Linux, plain raspian, no blitz or umbrel - it's a research node, but with some (little) real money in it.
And I have these files currently:
btc@btc02:~/.lnd/data/graph/mainnet $ ls -al
total 1113888
drwx------ 2 btc btc 4096 Nov 2 07:16 .
drwx------ 3 btc btc 4096 Oct 11 16:20 ..
-rw------- 1 btc btc 1080279040 Oct 30 16:38 channel.db
-rw------- 1 btc btc 20480 Oct 22 23:07 sphinxreplay.db
-rw-r--r-- 1 btc btc 75563008 Nov 2 07:16 temp-dont-use.db
Think it's a memory issue. Can I just delete "temp-dont-use.db" and restart lnd?
You need to switch to a 64bit operating system and use the linux-arm64
version. Otherwise you won't be able to open a DB that's more than 1 GB. You can get around this temporarily by moving the channel.db
to a 64bit machine, run the compaction (with chantools
for example), then move the DB file back if it's significantly smaller than 1 GB.
Ok, my second node recovery. I'd suggest not to provide lnd for 32-bit systems. Thx
Background
lnd crashing:
Your environment
lnd
: v0.13.3-betauname -a
on *Nix) Raspbian (Debian)Steps to reproduce
I don't know, sorry.
Expected behaviour
Not crash
Actual behaviour
Crashing