Hey guys, we were just chatting some days ago that sucessrates have gone up super high, just checking the node after like 3 days later. Download Success Rate is still at 99%, but Upload Success Rate dropped from 89% (9000 pieces) to 66% (20500 pieces)… As you can see below looks like normal ‘My no…

Hi, Update from here. Not much change since last. 1% down ========== AUDIT ============= Successful: 445 Recoverable failed: 0 Unrecoverable failed: 0 Success Rate Min: 100.000% Success Rate Max: 100.000% ========== DOWNLOAD ========== Successful: 49275 Failed: …

For me it doesn’t look good, maybe I was at the bottom list with my connection/speed and now more SNOs are there and ‘win over me’? Dropped to 64.950%, it gets worse :slight_smile: Maybe test focus has changed, more uploads, less download traffic? ========== AUDIT ============= Successful: …

What connection did you have? Time for a upgrade? Have you try to reboot router/your node/etc… hmmm :thinking:

It’s a home ADSL connection 10 mbit/s up and 40mbit/s down… so not fast, but quite stable. I’ll reboot the router and see if that changes anything but looks like it was online and connected for 10 days so no big changes there. Router rebooted … no change.

Hello guys, Do you have a script for this output? If so are you willing to share this or point where to find it? Thank you very much in advance!

@tankmann Could you try stopping the node and setting the storage2.max-concurrent-requests field in your config.yaml to something other than 0, maybe 50, and then restarting the container?

[image] cameron: storage2.max-concurrent-requests fi My understanding is that too many concurrent requests would result in a “Rejection” entry in the log file. Since there aren’t that many rejections listed, changing the concurrency limit is unlikely to be a solution.

That’s correct. However, our current default is unlimited concurrent requests, so there would be no rejection logs if the node has not set a limit

Thanks - but I thought through the ‘new way’ this was not needed any more, hence it was removed from the config / not used any longer. Not sure what’s changed but looks like since this morning (didn’t really have time to check details) it’s back on track… maybe just the pressure went down significa…

Two things: latest update, so it looks ok again but not so many pieces [image] When does the standard logfile restart again with docker? I restarted yesterday but a restart doesn’t remove logfiles right? I know I can output them to a file but for now didnt see the need… anyone know standard size…

Storj Community Forum (official)

Upload failed increased SIGNIFICANTLY over the last two days

Node Operators troubleshooting