ERROR server gRPC stream error response {“error”: “piecestore protocol: rpc error: code = Internal desc = transport: transport: the stream is done or WriteHeader was already called”, “errorVerbose”: “piecestore protocol: rpc error: code = Internal desc = transport: transport: the stream is done or WriteHeader was already called\n\tstorj.io/storj/storagenode/piecestore.(*Endpoint ).Upload:324\n\tstorj.io/storj/pkg/pb._Piecestore_Upload_Handler:851\n\tstorj.io/storj/pkg/server.(*Server ).logOnErrorStreamInterceptor:23\n\tgoogle.golang.org/grpc.(*Server ).processStreamingRPC:1127\n\tgoogle.golang.org/grpc.(*Server ).handleStream:1178\n\tgoogle.golang.org/grpc.(*Server ).serveStreams.func1.1:696”} stderr
07:39:29
Thanks for reporting it.
We had already detected this issue and we have a ticket for it, however it’s still in the backlog.
Sealr0x
September 12, 2019, 6:43pm
3
Same issue here, after reboot.
naxbc
October 22, 2019, 2:21pm
4
Same on my 2 RPI nodes, one of them brand new, started this morning.
Dylan
October 22, 2019, 9:00pm
5
This error is much like Context Canceled except that it is almost guaranteed that other nodes were faster in receiving their pieces than yours. It is an informational error and should not be concerning for an SNO.
You can find more common errors on this thread :
Hey all! I wanted to take the opportunity to compile a list of error codes, what they mean, and if you need to worry about the error. I will be updating this as I am able to get information, but wanted to create a central place that people can check. Find the error you are looking for in the list and click the Summary section below it. This will open up with a description of what the error means and its severity.
11/30/2020-A quick note since I have discovered threads that reference errors in t…
2 Likes
naxbc
October 23, 2019, 7:22am
6
Thank you for your reply @Dylan .
1 Like