DropBox: Not able to link account

WhoCares? wrote:
Wow, there may well be some problems interacting here.

Tell me about it! Hopefully it is nothing I am doing, but I am known to mess things up pretty bad :oops:

WhoCares? wrote:
First, as mdgm suggested, there are some browsers (especially on Windows but I don't want to rule out the Mac here although I've never run into the problem) that won't reflect status changes properly. IE is the major source of problems here but older versions of Firefox did show that problem too.

Not using IE and my infrastructure is OS X-centric. Just diving into Linux thanks to ReadyNas. The status changes do reflect, from what I can tell. For split seconds, the global user daemon starts, then the web browser refreshes and the daemon stops. Then nothing. I am also running the latest version of Firefox and Safari. Although I am running a few Firefox plugins, but I doubt that is the issue, since status do update on both Safari and Firefox.

WhoCares? wrote:
Next, the scripts managing the different Dropbox daemons are meant to run under the "admin" account. By manually starting/stopping/installing stuff there's a good chance that the ownership of some files needed by the web interface and the daemons has changed which in turn could prevent the whole system from functioning properly.

I initially tried installing everything as designed, using Frontview's add-on install page. When the Global user daemon was not starting, little by little I started doing things manually. However, the majority of my SSH is for checking and verifying stuff, until my last attempt.

WhoCares? wrote:
What would be interesting to see is the contents of the /tmp directory. There should be some files that contain the logs of the various deamons talking to the Dropbox master server. If those aren't created or contain nothing the starting/stopping/authenticating will fail.

I think you are talking about the "dropbox.admin" file? If not, which one's are you talking about so I can show you. Anyway, here are the current contents of the /tmp directory:

ProBiz-NAS:/tmp# ls -la
total 1268
drwxrwxrwt  5 admin admin    4096 2013-07-07 06:25 .
drwxr-xr-x 23 root  root     4096 2013-07-06 22:58 ..
drwxrwxrwx  2 admin admin    4096 2013-07-06 23:40 addons
-rw-r--r--  1 root  root       12 2013-07-04 22:11 .dhcp_server
-rw-r--r--  1 admin admin       0 2013-07-07 00:09 dropbox.admin
-rw-------  1 admin admin    1118 2013-07-07 00:09 dropbox_errorZLfGLO.txt
-rw-r--r--  1 root  root        0 2013-07-05 10:42 errors_001.log
-rw-r--r--  1 root  root        0 2013-07-05 08:56 group.16698
-rw-r--r--  1 root  root        0 2013-07-05 01:14 group.8976
drwxrwxrwt  2 root  root     4096 2013-07-04 23:37 .ICE-unix
-rw-r--r--  1 root  root      935 2010-04-22 21:57 istat.conf
-rwxr-xr-x  1 root  root  1155175 2012-11-23 10:57 istatd
srwxr-xr-x  1 admin admin       0 2013-07-06 22:58 istatd.sock
srw-------  1 root  root        0 2013-07-06 22:58 pureftpd.sock
-rw-r--r--  1 admin admin   98304 2013-07-06 23:53 update_file
drwxrwxrwt  2 root  root     4096 2013-07-04 23:37 .X11-unix

WhoCares? wrote:
Generally it's a very *bad* idea to try to fix things manually using the "root" account. This is more likely to break things than to fix them.

Yeah, I know! Especially if you don't know what you are doing, like me :oops: However, I am learning a lot, which is always fun. Luckily, there is not super critical data on this box. This is all my work stuff really. My other ReadyNAS has all my critical data, which is backed up by CrashPlan. But I digress...

WhoCares? wrote:
The same is true for the global /c/Dropbox share. As with other parts of the add-on, it is crucial that the ownership as well as the permissions of that directory match what is expected by the daemons and the Frontview tools. Manually creating the directory is more likely to create problems instead of fixing them.

The /Dropbox share was created within Frontview's share's tab. I made sure to follow instructions as much as possible. I figured that the permissions all have to be the same. If not, the instructions would say to SSH into the box. I have not tampered with the permissions of the /Dropbox share. Here they are currently for reference:

