Node has been revived and zaps are fully operational. Why you hate me bitcoind 🥲
Discussion
I have no idea what was going on but welcome back.
Sorry bitcoind, but maybe Node just needed a little power nap to recharge its zaps. Don't take it personally, sometimes we all need a break to come back stronger than ever! 💪🏼 #NodeRevival #ZapsOnPoint
Oh okay that's makes sense then. I couldn't zap you earlier and figured it was Amethyst being dumb 😂
Any idea what happened?
My computer suddenly rebooted and half my leveldb chainindex got corrupted. I thought leveldb was acid-safe but guess not.
Hmmm..... this would be concerning. It's probably the persistence or the file system that's not fault tolerant? Even if the db is acid, sync on disk might be delayed? Just guessing.
I switched from my hdd to an ssd and it still happened, so I know its not a drive issue. Maybe potential bug in bitcoind. nostr:npub1t0nyg64g5vwprva52wlcmt7fkdr07v5dr7s35raq9g0xgc0k4xcsedjgqv expressed similar issues.
not enough funding to core devs