I’m running storagenode, as a Docker on my Synology.
So far, so good.
Apparently, there was a power outage and Synology rebooted (I have UPS, not sure, why it didn’t help).
So, at some point today, I went to check the status and I see, that the storagenode is not running. By the way, the watchtower container was running.
So, I tried to start it and got:
docker: Error response from daemon: Conflict. The container name “/storagenode” is already in use by container "f6d49…
use docker ps to make sure.
If you would like to recreate your node docker stop storagenode - stop running node docker rm storagenode - remove docker container docker run ..... - create new container
While it is possible to place your SN Dashboard to be available directly on the Internet via an unauthenticated web page… it is not recommended that SNOs do this.
any errors from right after the synology came back online?
When Synology came back - storagenode failed to start, so there was no storagenode logs right after the start.
I started it after ~9 hours, and I see few errors like this:
2019-12-12T01:45:03.450Z ERROR piecestore failed to add order {“error”: “ordersdb error: database is locked”, “errorVerbose”: “ordersdb error: database is locked\n\tstorj.io/storj/storagenode/storagenodedb.(*ordersDB).Enqueue:52\n\tstorj.io/storj/storagenode/piecestore.(*Endpoint).saveOrder:672\n\tstorj.io/storj/storagenode/piecestore.(*Endpoint).doUpload:426\n\tstorj.io/storj/storagenode/piecestore.(*drpcEndpoint).Upload:223\n\tstorj.io/storj/pkg/pb.DRPCPiecestoreDescription.Method.func1:985\n\tstorj.io/drpc/drpcserver.(*Server).doHandle:175\n\tstorj.io/drpc/drpcserver.(*Server).HandleRPC:153\n\tstorj.io/drpc/drpcserver.(*Server).ServeOne:114\n\tstorj.io/drpc/drpcserver.(*Server).Serve.func2:147\n\tstorj.io/drpc/drpcctx.(*Tracker).track:51”}