Dropbox for R6 (x86 only)

WhoCares? wrote:

btaroli wrote: ... I yanked out all Dropbox references from my user home dir, returned /etc/default/dropbox to it's virgin null status, and rebooted the NAS (no amount of killing was going to get rid of the original zombie/defunct process). But you didn't remove the add-on and didn't make any changes/deleted the Dropbox references that were installed in your primary storage location (presumably /data)?

Well, if you mean /data/Dropbox, for the "admin" setup I presume, then no. I never started that one so there's nothing at all in there, even now.

# cd /data/Dropbox/
# ls -lA
total 0

The bits I removed from the homedir where I *was* running it were: .dropbox, Dropbox, and .dropbox-dist

WhoCares? wrote:

btaroli wrote: I should point out that trying to apply either the newer stable or testing builds results in an error. No logging on that either? Would have been nice to see the actual error message. But no, no logging on that either ;) But to give you a better understanding let me try to explain what is happening and also why I can't fix this. On initial install, Dropbox Manager wil try to download the Dropbox binaries from the generic "stable" link provided by Dropbox, e.g. from here https://www.dropbox.com/download?plat=lnx.x86_64 As you can see this is an unversioned link and it *should* point to the latest stable release. Unfortunately Dropbox isn't very good at keeping these links current, that's why in most of the cases Dropbox Manager will install a version that is older than the one Dropbox Manager later on reports as being the current "stable" version.

Well, I did try a simple wget on this and got:

# wget https://www.dropbox.com/download?plat=lnx.x86_64
--2014-04-23 12:35:30--  https://www.dropbox.com/download?plat=lnx.x86_64
Resolving www.dropbox.com (www.dropbox.com)... 108.160.165.20
Connecting to www.dropbox.com (www.dropbox.com)|108.160.165.20|:443... connected.
ERROR: The certificate of ‘www.dropbox.com’ is not trusted.
ERROR: The certificate of ‘www.dropbox.com’ hasn't got a known issuer.

OK... this time with --no-check-cert

# wget https://www.dropbox.com/download?plat=lnx.x86_64 --no-check-cert
--2014-04-23 12:35:49--  https://www.dropbox.com/download?plat=lnx.x86_64
Resolving www.dropbox.com (www.dropbox.com)... 108.160.165.20
Connecting to www.dropbox.com (www.dropbox.com)|108.160.165.20|:443... connected.
WARNING: The certificate of ‘www.dropbox.com’ is not trusted.
WARNING: The certificate of ‘www.dropbox.com’ hasn't got a known issuer.
HTTP request sent, awaiting response... 302 FOUND
Location: https://dl-web.dropbox.com/u/17/dropbox-lnx.x86_64-2.6.31.tar.gz [following]
--2014-04-23 12:35:49--  https://dl-web.dropbox.com/u/17/dropbox-lnx.x86_64-2.6.31.tar.gz
Resolving dl-web.dropbox.com (dl-web.dropbox.com)... 54.243.190.36
Connecting to dl-web.dropbox.com (dl-web.dropbox.com)|54.243.190.36|:443... connected.
WARNING: The certificate of ‘dl-web.dropbox.com’ is not trusted.
WARNING: The certificate of ‘dl-web.dropbox.com’ hasn't got a known issuer.
HTTP request sent, awaiting response... 302 FOUND
Location: https://dl.dropboxusercontent.com/u/17/dropbox-lnx.x86_64-2.6.31.tar.gz [following]
--2014-04-23 12:35:50--  https://dl.dropboxusercontent.com/u/17/dropbox-lnx.x86_64-2.6.31.tar.gz
Resolving dl.dropboxusercontent.com (dl.dropboxusercontent.com)... 50.19.234.162, 54.243.74.238, 54.243.241.219, ...
Connecting to dl.dropboxusercontent.com (dl.dropboxusercontent.com)|50.19.234.162|:443... connected.
WARNING: The certificate of ‘dl.dropboxusercontent.com’ is not trusted.
WARNING: The certificate of ‘dl.dropboxusercontent.com’ hasn't got a known issuer.
HTTP request sent, awaiting response... 200 OK
Length: 24380314 (23M) [application/octet-stream]
Saving to: ‘download?plat=lnx.x86_64’

100%[==========================================================>] 24,380,314  1.95MB/s   in 14s    

2014-04-23 12:36:05 (1.72 MB/s) - ‘download?plat=lnx.x86_64’ saved [24380314/24380314]

So at this moment, at least, it is pulling 2.6.31 when accessed.

WhoCares? wrote:

...To access these relelases directly, you need to use a special URL which I currently can't tell you for I'm at work and have no access to my dev environment at home. Anyway, as is the case with the stable releases Dropbox also is a bit slow when putting newer releases into the "direct download directory". So what happened in your case most likely is that while 2.6.31 was announced on the releases page as well as the RSS feed there wasn't any real downloadable version available in the direct downloads directory. Since the actual installation of newer versions is done using a bash script it is very hard to find out why exactly the download failed (which is the main reason why it would fail at all).

OK. I see install_dbx.sh and that indicates the direct URL is (forgiving var reference): https://dl-web.dropbox.com/u/17/dropbox-lnx.x86_64-${DBX_VERSION}.tar.gz

Maybe I'll step through the bits of the script and see if I can isolate that behavior, to determine if it's something local. But I can accept that there may be lag here, knowing how often DB puts out builds.

WhoCares? wrote:
btaroli wrote: ... I've just checked again and it says retrieving file list again. Odd but I'll check it again in a few mins before posting this. What you're seeing is what Dropbox writes into it's messaging socket. ... So chances are that if you just hit "refresh" often enough, you'll see the message appear and disappear again.

Figured it might be something like that... but never hurts to ask. :)

WhoCares? wrote:
btaroli wrote: Well, that's a little scary. I tried incrementally syncing a file to see how the daemon behaved. What exactly do you mean by "incrementally syncing"?

Added a file to the dropbox, to see if the NAS picked it up and downloaded it.

WhoCares? wrote:

... So I currently have no idea what may have gone wrong with your installation except maybe an improper "manual cleanup" that left some older configs on the system. In any case, if the folders are there, sync should automatically run over the LAN link and the files should appear. Depending on the size of your Dropbox you should be able to at least monitor the progress of an initial sync by refreshing the status page after linking a Dropbox.

Well, I guess I'll try completely removing it and re-adding. It sure did /seem/ to be doing the right thing. I saw the file count tick downward as I refreshed the page. So I was pretty surprised to see only sub-folders there afterward.

WhoCares? wrote:
Which reminds me: what version of the Dropbox Manager app are you using?

The version the page gave me when I paid... 1.0.1