Does the file already need to exist in the destination folder? I keep getting an error that the file doesn’t exist.
This still an issue? lost mount and unable to remount.
@East mine is working fine now too. No issues with rclone though. You might want to reauth your remote?
I still get intermittent slowness.
Can you give us more information ? What command do you use and when ??
I’m still getting intermittent slowness as well. Has anyone talked to amazon about the issue?
Im getting slowness last one hour, but Im not getting any error in logs. Anyone is having issues?
Thanks
yes, same here. lost mounts & plex server froze up because mounts are not responding
as you can see here, 50 seconds for a single http request to the ACD rest api ...
2017/04/25 21:54:43 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2017/04/25 21:54:43 DEBUG : HTTP REQUEST
2017/04/25 21:54:43 DEBUG : GET /drive/v1/nodes?filters=kind%3AFOLDER+AND+isRoot%3Atrue HTTP/1.1
Host: cdws.eu-west-1.amazonaws.com
User-Agent: rclone/v1.36-DEV
Authorization: XXXX
Accept-Encoding: gzip
2017/04/25 21:54:43 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2017/04/25 21:55:33 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2017/04/25 21:55:33 DEBUG : HTTP RESPONSE
2017/04/25 21:55:33 DEBUG : HTTP/1.1 200 OK
EDIT:
also multiple "Error: net/http: TLS handshake timeout"
And again, today the same problems as yesterday. Seems like it’s getting worse around 7pm-11pm mest.
aaaand again
httping -l -G -c 3 "https://cdws.eu-west-1.amazonaws.com/drive/v1/nodes?filters=kind%3AFOLDER+AND+isRoot%3Atrue"
PING cdws.eu-west-1.amazonaws.com:443 (/drive/v1/nodes?filters=kind%3AFOLDER+AND+isRoot%3Atrue):
connected to 54.239.32.36:443 (375 bytes), seq=0 time=49972.44 ms
connected to 54.239.34.70:443 (375 bytes), seq=1 time=22705.82 ms
connected to 54.239.32.36:443 (375 bytes), seq=2 time=59308.86 ms
--- https://cdws.eu-west-1.amazonaws.com/drive/v1/nodes?filters=kind%3AFOLDER+AND+isRoot%3Atrue ping statistics ---
3 connects, 3 ok, 0.00% failed, time 134989ms
round-trip min/avg/max = 22705.8/43995.7/59308.9 ms
unwillingly switched over to my gdrive mounts until i can see that these issues are fixed :\
Unfortunately ACD has become more unreliable… If that was even possible. I likely will not renew.
Hopefully it will be fixed, once rclone implements serialized DB I will switch to gdrive as main, but still plan to keep ACD for backup.
Who knows if tomorrow google or amazon does something stupid and completely limits usefulness of their drives.
Months ago hubic was a great and then ultra fuckup with bandwith limiting.
like clockwork - ACD http roundtrip times keep rising from 110ms to 25000ms and more around 19:00 (MEST) , again…
Yup during this time it always deteriorate
few minutes later
Rate exceeded strikes back!
Been having this error. HTTP code 429: “429 Too Many Requests”. Anything I can do?
I am experiencing this as well.
¯_(ツ)_/¯