Open ouwenxxing opened 8 years ago
Hello there @ouwenxxing thanks for reporting this issue and welcome to drive.
I think the first problem might have been caused by a "too many requests" response error from Google Drive. To try to isolate the problem, could you try pushing just one .MOV file alone? Also could you try a variant of push with --piped ie
$ cat IMG_2044.MOV | drive push --piped --force test.mov
Thanks.
hmmm interesting..
Tried couple times but different error logs:
pi@raspi-nas:~/gdrive/Photos/Ouwen Xing/iPhone5s $ cat IMG_2044.MOV | gdrive push --piped --force IMG2044.MOV /Photos/Ouwen Xing/iPhone5s/IMG2044.MOV: Post https://www.googleapis.com/upload/drive/v2/files?alt=json&uploadType=multipart: net/http: transport closed before response was received
Post https://www.googleapis.com/upload/drive/v2/files?alt=json&uploadType=multipart: net/http: transport closed before response was received pi@raspi-nas:~/gdrive/Photos/Ouwen Xing/iPhone5s $ cat IMG_2044.MOV | gdrive push --piped --force --verbose IMG2044.MOV /Photos/Ouwen Xing/iPhone5s/IMG2044.MOV: Post https://www.googleapis.com/upload/drive/v2/files?alt=json&uploadType=multipart: EOF
Post https://www.googleapis.com/upload/drive/v2/files?alt=json&uploadType=multipart: EOF
It's weird that when you specify a piped param but actually need user to provide the binaries to the command. I think it's more like you specify a --piped and read its binaries?(correct me if i misunderstand it)
@ouwenxxing I didn't catch this part
It's weird that when you specify a piped param but actually need user to provide the binaries to the command. I think it's more like you specify a --piped and read its binaries?
Did you mean to say, have to provide a destination name like IMG2044.MOV
? Like you did in
pi@raspi-nas:~/gdrive/Photos/Ouwen Xing/iPhone5s $ cat IMG_2044.MOV | gdrive push --piped --force IMG2044.MOV
If so: Notice that we piped the content in:
$ cat anything | drive push --piped <dest>
This option is useful say if you were chaining outputs from different commands e.g
$ wget https://github.com/odeke-em/drive/blob/master/README.md -O - | drive push --piped manual
I recommended it in https://github.com/odeke-em/drive/issues/638#issuecomment-216737889 as an alternative to try
I'm trying to push a file behind a proxy that needs user athentification. Does anyone know how I can do that? Thank you
hi,
I've been using the push command to sync my photos on raspberry(arm7). But the command failed to push my MOV files on drive. here's the log
Push::Started /Photos/Ouwen Xing/iPhone5s/IMG_2044.MOV
854337123 / 2896175588 [===========>---------------------------] 29.50 % 58m48strying again in 2.278507621s
875833443 / 2896175588 [===========>---------------------------] 30.24 % 57m14strying again in 1.423152201s
891660899 / 2896175588 [============>---------------------------] 30.79 % 56m5strying again in 32.530585715s
932950040 / 2896175588 [============>--------------------------] 32.21 % 54m22strying again in 4.2535405s
947532312 / 2896175588 [=============>--------------------------] 32.72 % 54m4strying again in 4.282080994s
975032677 / 2896175588 [=============>--------------------------] 33.67 % 53m1strying again in 2.788604915s
977195365 / 2896175588 [=============>-------------------------] 33.74 % 53m22sPush::Done``/Photos/Ouwen Xing/iPhone5s/IMG_2044.MOV
the file is around 33M
pi@raspi-nas:~/gdrive/Photos/Ouwen Xing/iPhone5s $ du -sh IMG_2044.MOV
33M IMG_2044.MOV
i use crontab to sync nightly
pi@raspi-nas:~/autosys $ cat gdrive-sync.sh
export http_proxy=192.168.88.249:8123
export https_proxy=$http_proxy
killall gdrive
/usr/bin/gdrive push -no-prompt -ignore-checksum=true --verbose /home/pi/gdrive/Photos
Cause i'm in china i had to use https proxy to upload files. The photos are fine to be pushed but None Mov Files are in drive.
Can you help me with this issue? Thank you!