The "transferring" here may mean that it's verifying checksums and stuff to ensure it's been copied/moved properly. Assuming this is Google Drive, I believe it supports server-side copy/move, which would explain the reason you're seeing no transfer time.
When you upload from your computer, it's actually uploading because the file doesn't already exist, right? Hence you'll see actual transfer times and whatnot.
At least, this is my guess based on the information you've provided so far. As @Animosity022 said, you should provide verbose logs. In addition, can you clarify where the first attempt is being run (it's clearly not being run on your computer given "OT[O]H, if I do the SAME command at my computer, it works fine", but I don't know where it is being run)?
There are the lines that shows this file (all others are checking all the other files)
2019-05-17 22:03:56 DEBUG : kr9t7oppphqa9eqp24jtjevjuo/nf2pupt24n031oj5f448fp2giq0gqluiilc98ovjaadg7oci3g61fkgv3e0at7g5uv6kbe0c9ct8fvkcn92qb3ea7vs1d44j0tm7hks2cler6ao81pmlke86bcck6durq4q21adu6ueq23jnll8s6ssve0: Received error: googleapi: Error 403: User rate limit exceeded., userRateLimitExceeded - low level retry 7/10
You can see too, that it shows, o of 0 bytes transfered, like if it can't get the filesize right.
The really stranger is that this happens with ALL the files on the server, but if I try to upload new files to the Drive, it works perfect. And if I run the same command of copy/sync on my computer, it works fine.