After upgrading ubuntu to version 19.10, errors started

Node Operators troubleshooting
1

Help, the second week a huge number of errors:

2 piecestore: piecestore protocol: write tcp 172.17.0.2:28967->195.201.198.16:52320: write: broken pipe; piecestore protocol: drpc: str…
2 piecestore: piecestore protocol: write tcp 172.17.0.2:28967->195.201.198.16:36526: write: connection reset by peer; piecestore protoc…
1 piecestore: piecestore protocol: write tcp 172.17.0.2:28967->46.4.33.240:35424: use of closed network connection; piecestore protocol…
1 piecestore: piecestore protocol: write tcp 172.17.0.2:28967->46.4.33.240:44054: write: broken pipe; piecestore protocol: drpc: stream…
1 piecestore: piecestore protocol: write tcp 172.17.0.2:28967->195.201.198.16:41036: use of closed network connection; piecestore proto…
1 piecestore: piecestore protocol: write tcp 172.17.0.2:28967->195.201.198.16:42956: write: connection reset by peer; piecestore protoc…
1 piecestore: piecestore protocol: write tcp 172.17.0.2:28967->195.201.198.16:43748: use of closed network connection; piecestore proto…
1 piecestore: piecestore protocol: write tcp 172.17.0.2:28967->46.4.33.240:54778: use of closed network connection; piecestore protocol…
1 piecestore: piecestore protocol: write tcp 172.17.0.2:28967->195.201.198.16:52202: write: connection reset by peer; piecestore protoc…
1 piecestore: piecestore protocol: write tcp 172.17.0.2:28967->46.4.33.240:49568: use of closed network connection; piecestore protocol…
1 piecestore: piecestore protocol: write tcp 172.17.0.2:28967->195.201.198.16:33860: write: connection reset by peer; piecestore protoc…
1 piecestore: piecestore protocol: write tcp 172.17.0.2:28967->46.4.33.240:60924: use of closed network connection; piecestore protocol…
1 piecestore: piecestore protocol: write tcp 172.17.0.2:28967->46.4.33.240:46054: write: broken pipe; piecestore protocol: drpc: stream…
1 piecestore: piecestore protocol: write tcp 172.17.0.2:28967->46.4.33.240:35066: use of closed network con

2

Hello @paster,
Welcome to the forum!

Please, stop and remove the container:

docker stop -t 300 storagenode 
docker rm storagenode

And run it back with all your parameters: https://documentation.storj.io/setup/cli/storage-node#running-the-storage-node

3

Hi Alexey.
Unfortunately it did not help; (

4

Hi. I have around 5% of this error in my log. It is looks like it is same destination IPs. This start at update 25.1.
I’m running Debian 10.2.

5

I suspect this is due to cancellation and some error paths not noticing it properly. Can you provide more complete log lines or full logs if possible? That would help me track it down.

Thanks!

6

Can provide full log modicum for a few days… Just tell me how to do it? I’m a new user here, can I email it to you? I can’t put it here…

Thanks!

You can also download the log file from here:

7

According to the logs, it looks to be retrying each failed download several times. Maybe someone is testing something?