Pull fails with status 404 #839
Comments
|
Hello there @gfalken, thanks for reporting this issue and welcome back to drive! For starters, please report what your drive version says. $ drive versionThanks. |
|
Version is 0.3.4
Thanks.
…On Mon, Jan 9, 2017, 6:15 PM Emmanuel T Odeke ***@***.***> wrote:
Hello there @gfalken <https://github.com/gfalken>, thanks for reporting
this issue and welcome back to drive!
For starters, please report what your drive version says.
$ drive version
Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#839 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AHlCBRpYjFvY3UbsQksrKzGOypTDUH2cks5rQumpgaJpZM4Le7TX>
.
|
|
Gotcha. So your version is a little behind, the current version is 0.3.9. Please get the latest drive and this problem shouldn't exist anymore $ go get -u -v github.com/odeke-em/drive/drive-gen && drive-gen |
|
Thanks very much, I'll try this tomorrow. Will the empty files will be
regenerated on the next pull?
…On Mon, Jan 9, 2017, 6:40 PM Emmanuel T Odeke ***@***.***> wrote:
Gotcha. So your version is a little behind, the current version is 0.3.9.
Google Drive shut down hosting files on
https://googledrive.com/host/fileId in August 2016 and @dermesser
<https://github.com/dermesser> reported that bug in #734 (comment)
<#734 (comment)> and
also fixed that bug in September 2016 with #735
<#735>.
Please get the latest drive and this problem shouldn't exist anymore
$ go get -u -v github.com/odeke-em/drive/drive-gen && drive-gen
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#839 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AHlCBZ__ORnVaF-Rmp5lCy_YaEWfeh_gks5rQu-JgaJpZM4Le7TX>
.
|
|
Yes, on pulling again, you'll have a manifest of files for deletion, then addition ie replacements. But beware that some files might not be properly synchronized. If you just want to deal with the zero byte files, I'd recommend doing this $ find . -type f -size 0 -exec rm -rf {} \; # Remove the zero byte files locally
$ # And then finally you can do the drive pull
$ drive pull |
|
I'll close this, please reopen if persists. Also let us know if the problem is fixed on the new pull tomorrow. |
|
I updated Drive and now show version 0.3.9. However, when I tried a pull on one affected directory, I got the following: pi@raspberrypi:/mnt/usbstorage/gdrive/webs/TCHealth $ drive pull goroutine 1 [running]: goroutine 17 [syscall, locked to thread]: goroutine 19 [syscall]: goroutine 25 [select]: goroutine 21 [chan receive]: goroutine 24 [IO wait]: goroutine 41 [IO wait]: goroutine 42 [select]: |
|
Yap, boltdb trips noticed in #824 and #828. For starters, my boltdb is at https://github.com/boltdb/bolt/tree/852d3024fa8d89dcc9a715bab6f4dcd7d59577dd, so until we've sorted out boltdb, please use that boltdb commit so that we'll be at par. You can do so like this: $ cd $GOPATH/src/github.com/boltdb/bolt && git reset --hard 852d3024fa8d89dcc9a715bab6f4dcd7d59577dd
$ drive-gen |
|
OK, that change has been made. Same error with a new pull. |
|
Ah crap, okay so how about your Go version? |
|
Actually |
|
drive version: 0.3.9 And there were a lot more errors when I did the pull. Screen dump attached. |
|
Okay, for starters I'd advise getting the latest Go. Debugging Go1.5 wouldn't be feasible. I can't reproduce it here. In case you can't get an updated Go, I made a few binaries here https://github.com/odeke-em/drive/releases/tag/v0.3.9 under downloads, checkout the arm versions, and please try with one of those. |
|
My system now recognizes go1.6.4 but Drive still reports go1.5. Any ideas? |
|
Hi Odeke Still causing the same issues $ go version $ drive version aaron@aaron-ubunix:~/lib/golang/src/github.com/boltdb/bolt $ drive pull goroutine 1 [running]: |
|
@gfalken, it could be that your $GOPATH isn't properly setup. @nelaaro and @gfalken would y'all mind trying the binaries that I built with go1.8? If those work that can help give some hints whether it might be related to the Go version and if the problem is reproducible with the latest Go. I ask because for now I don't have a clue what's going on, but am hoping to eliminate some suspicions so that we can solve this issue. Thank you. |
|
Also the initial reported bug was already solved, let's move the conversation to the bug tracking the boltdb panics at #828. |
|
I'm sorry for the extra work but can you give me some quick instructions for downloading and installing the binary? If I have to do it by trial and error, it's going to take me a long time. Thanks. |
|
Hi Odeke I downloaded the following binary $ ~/Downloads/drive_linux pull goroutine 1 [running]: aaron@aaron-ubunix:~/Documents/gdrive/nelaaro I am going to try and rebuild on go 1.7. Will let you know what I find then. |
|
Hi Odeke As per the post at #828
This did work for me and I was able to successfully pull a working drive directory. @odeke-em, what can be done to ensure that new setups don't encounter these same problems. I have updated to the go 1.7 and rebuilt, everything after removing the src/pkg directories in my $GOPATH This will cause the same issues for people pulling for the first time or on a new directory.
There must be some changes to the bolt src that is causing the regressions below. $ drive version aaron@aaron-ubunix:~/Documents/gdrive/nelaaro panic: invalid page type: 53: 10 goroutine 1822 [running]: I try to pull again with the same issues. goroutine 1 [running]: USING the bindary from aaron@aaron-ubunix:~/Documents/gdrive/nelaaro aaron@aaron-ubunix:~/Documents/gdrive/nelaaro goroutine 1 [running]: |
|
I have finished the wiki on how to work around this problem. |
After many months of working properly, I just noticed than recently pulled files have 0 file sizes. I ran a pull on a single directory and every file looked like this:
pull: /webs/TCHealth/assets/docs/TuolumneCountyHealth.org_map.pdf err: download: failed for url "https://googledrive.com/host/0B4H8hQ8EKW3IQWFLbTAxcmQ0c2M". StatusCode: 404
Any ideas on troubleshooting this?
The text was updated successfully, but these errors were encountered: