Upload failed in docker logs and lot less traffic

Hey fellow SNO,

This is my 3rd month as a SNO and still learning, ive got a couple of rigs up and running but this month i got a lot less traffic then i did at the end of January also my docker logs are full with Failed upload messages.
Im running v.0.31.12 on my nodes.

Is this normal?

A lot of people are experiencing the same, me included, but apparently, it´s “normal”!

Seems to me something is not right…

Looks normal. The 118U satellite stopped uploading volumes of test data so now you see more of the other satellites around the world trying uploads and you link/distance to the client is such that you lose the race to receive the file. It’s part of the storj design. Nothing wrong, just accept those messages.

3 Likes

Ok, thank you.

Any ideas what i can do to not loose the race?

On my node, based on my packet traffic, it looks like a lot of those failed uploads are coming from Denmark(I suspect Stefan). I’m in the US so I’m not too surprised I’m loosing the race.

I’m in germany and still onlly get 12% upload success rate

I’m in japan and only get under 10% upload success rate.

How can i check upload success rates?

Highly unlikely that only resumes to “losing the race”.
I have 5 nodes, since RPI 3b+ on a 100/40 ISP to a HP Proliant Microserver on a dedicated 100/100 ISP!
They all went from a upload sucess rate of 96% to a 6ish!!!
This is not just “losing the race”!! Something else was implemented on 0.30.12!

1 Like

Well, I´m in The Netherlands and “losing the race” bigtime! Went from a sucess upload rate of 96% to 6%!!!

My success rate dropped to 65% with a 250/100 MBit/s connection in Germany. My guess is with a lot less traffic the competition gets more fierce…

probably not bandwith related, I have a 50/1000MBit/s connection in Germany.
Hardware is not bad either, Ryzen 2400, HDDs connected by USB3.0, almost no load on the server. But apparently my successrate is just as low as other people’s RPIs.

I’m surprised you get 65% success rate, that’s quite a lot higher than anything I read the last days.

I was surprised myself. With the little traffic I am seeing these days I expected a lot worse. I am running a Synology DS918+.

========== AUDIT ============= 
Successful:           1891 
Recoverable failed:   0 
Unrecoverable failed: 0 
Success Rate Min:     100.000%
Success Rate Max:     100.000%
========== DOWNLOAD ========== 
Successful:           16041 
Failed:               28 
Success Rate:         99.826%
========== UPLOAD ============ 
Successful:           11910 
Rejected:             0 
Failed:               6505 
Acceptance Rate:      100.000%
Success Rate:         64.676%
========== REPAIR DOWNLOAD === 
Successful:           5 
Failed:               0 
Success Rate:         100.000%
========== REPAIR UPLOAD ===== 
Successful:           1848 
Failed:               1216 
Success Rate:         60.313%

You should reset your log and check again. 1891 audits must be 3 days?

This is from one day on my node:
========== AUDIT =============
Successful: 807
Recoverable failed: 0
Unrecoverable failed: 0
Success Rate Min: 100.000%
Success Rate Max: 100.000%
========== DOWNLOAD ==========
Successful: 5606
Failed: 70
Success Rate: 98.767%
========== UPLOAD ============
Successful: 888
Rejected: 0
Failed: 6242
Acceptance Rate: 100.000%
Success Rate: 12.454%
========== REPAIR DOWNLOAD ===
Successful: 922
Failed: 0
Success Rate: 100.000%
========== REPAIR UPLOAD =====
Successful: 80
Failed: 535
Success Rate: 13.008%

Yes it has been 3 days. Will reset now to get some more up to date ratios…

My overall traffic dropped when 118 stopped stress testing… but my success rate only moved moderately down. I’m still seeing significantly higher success rates than Sept and Oct of 2019 when my node was sitting around 60% …

Results since 2020-02-02 13:49 UTC, node location NE USA

========== AUDIT ============= 
Successful:           997 
Recoverable failed:   0 
Unrecoverable failed: 0 
Success Rate Min:     100.000%
Success Rate Max:     100.000%
========== DOWNLOAD ========== 
Successful:           4462 
Failed:               1 
Success Rate:         99.978%
========== UPLOAD ============ 
Successful:           5265 
Rejected:             0 
Failed:               1050 
Acceptance Rate:      100.000%
Success Rate:         83.373%
========== REPAIR DOWNLOAD === 
Successful:           77 
Failed:               0 
Success Rate:         100.000%
========== REPAIR UPLOAD ===== 
Successful:           481 
Failed:               95 
Success Rate:         83.507%

Keep in mind that latency to the satellite is not relevant, it’s latency to the uploading customer. As an example, if a customer is using a satellite in Europe but the customer is in Australia, nodes in Europe are going to lose the race against nodes in Australia.

You can only reason using the location of the satellite insofar as customers choose the satellite closest to them. They might not. And even in the same geographic region, latency to the satellite and latency to the customer could be wildly different depending on a whole host of factors.

1 Like

I run a dual stack IPv4/IPv6 … Since about mid-Nov 2019, I get about half my traffic over IPv6. So, maybe that’s something to try if a given SNO sees a drop in successful hits.

how can I get a statistic like you guys have in the previous posts?