Fatal error: rpc error: code = Unknown desc = piecestore inspector: infodb: locking protocol

I trying to start a dashboard and got this error:

2019-07-13T18:51:19.979Z        INFO    Configuration loaded from: /app/config/config.yaml
2019-07-13T18:51:19.993Z        INFO    Node ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Fatal error: rpc error: code = Unknown desc = piecestore inspector: infodb: locking protocol

docker logs --tail 20 storagenode

2019-07-13T18:53:35.464Z        INFO    piecestore      upload started  {"Piece ID": "6A4G772K2FT5QZIO5ZYEY53SLMZZTVA6AV
KOQUJRNL6TIZXQBZ5Q", "SatelliteID": "118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW", "Action": "PUT"}
2019-07-13T18:53:35.518Z        ERROR   duplicate request: infodb: locking protocol
        storj.io/storj/storagenode/storagenodedb.(*usedSerials).Add:35
        storj.io/storj/storagenode/piecestore.(*Endpoint).VerifyOrderLimit:82
        storj.io/storj/storagenode/piecestore.(*Endpoint).Upload:176
        storj.io/storj/pkg/pb._Piecestore_Upload_Handler:602
        storj.io/storj/pkg/server.logOnErrorStreamInterceptor:23
        google.golang.org/grpc.(*Server).processStreamingRPC:1209
        google.golang.org/grpc.(*Server).handleStream:1282
        google.golang.org/grpc.(*Server).serveStreams.func1.1:717
2019-07-13T18:53:35.549Z        ERROR   duplicate request: infodb: locking protocol
        storj.io/storj/storagenode/storagenodedb.(*usedSerials).Add:35
        storj.io/storj/storagenode/piecestore.(*Endpoint).VerifyOrderLimit:82
        storj.io/storj/storagenode/piecestore.(*Endpoint).Upload:176
        storj.io/storj/pkg/pb._Piecestore_Upload_Handler:602
        storj.io/storj/pkg/server.logOnErrorStreamInterceptor:23
        google.golang.org/grpc.(*Server).processStreamingRPC:1209
        google.golang.org/grpc.(*Server).handleStream:1282
        google.golang.org/grpc.(*Server).serveStreams.func1.1:717

After restarting of storagenode the problem is gone. But I think it’s a temporary solution

me too… i have the same error :roll_eyes::roll_eyes:

Hello @guarez,
Welcome to the forum!

Please, try a workaround from the topic: restart the container docker restart -t 300 storagenode

Just out of curiosity, it’s the same to run “docker restart -t 300 storagenode” than this other “docker run -d --restart unless-stopped -p 28967: 28967 -e WALLET =” 0xxxxxxxxxxxxxxxxxxxx “-e EMAIL =” xxxxxxx @ gmail .com “-e ADDRESS =” xxx.xxx.xxx.xxx:28967 “-e BANDWIDTH =” 6TB “-e STORAGE =” 1.5TB “–mount type = bind, source =” / root / .local / share / storj / identity / storagenode “, destination = / app / identity --mount type = bind, source =” / mnt / storj ", destination = / app / config --name storagenode storjlabs / storagenode: alpha

The docker run command creates the container, docker restart -t 300 storagenode restarts the already existing container.