Hello
I have an ACD account with 4 TB of encryoted stuff on it.
Sometime listing the remote dirs, I can see just some of them.
If i try later, I see all of them and so on… with no reason.
Why?
Did you try using -vv - any clues there?
I am not able to see anythings strange… the listed dirs are just some of the dirs on ACD.
I am sure that later it will display all of them.
Moreover, if i launch a SYNC… rclone starts creating the dirs it can not see 
stefano@MSG8:~$ rclone lsd :bck -vv
2017/11/03 17:39:33 DEBUG : rclone: Version “v1.37” starting with parameters [“rclone” “lsd” “:bck” “-vv”]
2017/11/03 17:39:33 INFO : Local file system at /home/stefano/:bck: Modify window is 1s
-1 2017-10-13 01:14:03 -1 Archivio
-1 2017-10-13 01:12:47 -1 CARTONI
-1 2017-10-13 01:13:40 -1 nuova1
-1 2017-10-13 01:13:40 -1 temp
2017/11/03 17:39:33 DEBUG : Go routines at exit 2
2017/11/03 17:39:33 DEBUG : rclone: Version “v1.37” finishing with parameters [“rclone” “lsd” “:bck” “-vv”]
The next thing to try would be to use -vv --dump-bodies along with the lsd command. That will show the actual responses from ACD and you can see if the missing directories are in the response or not. If they are in the response then likely there is an rclone bug, if not, then it must be an ACD problem.
here is the output, but seems the very same as before
stefano@MSG8:~$ rclone -vv --dump-bodies lsd :bck
2017/11/05 16:18:26 DEBUG : rclone: Version “v1.37” starting with parameters [“rclone” “-vv” “–dump-bodies” “lsd” “:bck”]
2017/11/05 16:18:26 INFO : Local file system at /home/stefano/:bck: Modify window is 1s
-1 2017-10-13 01:14:03 -1 Archivio
-1 2017-10-13 01:12:47 -1 CARTONI
-1 2017-10-13 01:13:40 -1 nuova1
-1 2017-10-13 01:13:40 -1 temp
2017/11/05 16:18:26 DEBUG : Go routines at exit 2
2017/11/05 16:18:26 DEBUG : rclone: Version “v1.37” finishing with parameters [“rclone” “-vv” “–dump-bodies” “lsd” “:bck”]
Am I misreading this, but you’re writing lsd :bck which is looking for a local directory; this isn’t talking to ACD at all.
what?
no!!!
:bck links my encrypted ACD drive.
[bck]
type = crypt
remote = acd:BCK
filename_encryption = standard
password = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
password2 = yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy
[acd]
type = amazon cloud drive
client_id = rclone
client_secret = acd
auth_url = https://quixotic-module-170120.appspot.com/auth
token_url = https://quixotic-module-170120.appspot.com/token
token = {"wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww
No, bck: is your encrypted drive; :bck is a local directory. You can see that in your output:
2017/11/05 16:18:26 INFO : Local file system at /home/stefano/:bck: Modify window is 1s
The : goes after the name, not before.
ahhhhhhhhh my fault!!!
after years using rclone… seems I forgot everything.
Got it… anyway it does not work… bud at least I got the error message that the token is EXPIRED.
Maybe this is the reason
END of the story… sorry my fault.
I was no more able to sync my NAS to ACD using my old scripts.
typing manually the comemnds, I confused the position of “:”, but the original root cause my scripts were not running was because tokens expired.
Thanks.
I’m glad it isn’t rclone and ACD having an incompatibility - that would have been hard work to debug!