ProBiz-NAS:/# ls -l
total 76
lrwxrwxrwx  1 root     16 2013-07-05 01:14 addons-config -> /c/addons-config
lrwxrwxrwx  1 root      9 2013-07-04 13:14 backup -> /c/backup
drwxr-xr-x  2 root   4096 2013-07-04 13:03 bin
drwxrwxrwx 20 root   4096 2013-07-07 00:09 c
drwxr-xr-x 18 root   5040 2013-07-06 22:58 dev
lrwxrwxrwx  1 root     10 2013-07-05 08:58 Dropbox -> /c/Dropbox
drwxr-xr-x 73 root   4096 2013-07-06 22:57 etc
lrwxrwxrwx  1 root     14 2013-07-05 01:49 fortressftp -> /c/fortressftp
drwxr-xr-x  6 admin  4096 2013-07-04 13:03 frontview
drwxr-xr-x  3 root   4096 2013-07-04 13:03 home
drwxr-xr-x  2 root   4096 2007-09-07 10:53 initrd
lrwxrwxrwx  1 root      9 2013-07-05 01:30 janftp -> /c/janftp
drwxr-xr-x 13 root   4096 2013-07-04 13:03 lib
drwxr-xr-x  2 root   4096 2013-07-04 13:03 lib64
drwx------  2 root  16384 2013-07-04 13:03 lost+found
drwxr-xr-x  2 root   4096 2006-10-28 07:06 mnt
drwxr-xr-x  2 root   4096 2010-05-15 02:29 opt
dr-xr-xr-x 97 root      0 2013-07-06 22:57 proc
drwxrwxrwt  3 root      0 2013-07-07 09:23 ramfs
drwxr-xr-x  3 root   4096 2013-07-06 22:57 root
drwxr-xr-x  2 root   4096 2013-07-04 13:03 sbin
drwxr-xr-x 12 root      0 2013-07-06 22:57 sys
drwxrwxrwt  5 admin  4096 2013-07-07 06:25 tmp
drwxrwxrwt  2 root     40 2013-07-06 22:57 USB
drwxr-xr-x 11 root   4096 2008-09-20 04:27 usr
drwxr-sr-x 15 root   4096 2009-11-20 06:29 var
lrwxrwxrwx  1 root     10 2013-07-05 01:14 webroot -> /c/webroot

WhoCares? wrote:
The Dropbobx add-on should create all needed directories for you and if it doesn't that points to a more basic problem preventing the add-on from installing properly. -Stefan

It does, here is the current /c/ permissions and users for reference:

ProBiz-NAS:/# ls -la /c/
total 108
drwxrwxrwx 20 root     root      4096 2013-07-07 00:09 .
drwxr-xr-x 23 root     root      4096 2013-07-06 22:58 ..
drwxr-xr-x  3 root     root      4096 2013-07-05 00:10 addons-config
-rw-------  1 root     root      8192 2013-07-07 00:09 aquota.group
-rw-------  1 root     root      8192 2013-07-07 00:09 aquota.user
drwxrwxrwt  2 nobody   nogroup   4096 2013-07-04 13:13 backup
drwx------  3 admin    admin     4096 2013-07-07 00:09 .dropbox
drwx-----T  3 nobody   nogroup   4096 2013-07-06 23:35 Dropbox
drwxr-xr-x  5 admin    admin     4096 2013-07-07 00:04 .dropbox-dist
drwxr-xr-x  5 admin    admin     4096 2013-07-06 23:51 .dropbox-dist.2.2.8
drwx--S--T 36 fortress fortress  4096 2013-07-06 21:01 fortressftp
drwxrwxrwx  2 admin    admin     4096 2013-07-05 00:15 .gitscm
drwxr-xr-x  5 admin    admin     4096 2013-07-06 21:00 home
drwxr-xr-x  2 root     root      4096 2013-07-04 13:13 .iscsi
drwx-----T  2 jan      jan       4096 2013-07-05 02:32 janftp
drwx------  2 root     root     16384 2013-07-04 13:12 lost+found
drwxrwxrwx  2 admin    users     4096 2013-07-05 02:14 media
drwxr-xr-x  7 admin    admin     4096 2013-07-05 00:09 .puremgr
drwxr-xr-x  6 admin    admin     4096 2013-07-06 22:58 .pyload
drwxr-xr-x  6 root     root      4096 2010-05-15 02:23 .rfw
drwxr-xr-x  2 ReadyNAS root      4096 2013-07-04 13:13 .timemachine
drwxr-xr-x  3 root     root      4096 2011-03-29 08:51 webroot

The only directory that is not created is the /c/Dropbox for the Global Dropbox user, which is the one I am trying to initialize, with no success. However, I created on Frontview, per instructions.