Closed joamla96 closed 2 years ago
This issue refers to broken database. Actually, seems like LiteDB journal didn't save us from DB crashes (and from code it seems like this).
It was improved in 9.0, but to fully fix this issue we at least should move to next version of LiteDB which isn't yet released. So put it to Backlog for now.
Hi @joamla96
This issue should be fixed now. Feel free to submit another bug report if this is still the case for you.
Hi
My server had started to spew out two Errors:
It started after my server had physically crashed. It does not seem to have any adverse effects on the server, so far it's run 48h with the errors, so thankfully nothing fatal, just rather annoying to see in the console.
I'm looking through the database file right now, trying to find the keys it's having issues with, but if i had some more information about which specific database it was in, it would have been alot easier.