Closed nbauernfeind closed 8 months ago
It must have been one of the other files in the db directory. Even after copying the sql database from another host I couldn't get that node to sync. Then I blew away the entire db directory, but kept the copy of the database, and the farmer was able to restart.
No idea what was actually corrupt. Leaving this note in hopes to help the next poor soul who thinks they could fix it with a resync from the network.
What happened?
I recently updated to v2.1.4. Somehow the database got malformed, so I deleted it and have been trying to sync from other nodes on the network. Again I'm getting errors that the database is malformed.
The SSD that hosts the db is showing no data or integrity errors; so I don't believe it is a hardware failure. There is also 1.7TB of free space on the drive; so it's not an out-of-memory issue either.
Version
2.1.4
What platform are you using?
Linux
What ui mode are you using?
CLI
Relevant log output