Node Status, last Contact "17704127h 18m ago" since Update

[Alexey]

1. Stop the storagenode
2. Check your disk for errors, fix if found
3. Start the storagenode

The database is locked is happening with nodes with a slow disk or when the database is fragmented too much.
Usually it resolves itself after a while, but the restart is helping too. Also, you can try to vacuum your database:

"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 "…

By the way what the filesystem on that drive?