Still struggling to get my node to sync.

Full reindex didn’t work. Keeps choking about halfway through. Now attempting to copy chain data from a slightly behind raspberry pi node. To see if I can get caught up.

Had a channel force closed this morning, likely cause the lightning node had been offline so much recently. 😩

Reply to this note

Please Login to reply.

Discussion

Just get a recent bootstrap of the chain so you don't have to sync from scratch.

That’s what I’m doing now from my old umbrel

👍

sorry to hear about the force closure.

is this bitcoin core, knots or btcd?

btcd is slow af and prone to choking on random things, if that's what you are using then at least upgrade it to latest builds...

core is the fastest, on a 100mbit connection on a ryzen 5 2021 it has full sync in under 2 days and probably 3-4 days if you add those indexes, indexes mainly speed up queries so i recommend syncing first and then enabling the index when you can afford downtime

Core. Thanks for the tipis.

hopefully not disk related issues. check `dmesg` or SMART parameters

Definitely disk related to begin with. Already moved to a different disk but the files from the original were obviously corrupted beyond a reindex.

I gave up running my own lightning node a while ago. Because I don't have time to pet the god damn thing all the time.

It has been surprisingly easy until now and it wasn’t even the lightning node’s issue.

Similar expirience... 2 channels force closed...

I’m sorry for your loss.

Fee wasnt high so no much harm done...

I see this a lot, among other noderunners. I started writing a long post about how to setup reasonably stable and reasonably worry free node. I will definitely address the issue of disks and corruption of the filesystem 🐶🐾🫡