My node has been suspended on asia east?

[Dinip]

Seems like my node was suspended today morning in asia east. Just restarted to node now to see if it affects something but it has been up 24/7 for the last 6 months, only a few restarts to update the docker. Also have another node in another location with different hardware and that one seems to be fine… I ran the scripts for audits before restarting the node, 2nd printscreen.

What should I do?
Thanks

Script for audits:

[nerdatwork]

Check your log for audit errors. Try searching for download failed and GET_AUDIT.

[Dinip]

2016 GET_AUDIT and ~1500 download failed in different satellites with the error “usedserialsdb error: database disk image is malformed” since the beginning of the month…

edit: sorry for the double reply… somehow it was not sending and then it sent twice…

[donald.m.motsinger]

Search for download failed AND GET_AUDIT not download failed OR GET_AUDIT

[nerdatwork]

@Dinip

usedserialsdb error: database disk image is malformed

You need to follow the steps given below

How to fix a "database disk image is malformed"

[Dinip]

how do I search like that? I was opening the docker log file in sublime text…

[donald.m.motsinger]

@Dinip

how do I search like that?

If you’re on Linux, grep "download failed" logfile | grep "GET_AUDIT"

[Dinip]

yeah, I got 2 .db errors, in orders.db and used_serial.db… following the article to fix…

[Dinip]

well… I followed the article to fix “used_serial.db” since that is the one giving errors "error": "usedserialsdb error: database disk image is malformed", not in every download it gets "error": "usedserialsdb error: database is locked",… I was searching in the forum about the topic and seems like more users are having the same problems the last few days… maybe something related with the update? since the docker update (storjlabs/storagenode:beta) was released 4 days ago and people are having problems since them.
I have my server with 31 days uptime, so it wasn’t an unexpected power outage causing the corruption

edit: the errors of malformed only occur in data from 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6 (asia-east) the one that I got suspended…

[Dinip]

any solution to “unlock” the db after the fix?

[Alexey]

This could help:

"Action": "GET_AUDIT", "error": "usedserialsdb error: database is locked",

I’m running a docker version on Debian GNU/Linux. Here’s the procedure I use to vacuum and check the databases: Stop the node Vacuum the dbs integrity_check the dbs Restart the node Here’s a bash check which should do that for you. Please change the database directory to reflect where yours are on your system. docker stop -t 300 storagenode && dbs=$(ls /opt/storj/storage/*.db) c1="VACUUM;" c2="PRAGMA integrity_check;" for i in $dbs do sqlite3 $i "$c1" done for i in $dbs do sqlite3 $i "…

[Dinip]

already tried that this afternoon and no luck…I tried to the “script” (vacuum and pragma integrity_check) i the original .db file and it as giving a malformation error, so I followed the article above to fix the image and then it worked (vacuum and integrity) but kept giving the locked error.
So, I kept using the same used_serial.db since it is only giving “errors” on asia satellite… probably not the best idea but otherwise it was giving “database is locked in every action”.