I just did an integrity check on the info.db through sqlite3 (while I had my node temporarily offline), and it went ok, but after starting up the node, I see this error:
2019-09-07T12:10:06.914Z ERROR bandwidth Could not rollup bandwidth usage {"error": "bandwidthdb error: database is locked", "errorVerbose": "bandwidthdb error: database is locked\n\tstorj.io/storj/storagenode/storagenodedb.(*bandwidthDB).Rollup:212\n\tstorj.io/storj/storagenode/bandwidth.(*Service).Rollup:51\n\tstorj.io/storj/internal/sync2.(*Cycle).Run:87\n\tstorj.io/storj/storagenode/bandwidth.(*Service).Run:43\n\tstorj.io/storj/storagenode.(*Peer).Run.func9:417\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
I’m using Watchtower to keep the node up-to-date (currently 0.20.1), so the version is fine. And I’ve already restarted the node when I’ve run the integrity check on the DB (had a similar error, hence why I ran it in the first place).
Edit: Just restarted the node though. Same error, and even the former error is showing (during “archiving orders”)
Not sure if that refers somehow to my node (node id is different), or if that’s some unofficial satellite running in the wild being refused by my node.
The node seems to be running mostly alright. There are download requests being received and served and the occasional context cancellation. I was also meaning to ask if there’s a way to store the DB somewhere other than alongside the data (on a faster but smaller storage medium, for example), since it’s now almost 1GB, and I can only image how slow the lookups are on the harddrive that way.