Git'Fellow
Git'Fellow
Could you do the same test **but** stop cron in the meantime to see what happens?
Does this fix https://github.com/nextcloud/server/issues/34123?
> #28695 was an older alternative, not sure which is best Both perform a similar goal, this one seems more clean.
Is this still a thing after https://github.com/nextcloud/server/commit/9e1d4312555ddc1009450b1f6b7078ae35790593? Cc @juliushaertl
>While rate limiting could be put in place on the load balancer/webserver side, it may not be able to limit properly (based on the ip) if there are multiple users...
We've implemented a rate limiting by extracting some **cookie** params from the session request on a [Leaky Bucket](https://en.wikipedia.org/wiki/Leaky_bucket) algo. We apply it not only for Nextcloud but also for other...
Adding this thread that may help here: https://github.com/mattn/go-sqlite3/issues/274
On our side we're just `rsync`ing from a local NFS volume to a JuiceFS mount over SSH: `rsync -arv /data 10.10.10.1:/srv/juicefs` There is an average of 400K files of different...
On the sender side: ``` rsync: [receiver] close failed on "/srv/juicefs/slprj/sldrt_win64/_sharedutils/.shared_file.dmr.tvezGA": Input/output error (5) rsync error: error in file IO (code 11) at receiver.c(871) [receiver=3.2.3] rsync: [sender] write error: Broken...
Hi @SandyXSD I've asked the provider about the logs, they told me there are no errors on the logs, only normal codes like 200, 304, etc. As I've said early,...