It’s just a backup, but the file is corrupt so I don’t think you can do much with it anyway. I just don’t like deleting stuff until we know it’s all fixed.
That seems fixable though. What version was your node running on when you first encountered the error and did you update it in the mean time? It seems it’s trying to do some migration steps. We may have to drop the index. Let me have a look at the code, I’ll get back to you.
The last I remember was 1.6.4, but I’m not sure
That’s quite old. Maybe that explains why it’s still trying to do the migration. Should be an easy fix though.
Please run:
sqlite3 orders.db
then
DROP INDEX idx_order_archived_at;
and then
.quit
And try starting the node again.
It’s working now. Node is at version 1.10.1. Thank you very much. If I knew this was so easy to do, then I would not feel so bad about this. I was very afraid to lose those 2 months of node progress.
Glad to see that resolved it!
Most issues that don’t involve actual data loss can be fixed as long as your node hasn’t been disqualified yet. So yeah, don’t stress, we can usually help you fix things.