An existing connection was forcibly closed by the remote host

Node Operators troubleshooting
1

I have new error since 0.25.1

2019-11-10T08:10:10.822+0200 INFO piecestore download failed {“Piece ID”: “F77NADQLOXGKNFWUPOPIZTI7KIBP2C7OIDPTE4XOHY35VMXVNHCA”, “Satellite ID”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”, “Action”: “GET”, “error”: “piecestore: piecestore protocol: write tcp 192.168.88.240:12000->46.4.33.240:40608: wsasend: An existing connection was forcibly closed by the remote host.”, “errorVerbose”: “piecestore: piecestore protocol: write tcp 192.168.88.240:12000->46.4.33.240:40608: wsasend: An existing connection was forcibly closed by the remote host.\n\tstorj.io/drpc/drpcstream.(*Stream).pollWrite:177\n\tstorj.io/drpc/drpcwire.SplitN:25\n\tstorj.io/drpc/drpcstream.(*Stream).RawWrite:221\n\tstorj.io/drpc/drpcstream.(*Stream).MsgSend:254\n\tstorj.io/storj/pkg/pb.(*drpcPiecestoreDownloadStream).Send:905\n\tstorj.io/storj/storagenode/piecestore.(*Endpoint).doDownload.func3:574\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}

2

Also bandwidth is 3 time less than before after update

3

This is result of the same event - the uplink is forcible closed connection to your host.
Since we do not have an earlier pieces of this log we can’t tell you exact reason from these two:

  • your node’s competitors finished earlier;
  • the client canceled upload
4

This is not mining and statistics doesn’t help either. Our customers - living people, not machines, so you can’t expect a “normal” or “abnormal” traffic. They uploads and downloads when they want and how much they want.
Our goal as storage node operators - keeps our nodes online and do not lose the data.

3 Likes