I think it may be cockpit error on my part because I have some other access issue on 443 and I am misinterpreting what it is telling me.
The reason I think this is because each of your solutions works in other environments, as does the simple account:container.
Unfortunately I can not yet explain what I am seeing so I think I have to conclude I am mistaken and therefore the question I asked is the wrong question and the issue is related to a specific environment.
Thanks, and if I figure out what is going on, I will report back.
Can you paste the traceback for that please? rclone shouldn’t ever do that!
Unless you use the -v flag rclone won’t print anything unless there are errors. The -P flag will show you what is going on (for progress) so that is better than -v for interactive use.
@ncw wtih respect to the nil pointer. It seems to happen if I try to sync a blob that only contains a folder in the first directory. (doesnt do this in cmd, only in powershell (v4.4) )
@ncw with respect to the run and disappear thing. It disappears even though i specified -p. After specifying -v i do get an error message.
something about waiting for checks to finish. (once again only happens in powershell (v4.4) not cmd.
./rclone.exe : 2018/11/18 22:54:51 INFO : Local file system at \\?\C:\gcdstest1: Waiting for checks to finish
At line:1 char:1
+ ./rclone.exe sync azure:gcdsmaster\2019\master C:\gcdstest1 -v
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (2018/11/18 22:5...hecks to finish:String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError
2018/11/18 22:54:51 INFO : Local file system at \\?\C:\gcdstest1: Waiting for transfers to finish
2018/11/18 22:54:51 INFO : Waiting for deletions to finish
2018/11/18 22:54:51 INFO :
Transferred: 0 / 0 Bytes, -, 0 Bytes/s, ETA -
Errors: 0
Checks: 0 / 0, -
Transferred: 0 / 0, -
Elapsed time: 1.3s
I’m not sure I understand what you mean? What does rclone lsf -R give on the source which causes the error?
Can you run the command with -vv --log-file rclone.log and paste the output of the log?
Thanks!
That isn’t an error message, that is just a log produced by the -v flag. Not sure why powershell thinks there is an error.
It looked like that sync was successful, but no objects were transferred. If the source has only empty directories in, that is what you’d expect as azure blob storage doesn’t have a concept of directory so rclone can’t store empty directories.
Is the case here that rclone writes to stderr, and PowerShell treats output from native commands on stderr as an error? You can work around this by tricking PowerShell into just outputting anything from stderr (and stdout) as strings: