High Amount of Upload Failures?

I have notice a increase of upload failures lately. Should I be concern? I have not made any changes lately.

I think I’m seeing the same thing for about the last hour. Mostly coming from satellite:12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs
========== UPLOAD ============
Successful: 6
Rejected: 0
Failed: 217
Acceptance Rate: 100.000%
Success Rate: 2.691%

Lots of them

Changes in the number of storage nodes being uploaded to and the ratio winning the race has changed with the latest update, a lot of people are seeing the same thing.

I also read in another thread that stress tester Stefan Benten is moving to another satellite. Perhaps he is operating from the europe-west satellite now?

1 Like

Should I just ignore it then?

If your node is otherwise working properly, than yeah, not much you can do about the context cancelled uploads.

Guess seeing a bunch of those error messages had me concern. So why I asked about it here. I think those type of messages should be labeled as something else like “Canceled” vs just “Failed”.


My nodes started bringing up alot of those messages as well.
I could fix this by reducing the cpu load other processes on the servers use.
After lowering the physical cpu core usage of other processes, the “upload failed” messages from storj disappeared almost completely.

I hope this helps someone.

I noticed the traffic pattern changed in February, more Ingress than Egress and also in the logs lots of upload canceled contexts. I guess we are still in testing phase, otherwise the node seem to work ok.

Basically, the less traffic there is, there is more competition among nodes and you will see more failures.

Again nobody is mentioning this: Context cancelled on all uploads/downloads.

1 Like


In order to actually know if a particular data piece was successfully caught, one would need to query the logs for reportedly failed pieces and then query the sqlite DB … this is time consuming, resource consuming, as well as slightly risky since the sqlite DB is actively opened several times by the Storjnode software.

Uplink can simply send a “success” packet or something similar. As they say, they will fix this.