I’ve recently had an issue with on of my db’s after my cache disk filled up to 100%, it seemed to have caused a malformation of the used_serial.db database.
I’ve followed the link within the forums to used sqlite to try and correct the db but the process is taking forever. Its been running for about 14 hours and has only complete 40Mb of the 2000Mb db. Is there any way of speeding this up as I think my node will become completely disqualified before the process has finished.
Also, if the db cannot be repaired what are my options as this node has been running for 9 months and has nearly $300 in held back money, will i be able to get this money or at least some of it should the node not be able to be recovered?
Tip . You can use tmpfs to restore your databases. It uses memory instead of disk and should take a lot less time than on HDD (you can read more about usage of tmpfs with Docker in the Use tmpfs mounts guide).
You could also move the db file to an SSD and do the procedure there. But tmpfs is by far the fastest.
If I look at the dashboard when ‘all satelites’ is selected there is no information in the window for ingress egress and with held amount is $0. If i select individual satlites then all the information for ingress, held amount etc is displayed for the satelite.
I think the error is still something to do with the used_serials db saying its locked but i’m not sure where to go next?
So i did what you said and checked every db in the node. I found that bandwidth.db was malformed also and have repaired this. Also revocations.db when i integrity check it it says it was unable to open database.
Is revocations.db able to be fixed?
I have reloaded all the databases back into the node excpet revocations and they are all ok. The node dashboard is back up and all information is in it but i am still getting usedserialdb database locked. I check the used_serials.db again but it passes ok.
I ran the VACUUM script and everything reported OK, i’ve started the node backup and everything seems to be working but i’m getting a lot of database locked errors, i’m hoping like you say it’ll be fixed in the next version.
I’ll leave the node up and running now and keep my fingers crossed that it doesn’t get disqualified and that the suspensions get lifted.
Unless there’s anything else you can think of that my help?
I just wanted to say thank you for helping me with my problems it was very much appriciated.