NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

fifer55's avatar
fifer55
Apprentice
Jul 06, 2013

DropBox: Not able to link account

Hello everyone, I recently purchased the following addon - Dropbox (vInstall-rnx86-1.0.1):
viewtopic.php?f=48&t=58647

It was installed on a newly updated (factory reset) ReadyNas Pro Business Edition.

Currently, the following addons are also installed:
DAAPD!!FireFly!!1.0.3!!start-stop-daemon -S -q -x /usr/sbin/mt-daapd!!start-stop-daemon -K -n mt-daapd
PYTHON27!!Python2.7!!2.7.3-rnx86-1.0.1!!/etc/frontview/addons/bin/PYTHON27/start.sh!!/etc/frontview/addons/bin/PYTHON27/stop.sh!!Other!!current_url==http://readynasxtras.com/addons/x86/xml/PYTHON27_CURRENT.xml::detail_url==http://readynasxtras.com/readynas-x86-add-ons/python-27-x86::icon_url==/addons/PYTHON27/python_logo.gif
PHP5!!PHP5!!5.4.15-x86-4.4.0!!/etc/frontview/addons/bin/PHP5/start.sh!!/etc/frontview/addons/bin/PHP5/stop.sh!!Other!!current_url==http://readynasxtras.com/addons/x86/xml/PHP5_CURRENT.xml::detail_url==http://readynasxtras.com/readynas-x86-add-ons/php-53-x86::icon_url==http://readynasxtras.com/addons/x86/img/php_logo.gif
ENABLERSYNCSSH!!RsyncSsh!!x86-0.1.7!!/etc/frontview/addons/bin/ENABLERSYNCSSH/start.sh!!/etc/frontview/addons/bin/ENABLERSYNCSSH/stop.sh!!Other
PYLOAD!!PyLoad!!0.4.9-rnx86-0.3.3!!/etc/frontview/addons/bin/PYLOAD/start.sh!!/etc/frontview/addons/bin/PYLOAD/stop.sh!!Other!!current_url==http://readynasxtras.com/addons/x86/xml/PyLoad_CURRENT.xml::detail_url==http://readynasxtras.com/readynas-x86-add-ons/pyload-x86::icon_url==http://readynasxtras.com/addons/x86/img/pyload.jpg
ISTATD!!Istatd!!1.7!!/etc/frontview/addons/bin/ISTATD/start.sh!!/etc/frontview/addons/bin/ISTATD/stop.sh!!Other
NASMONITOR!!Nas Monitor!!3.6.11!!/etc/frontview/addons/bin/NASMONITOR/start.sh!!/etc/frontview/addons/bin/NASMONITOR/stop.sh!!Other!!current_url==https://www.readynas.com/contributed/super-poussin/x86/NASMONITOR_CURRENT.xml::detail_url==https://www.readynas.com/contributed/super-poussin/x86/NASMONITOR_REL.html::icon_url==https://www.readynas.com/contributed/super-poussin/x86/NASMONITOR_ICON.jpg
GITSCM!!gitscm!!1.7.1-readypro-0.1.2!!/etc/frontview/addons/bin/GITSCM/start.sh!!/etc/frontview/addons/bin/GITSCM/stop.sh!!Other
FFMPEG!!ffmpeg!!1.3!!/etc/frontview/addons/bin/FFMPEG/start.sh!!/etc/frontview/addons/bin/FFMPEG/stop.sh!!Other!!current_url==https://www.readynas.com/contributed/super-poussin/x86/FFMPEG_CURRENT.xml::detail_url==https://www.readynas.com/contributed/super-poussin/x86/FFMPEG_REL.html::icon_url==https://www.readynas.com/contributed/super-poussin/x86/ffmpeg-logo.png


In addition, the following services are running:
APACHE=0
APACHESSL=1
ATALKD=0
AUTOMATIC_VOLUME_EXPANSION=1
AUTO_CHECK_UPDATE=1
AUTO_DOWNLOAD_UPDATE=1
BONJOUR=0
BONJOUR_AFP=0
BONJOUR_FRONTVIEW=0
BONJOUR_PRINTER=0
BONJOUR_SUPPORT=1
CSV_USERADD_SUPPORT=1
DAAPD=0
DAAPD_SUPPORT=1
DISALLOW_PASSWORD_CHANGE=1
DISKCACHE=1
DOMAIN_SUPPORT=1
ENABLERSYNCSSH=1
ENABLERSYNCSSH_SUPPORT=1
ENABLE_POWERON_TIMER=0
ENABLE_POWERON_TIMER_SUPPORT=1
ENCODE=utf-8
FAN=1,1,0,0,0
FFMPEG=1
FFMPEG_SUPPORT=1
FLASH_AUTO_COPY=0
FLASH_OWNER=admin
FLASH_PATH=Pictures
FLASH_SHARE=media
FTP_MASQUERADE_ADDRESS=xxx.xxx.xxx.xxx
FTP_MODE=user
FTP_PASSIVE_END=xxxx
FTP_PASSIVE_START=xxxx
FTP_PORT=21
FTP_UPLOAD_RESUME=0
GITSCM=1
GITSCM_SUPPORT=1
HTTPS_SSL_KEY_HOST=192.168.168.168
IPV6_ASSIGN_bond0=OFF
IPV6_ASSIGN_eth0=OFF
IPV6_ASSIGN_eth1=OFF
ISTATD=1
ISTATD_PASSWORD=xxxxx
ISTATD_SUPPORT=1
JOURNAL=ordered
JUMBO_FRAMES_bond0=0
JUMBO_FRAMES_eth0=0
JUMBO_FRAMES_eth1=0
LANGUAGE=en-us
LANGUAGES_SUPPORTED=en-us/utf-8,en-us/ascii,ja/euc-jp,ko/euc-kr,ja/utf-8,ko/utf-8,zh-cn/utf-8,zh-tw/utf-8,ru/utf-8,es/utf-8,pt/utf-8,de/utf-8,fr/utf-8,it/utf-8,nl/utf-8,pl/utf-8,cs/utf-8,hu/utf-8,nb/utf-8,da/utf-8,fi/utf-8,sv/utf-8
MONITOR=board_temp,fan,disk_full,quota_exceeded,disk_temp
NASMONITOR=1
NASMONITOR_SUPPORT=1
NETATALK=1
NFS=1
NTPDATE=1
OPTIMIZE_FOR_MAC=1
PHP5=1
PHP5_SUPPORT=1
PROFTPD=1
PYLOAD=1
PYLOAD_SUPPORT=1
PYTHON27=1
PYTHON27_SUPPORT=1
RAID_MODE=1
READYTIVOD=0
RESYNC_UNCLEAN_SHUTDOWN=1
RSYNC=0
RSYNC_SUPPORT=1
SAMBA=0
SHAREACCESS=SAMBA,NETATALK
SHUTDOWN_ON_DISK_OVERTEMP=1
SMTP_PROVIDER=ITEM_ALERTS_CUSTOM
SNMP=1
SNMP_COMMUNITY=public
SNMP_SUPPORT=1
SPEED_DUPLEX_eth0=AUTO_NEGOTIATION
SPEED_DUPLEX_eth1=AUTO_NEGOTIATION
SSH=1
SSHKEY=rsa
SUPPORT_UTF8_NAMES=1
TEMP=1,1,0
UDHCPD=0
UPNP=0
UPNPAV=0
UPNPAV_SUPPORT=1
UPNP_SUPPORT=1
UPS_LOWBATT_PCT=0
UPS_SHARING=0
USER_HOME_DIRECTORY=0
WAKE_ON_LAN=1
WIZD=0
WIZD_SUPPORT=0

Now, the installs goes without a hitch. The current Installed version is: 2.2.8. I immediately update to the latest stable release of 2.2.9. So far, so good.

Next, I follow the instructions on how to configure the Drobox add on:
viewtopic.php?f=48&t=58647

This is where I get stuck, specifically the configuration step. After enabling the add on and the Global dropbox, the daemon starts, then stops. After which it never starts again.


The only way to have it start again is to remove the addon, then manually remove all dropbox folders, even after clearing my web caches on several web browsers and rebooting the ReadyNAS itself. Before I remove the addon and after, no dice. The same when I remove, reboot, re-install.

After removing the add on and clicking on "Cancel" during removal, I am manually deleting the following folders by doing:
ProBiz-NAS:/# find -iname *dropbox*

which returns directories in:
/c/.dropbox/
/c/.dropbox-dist.2.2.8/
/c/.dropbox-dist.2.2.9/
/c/Dropbox (this one is OK, it is a share that I created, since Dropbox doesn't automatically create one for Global)

A simple 
rm-rf .dropbox*
removes all directories pertaining to Dropbox that are left behind.

Now, no directories exist except my share, however, there are also some text files in "/tmp/"
./tmp/dropbox_error1DQn6M.txt
./tmp/dropbox_errorcxtOPP.txt
./tmp/dropbox_errorNW9OrF.txt
./tmp/dropbox_errorSUJlLz.txt
./tmp/dropbox_errorxOa2mm.txt
./tmp/dropbox_error4ecQAi.txt
./tmp/dropbox_errorPi68YR.txt
./tmp/dropbox_error5aCw15.txt

WTH!?

ProBiz-NAS:/tmp# cat dropbox_error1DQn6M.txt 
pid:	6277
ppid:	6276
uid:	98
user_info:	pwd.struct_passwd(pw_name='admin', pw_passwd='x', pw_uid=98, pw_gid=98, pw_gecos='', pw_dir='/c/home/admin', pw_shell='/bin/false')
effective_user_info:	pwd.struct_passwd(pw_name='admin', pw_passwd='x', pw_uid=98, pw_gid=98, pw_gecos='', pw_dir='/c/home/admin', pw_shell='/bin/false')
euid:	98
gid:	98
egid:	98
group_info:	grp.struct_group(gr_name='admin', gr_passwd='x', gr_gid=98, gr_mem=[])
effective_group_info:	grp.struct_group(gr_name='admin', gr_passwd='x', gr_gid=98, gr_mem=[])
appdata:	u'/c/.dropbox'
real_path=u'/c/.dropbox'
	mode=040700	uid=98	gid=98
parent	mode=040777	uid=0	gid=0
dropbox_path:	u'/c/Dropbox'
real_path=u'/c/Dropbox'
	mode=041700	uid=65534	gid=65534
parent	mode=040777	uid=0	gid=0
HOME:	/c
tempdir:	'/tmp'
real_path='/tmp'
	mode=041777	uid=0	gid=0
parent	mode=040755	uid=0	gid=0
Traceback (most recent call last):
  File "dropbox/client/main.py", line 1239, in main_startup
  File "dropbox/client/main.py", line 765, in run
  File "dropbox/client/main.py", line 712, in create_keystore_and_unlink_cookie
Exception: statvfs failed with retval -1


ProBiz-NAS:/tmp# cat dropbox_errorcxtOPP.txt 
pid:	6831
ppid:	6829
uid:	98
user_info:	pwd.struct_passwd(pw_name='admin', pw_passwd='x', pw_uid=98, pw_gid=98, pw_gecos='', pw_dir='/c/home/admin', pw_shell='/bin/false')
effective_user_info:	pwd.struct_passwd(pw_name='admin', pw_passwd='x', pw_uid=98, pw_gid=98, pw_gecos='', pw_dir='/c/home/admin', pw_shell='/bin/false')
euid:	98
gid:	98
egid:	98
group_info:	grp.struct_group(gr_name='admin', gr_passwd='x', gr_gid=98, gr_mem=[])
effective_group_info:	grp.struct_group(gr_name='admin', gr_passwd='x', gr_gid=98, gr_mem=[])
appdata:	u'/c/.dropbox'
real_path=u'/c/.dropbox'
	mode=040700	uid=98	gid=98
parent	mode=040777	uid=0	gid=0
dropbox_path:	u'/c/Dropbox'
real_path=u'/c/Dropbox'
	mode=041700	uid=65534	gid=65534
parent	mode=040777	uid=0	gid=0
HOME:	/c
tempdir:	'/tmp'
real_path='/tmp'
	mode=041777	uid=0	gid=0
parent	mode=040755	uid=0	gid=0
Traceback (most recent call last):
  File "dropbox/client/main.py", line 1239, in main_startup
  File "dropbox/client/main.py", line 765, in run
  File "dropbox/client/main.py", line 712, in create_keystore_and_unlink_cookie
Exception: statvfs failed with retval -1


ProBiz-NAS:/tmp# cat dropbox_errorNW9OrF.txt 
pid:	6682
ppid:	6681
uid:	98
user_info:	pwd.struct_passwd(pw_name='admin', pw_passwd='x', pw_uid=98, pw_gid=98, pw_gecos='', pw_dir='/c/home/admin', pw_shell='/bin/false')
effective_user_info:	pwd.struct_passwd(pw_name='admin', pw_passwd='x', pw_uid=98, pw_gid=98, pw_gecos='', pw_dir='/c/home/admin', pw_shell='/bin/false')
euid:	98
gid:	98
egid:	98
group_info:	grp.struct_group(gr_name='admin', gr_passwd='x', gr_gid=98, gr_mem=[])
effective_group_info:	grp.struct_group(gr_name='admin', gr_passwd='x', gr_gid=98, gr_mem=[])
appdata:	u'/c/.dropbox'
real_path=u'/c/.dropbox'
	mode=040700	uid=98	gid=98
parent	mode=040777	uid=0	gid=0
dropbox_path:	u'/c/Dropbox'
real_path=u'/c/Dropbox'
	mode=041700	uid=65534	gid=65534
parent	mode=040777	uid=0	gid=0
HOME:	/c
tempdir:	'/tmp'
real_path='/tmp'
	mode=041777	uid=0	gid=0
parent	mode=040755	uid=0	gid=0
Traceback (most recent call last):
  File "dropbox/client/main.py", line 1239, in main_startup
  File "dropbox/client/main.py", line 765, in run
  File "dropbox/client/main.py", line 712, in create_keystore_and_unlink_cookie
Exception: statvfs failed with retval -1


From here, the rest of the error logs return the same content.

Now, I have been reading the following topics:
viewtopic.php?f=36&t=65909
hmm, I have PHP enabled...

viewtopic.php?f=36&t=60941&start=30#p349866
Not an issue for me, I use the following:


Finally, here is some information that might be useful:
ProBiz-NAS:/# ls -la /tmp
total 1196
drwxrwxrwt  5 root  root     4096 2013-07-06 13:17 .
drwxr-xr-x 23 root  root     4096 2013-07-06 13:00 ..
drwxrwxrwx  2 admin admin    4096 2013-07-06 12:51 addons
-rw-r--r--  1 root  root       12 2013-07-04 22:11 .dhcp_server
-rw-------  1 admin admin    1114 2013-07-06 12:51 dropbox_error1DQn6M.txt
-rw-------  1 admin admin    1114 2013-07-06 12:52 dropbox_error4ecQAi.txt
-rw-------  1 admin admin    1114 2013-07-06 12:52 dropbox_error5aCw15.txt
-rw-------  1 admin admin    1114 2013-07-06 12:53 dropbox_errorcxtOPP.txt
-rw-------  1 admin admin    1114 2013-07-06 12:53 dropbox_errorNW9OrF.txt
-rw-------  1 admin admin    1114 2013-07-06 12:53 dropbox_errorPi68YR.txt
-rw-------  1 admin admin    1114 2013-07-06 12:52 dropbox_errorSUJlLz.txt
-rw-------  1 admin admin    1114 2013-07-06 12:59 dropbox_errorxOa2mm.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 12:40 istatd.sock
srw-------  1 root  root        0 2013-07-06 12:40 pureftpd.sock
drwxrwxrwt  2 root  root     4096 2013-07-04 23:37 .X11-unix


ProBiz-NAS:/# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/md0              4.0G  462M  3.4G  12% /
tmpfs                  16K     0   16K   0% /USB
/dev/c/c               19T  2.4T   16T  14% /c
/c/fortressftp         19T  2.4T   16T  14% /home/ftp/fortressftp
/c/janftp              19T  2.4T   16T  14% /home/ftp/janftp


I have an account and everything with dropbox, but I just can't get the thing up and running. Any help would be greatly appreciated.
General
ReadyNAS Add-ons for Legacy ReadyNAS

26 Replies

Replies have been turned off for this discussion
Show More
  • fifer55's avatar
    fifer55
    Apprentice
    Jul 07, 2013
    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.
  • WhoCares_'s avatar
    WhoCares_
    Mentor
    Jul 08, 2013
    Would be nice to know what's in the "dropbox_errorZLfGLO.txt" file in your /tmp directory. This is not normally created by the add-on and may well contain some hints as to where the problem with your Dropbox installation is.

    -Stefan
  • fifer55's avatar
    fifer55
    Apprentice
    Jul 08, 2013
    WhoCares? wrote:
    Would be nice to know what's in the "dropbox_errorZLfGLO.txt" file in your /tmp directory. This is not normally created by the add-on and may well contain some hints as to where the problem with your Dropbox installation is.

    -Stefan


    Thanks for your help Stefan.

    Anytime I try to start the Global Dropbox User Daemon, an error is logged in /tmp. It is always the same content, regardless of file name.

    pid: 6382
    ppid: 6380
    uid: 98
    user_info: pwd.struct_passwd(pw_name='admin', pw_passwd='x', pw_uid=98, pw_gid=98, pw_gecos='', pw_dir='/c/home/admin', pw_shell='/bin/false')
    effective_user_info: pwd.struct_passwd(pw_name='admin', pw_passwd='x', pw_uid=98, pw_gid=98, pw_gecos='', pw_dir='/c/home/admin', pw_shell='/bin/false')
    euid: 98
    gid: 98
    egid: 98
    group_info: grp.struct_group(gr_name='admin', gr_passwd='x', gr_gid=98, gr_mem=[])
    effective_group_info: grp.struct_group(gr_name='admin', gr_passwd='x', gr_gid=98, gr_mem=[])
    appdata: u'/c/.dropbox'
    real_path=u'/c/.dropbox'
    mode=040700 uid=98 gid=98
    parent mode=040777 uid=0 gid=0
    dropbox_path: u'/c/Dropbox'
    real_path=u'/c/Dropbox'
    mode=041700 uid=65534 gid=65534
    parent mode=040777 uid=0 gid=0
    HOME: /c
    tempdir: '/tmp'
    real_path='/tmp'
    mode=041777 uid=98 gid=98
    parent mode=040755 uid=0 gid=0
    Traceback (most recent call last):
    File "dropbox/client/main.py", line 1377, in main_startup
    File "dropbox/client/main.py", line 895, in run
    File "dropbox/client/main.py", line 844, in create_keystore_and_unlink_cookie
    Exception: statvfs failed with retval -1
  • WhoCares_'s avatar
    WhoCares_
    Mentor
    Jul 08, 2013
    The problem seems to be that the Dropbox daemon is unable to create one or more of it's needed directories. My suggestion would be to clean out all Dropbox related files and directories by first uninstalling the Dropbox add-on and then manually check for either "Dropbox" or ".dropbox*" directories in /c and /c/home/<userdirs> manually and remove the remaining ones there. Next check for space on the /tmp drive and if everything looks fine try another install of the add-on. If that fails again, leave as is and check the dropbox_errorXXXX file again. If it still reports the same error, I'd be interested in an ls -al of "/c", "/tmp" and "/c/home".

    -Stefan
  • fifer55's avatar
    fifer55
    Apprentice
    Jul 08, 2013
    WhoCares? wrote:
    The problem seems to be that the Dropbox daemon is unable to create one or more of it's needed directories.

    D'oh. OK, figured something was not being created.

    WhoCares? wrote:
    My suggestion would be to clean out all Dropbox related files and directories by first uninstalling the Dropbox add-on and then manually check for either "Dropbox" or ".dropbox*" directories in /c and /c/home/<userdirs> manually and remove the remaining ones there.

    OK, first let me show you anything related to Dropbox that I have.
    ProBiz-NAS:/# find -name *dropbox*
    ./tmp/dropbox_errord1Ahbi.txt
    ./tmp/dropbox_error6lRXIV.txt
    ./tmp/dropbox_errory6FEDe.txt
    ./tmp/dropbox_errordjt9fv.txt
    ./tmp/dropbox.admin
    ./tmp/dropbox_errorxGn0Oe.txt
    ./tmp/dropbox_errorUx8EMQ.txt
    ./tmp/dropbox_erroryAZggK.txt
    ./tmp/dropbox_errorNqGvLP.txt
    ./tmp/dropbox_errorgLdapg.txt
    ./tmp/dropbox_errorzeN41M.txt
    ./tmp/dropbox_errorOjhksz.txt
    ./tmp/dropbox_errorUjvy_Q.txt
    ./tmp/dropbox_errorV4Qhgm.txt
    ./tmp/dropbox_errorrznHye.txt
    ./tmp/dropbox_errorgHsNkD.txt
    ./tmp/dropbox_erroreO5b9b.txt
    ./tmp/dropbox_error0ZtpEB.txt
    ./tmp/dropbox_errorZiccgP.txt
    ./tmp/dropbox_errorF2NnFo.txt
    ./tmp/dropbox_errorfqLqPg.txt
    ./tmp/dropbox.fortress
    ./tmp/dropbox_errorbfT1LT.txt
    ./tmp/dropbox_errorzpsBBr.txt
    ./tmp/dropbox_error3ou2t0.txt
    ./usr/share/dropbox
    ./usr/share/dropbox/dropbox_up
    ./usr/share/dropbox/dropboxcheck
    ./usr/share/dropbox/run_dropbox.sh
    ./var/spool/frontview/shutdown/099_dropbox_shutdown
    find: ./proc/15995/net: Invalid argument
    ./c/.dropbox-dist.2.2.8
    ./c/.dropbox-dist.2.2.8/images/emblems/emblem-dropbox-unsyncable.icon
    ./c/.dropbox-dist.2.2.8/images/emblems/emblem-dropbox-syncing.png
    ./c/.dropbox-dist.2.2.8/images/emblems/emblem-dropbox-app.svg
    ./c/.dropbox-dist.2.2.8/images/emblems/emblem-dropbox-selsync.icon
    ./c/.dropbox-dist.2.2.8/images/emblems/emblem-dropbox-uptodate.icon
    ./c/.dropbox-dist.2.2.8/images/emblems/emblem-dropbox-uptodate.png
    ./c/.dropbox-dist.2.2.8/images/emblems/emblem-dropbox-app.icon
    ./c/.dropbox-dist.2.2.8/images/emblems/emblem-dropbox-selsync.png
    ./c/.dropbox-dist.2.2.8/images/emblems/emblem-dropbox-syncing.icon
    ./c/.dropbox-dist.2.2.8/images/emblems/emblem-dropbox-unsyncable.png
    ./c/.dropbox-dist.2.2.8/images/hicolor/16x16/status/dropboxstatus-blank.png
    ./c/.dropbox-dist.2.2.8/images/hicolor/16x16/status/dropboxstatus-x.png
    ./c/.dropbox-dist.2.2.8/images/hicolor/16x16/status/dropboxstatus-logo.png
    ./c/.dropbox-dist.2.2.8/images/hicolor/16x16/status/dropboxstatus-busy.png
    ./c/.dropbox-dist.2.2.8/images/hicolor/16x16/status/dropboxstatus-idle.png
    ./c/.dropbox-dist.2.2.8/images/hicolor/16x16/status/dropboxstatus-busy2.png
    ./c/.dropbox-dist.2.2.8/dropboxd
    ./c/.dropbox-dist.2.2.8/dropbox
    ./c/.dropbox-dist.2.2.8/run_dropbox.sh
    ./c/.dropbox-dist
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-unsyncable.icon
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-syncing.png
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-app.svg
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-selsync.icon
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-uptodate.icon
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-uptodate.png
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-app.icon
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-selsync.png
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-syncing.icon
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-unsyncable.png
    ./c/.dropbox-dist/images/hicolor/16x16/status/dropboxstatus-blank.png
    ./c/.dropbox-dist/images/hicolor/16x16/status/dropboxstatus-x.png
    ./c/.dropbox-dist/images/hicolor/16x16/status/dropboxstatus-logo.png
    ./c/.dropbox-dist/images/hicolor/16x16/status/dropboxstatus-busy.png
    ./c/.dropbox-dist/images/hicolor/16x16/status/dropboxstatus-idle.png
    ./c/.dropbox-dist/images/hicolor/16x16/status/dropboxstatus-busy2.png
    ./c/.dropbox-dist/dropboxd
    ./c/.dropbox-dist/dropbox
    ./c/.dropbox-dist/run_dropbox.sh
    ./c/.dropbox
    ./etc/cron.d/dropboxcheck
    ./etc/frontview/addons/ui/DROPBOX/dropbox_logo.gif
    ./etc/default/dropbox
    ./etc/init.d/dropbox
    ProBiz-NAS:/#

    Now that I know where everything is, let me uninstall via Frontview... Done. I am left with this:
    ProBiz-NAS:/# find -name *dropbox*                                                                                                                                                                       
    ./tmp/dropbox_errord1Ahbi.txt
    ./tmp/dropbox_error6lRXIV.txt
    ./tmp/dropbox_errory6FEDe.txt
    ./tmp/dropbox_errordjt9fv.txt
    ./tmp/dropbox_errorxGn0Oe.txt
    ./tmp/dropbox_errorUx8EMQ.txt
    ./tmp/dropbox_erroryAZggK.txt
    ./tmp/dropbox_errorNqGvLP.txt
    ./tmp/dropbox_errorgLdapg.txt
    ./tmp/dropbox_errorzeN41M.txt
    ./tmp/dropbox_errorOjhksz.txt
    ./tmp/dropbox_errorUjvy_Q.txt
    ./tmp/dropbox_errorV4Qhgm.txt
    ./tmp/dropbox_errorrznHye.txt
    ./tmp/dropbox_errorgHsNkD.txt
    ./tmp/dropbox_erroreO5b9b.txt
    ./tmp/dropbox_error0ZtpEB.txt
    ./tmp/dropbox_errorZiccgP.txt
    ./tmp/dropbox_errorF2NnFo.txt
    ./tmp/dropbox_errorfqLqPg.txt
    ./tmp/dropbox_errorbfT1LT.txt
    ./tmp/dropbox_errorzpsBBr.txt
    ./tmp/dropbox_error3ou2t0.txt
    ./c/.dropbox-dist.2.2.8
    ./c/.dropbox-dist.2.2.8/images/emblems/emblem-dropbox-unsyncable.icon
    ./c/.dropbox-dist.2.2.8/images/emblems/emblem-dropbox-syncing.png
    ./c/.dropbox-dist.2.2.8/images/emblems/emblem-dropbox-app.svg
    ./c/.dropbox-dist.2.2.8/images/emblems/emblem-dropbox-selsync.icon
    ./c/.dropbox-dist.2.2.8/images/emblems/emblem-dropbox-uptodate.icon
    ./c/.dropbox-dist.2.2.8/images/emblems/emblem-dropbox-uptodate.png
    ./c/.dropbox-dist.2.2.8/images/emblems/emblem-dropbox-app.icon
    ./c/.dropbox-dist.2.2.8/images/emblems/emblem-dropbox-selsync.png
    ./c/.dropbox-dist.2.2.8/images/emblems/emblem-dropbox-syncing.icon
    ./c/.dropbox-dist.2.2.8/images/emblems/emblem-dropbox-unsyncable.png
    ./c/.dropbox-dist.2.2.8/images/hicolor/16x16/status/dropboxstatus-blank.png
    ./c/.dropbox-dist.2.2.8/images/hicolor/16x16/status/dropboxstatus-x.png
    ./c/.dropbox-dist.2.2.8/images/hicolor/16x16/status/dropboxstatus-logo.png
    ./c/.dropbox-dist.2.2.8/images/hicolor/16x16/status/dropboxstatus-busy.png
    ./c/.dropbox-dist.2.2.8/images/hicolor/16x16/status/dropboxstatus-idle.png
    ./c/.dropbox-dist.2.2.8/images/hicolor/16x16/status/dropboxstatus-busy2.png
    ./c/.dropbox-dist.2.2.8/dropboxd
    ./c/.dropbox-dist.2.2.8/dropbox
    ./c/.dropbox-dist.2.2.8/run_dropbox.sh
    ./c/.dropbox
    ProBiz-NAS:/#

    Now to manually remove via SSH any/all Dropbox related directories that I know to look for... Done.
    ProBiz-NAS:/# cd c/
    ProBiz-NAS:/c# ls -la
    total 72
    drwxrwxrwx 11 root     root      4096 2013-07-08 00:03 .
    drwxr-xr-x 23 root     root      4096 2013-07-07 23:54 ..
    -rw-------  1 root     root      8192 2013-07-08 00:03 aquota.group
    -rw-------  1 root     root      8192 2013-07-08 00:03 aquota.user
    drwxrwxrwt  7 nobody   nogroup   4096 2013-07-07 23:03 backup
    drwx------  3 admin    admin     4096 2013-07-07 23:44 .dropbox
    drwxr-xr-x  5 admin    admin     4096 2013-07-07 23:41 .dropbox-dist.2.2.8
    drwxrwsrwx 15 fortress fortress  4096 2013-07-07 23:03 fortressftp
    drwxr-xr-x  5 admin    admin     4096 2013-07-06 21:00 home
    drwx------  2 root     root     16384 2013-07-04 13:12 lost+found
    drwxrwxrwx  2 nobody   nogroup   4096 2013-07-07 23:27 media
    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
    ProBiz-NAS:/c# rm -rf .dropbox*
    ProBiz-NAS:/c# ls -la
    total 64
    drwxrwxrwx  9 root     root      4096 2013-07-08 00:06 .
    drwxr-xr-x 23 root     root      4096 2013-07-07 23:54 ..
    -rw-------  1 root     root      8192 2013-07-08 00:06 aquota.group
    -rw-------  1 root     root      8192 2013-07-08 00:06 aquota.user
    drwxrwxrwt  7 nobody   nogroup   4096 2013-07-07 23:03 backup
    drwxrwsrwx 15 fortress fortress  4096 2013-07-07 23:03 fortressftp
    drwxr-xr-x  5 admin    admin     4096 2013-07-06 21:00 home
    drwx------  2 root     root     16384 2013-07-04 13:12 lost+found
    drwxrwxrwx  2 nobody   nogroup   4096 2013-07-07 23:27 media
    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
    ProBiz-NAS:/c#

    Let me see what is left over, in respect to Dropbox...
    ProBiz-NAS:/c# cd ..
    ProBiz-NAS:/# find -name *dropbox*
    ./tmp/dropbox_errord1Ahbi.txt
    ./tmp/dropbox_error6lRXIV.txt
    ./tmp/dropbox_errory6FEDe.txt
    ./tmp/dropbox_errordjt9fv.txt
    ./tmp/dropbox_errorxGn0Oe.txt
    ./tmp/dropbox_errorUx8EMQ.txt
    ./tmp/dropbox_erroryAZggK.txt
    ./tmp/dropbox_errorNqGvLP.txt
    ./tmp/dropbox_errorgLdapg.txt
    ./tmp/dropbox_errorzeN41M.txt
    ./tmp/dropbox_errorOjhksz.txt
    ./tmp/dropbox_errorUjvy_Q.txt
    ./tmp/dropbox_errorV4Qhgm.txt
    ./tmp/dropbox_errorrznHye.txt
    ./tmp/dropbox_errorgHsNkD.txt
    ./tmp/dropbox_erroreO5b9b.txt
    ./tmp/dropbox_error0ZtpEB.txt
    ./tmp/dropbox_errorZiccgP.txt
    ./tmp/dropbox_errorF2NnFo.txt
    ./tmp/dropbox_errorfqLqPg.txt
    ./tmp/dropbox_errorbfT1LT.txt
    ./tmp/dropbox_errorzpsBBr.txt
    ./tmp/dropbox_error3ou2t0.txt
    ProBiz-NAS:/#

    Just the error logs in /tmp. Let's have a looksie...
    ProBiz-NAS:/# cat /tmp/dropbox_error
    dropbox_error0ZtpEB.txt  dropbox_errorbfT1LT.txt  dropbox_erroreO5b9b.txt  dropbox_errorgHsNkD.txt  dropbox_errorOjhksz.txt  dropbox_errorUx8EMQ.txt  dropbox_errory6FEDe.txt  dropbox_errorZiccgP.txt
    dropbox_error3ou2t0.txt  dropbox_errord1Ahbi.txt  dropbox_errorF2NnFo.txt  dropbox_errorgLdapg.txt  dropbox_errorrznHye.txt  dropbox_errorV4Qhgm.txt  dropbox_erroryAZggK.txt  dropbox_errorzpsBBr.txt
    dropbox_error6lRXIV.txt  dropbox_errordjt9fv.txt  dropbox_errorfqLqPg.txt  dropbox_errorNqGvLP.txt  dropbox_errorUjvy_Q.txt  dropbox_errorxGn0Oe.txt  dropbox_errorzeN41M.txt  
    ProBiz-NAS:/# cat /tmp/dropbox_error0ZtpEB.txt 
    pid:	12875
    ppid:	12871
    uid:	1003
    user_info:	pwd.struct_passwd(pw_name='fortress', pw_passwd='x', pw_uid=1003, pw_gid=101, pw_gecos='', pw_dir='/c/home/fortress', pw_shell='/bin/false')
    effective_user_info:	pwd.struct_passwd(pw_name='fortress', pw_passwd='x', pw_uid=1003, pw_gid=101, pw_gecos='', pw_dir='/c/home/fortress', pw_shell='/bin/false')
    euid:	1003
    gid:	101
    egid:	101
    group_info:	grp.struct_group(gr_name='fortress', gr_passwd='x', gr_gid=101, gr_mem=[])
    effective_group_info:	grp.struct_group(gr_name='fortress', gr_passwd='x', gr_gid=101, gr_mem=[])
    appdata:	u'/c/home/fortress/.dropbox'
    real_path=u'/c/home/fortress/.dropbox'
    	not found
    parent	mode=040755	uid=1016	gid=103
    dropbox_path:	u'/c/home/fortress/Dropbox'
    real_path=u'/c/home/fortress/Dropbox'
    	not found
    parent	mode=040755	uid=1016	gid=103
    HOME:	/c/home/fortress
    tempdir:	'/tmp'
    real_path='/tmp'
    	mode=041777	uid=0	gid=0
    parent	mode=040755	uid=0	gid=0
    Traceback (most recent call last):
      File "dropbox/client/main.py", line 1239, in main_startup
      File "dropbox/client/main.py", line 721, in run
      File "dropbox/client/main.py", line 243, in startup_low
      File "dropbox/client/main.py", line 189, in safe_makedirs
      File "os.py", line 157, in makedirs
    OSError: [Errno 13] Permission denied: '/c/home/fortress/.dropbox'
    ProBiz-NAS:/# cat /tmp/dropbox_errorbfT1LT.txt 
    pid:	5217
    ppid:	5214
    uid:	98
    user_info:	pwd.struct_passwd(pw_name='admin', pw_passwd='x', pw_uid=98, pw_gid=98, pw_gecos='', pw_dir='/c/home/admin', pw_shell='/bin/false')
    effective_user_info:	pwd.struct_passwd(pw_name='admin', pw_passwd='x', pw_uid=98, pw_gid=98, pw_gecos='', pw_dir='/c/home/admin', pw_shell='/bin/false')
    euid:	98
    gid:	98
    egid:	98
    group_info:	grp.struct_group(gr_name='admin', gr_passwd='x', gr_gid=98, gr_mem=[])
    effective_group_info:	grp.struct_group(gr_name='admin', gr_passwd='x', gr_gid=98, gr_mem=[])
    appdata:	u'/c/.dropbox'
    real_path=u'/c/.dropbox'
    	mode=040700	uid=98	gid=98
    parent	mode=040777	uid=0	gid=0
    dropbox_path:	u'/c/Dropbox'
    real_path=u'/c/Dropbox'
    	not found
    parent	mode=040777	uid=0	gid=0
    HOME:	/c
    tempdir:	'/tmp'
    real_path='/tmp'
    	mode=041777	uid=0	gid=0
    parent	mode=040755	uid=0	gid=0
    Traceback (most recent call last):
      File "dropbox/client/main.py", line 1239, in main_startup
      File "dropbox/client/main.py", line 765, in run
      File "dropbox/client/main.py", line 712, in create_keystore_and_unlink_cookie
    Exception: statvfs failed with retval -1
    ProBiz-NAS:/#

    Well I'll be, there is now an Errno code on one of the DB error logs! However, that is for a specific user, not Global DB user. Still getting the same return value error on Global DB user. Let me delete those logs now... Done.
    ProBiz-NAS:/# rm /tmp/dropbox_error*
    ProBiz-NAS:/# ls -la /tmp/
    total 24
    drwxrwxrwt  5 root  root  4096 2013-07-08 00:14 .
    drwxr-xr-x 23 root  root  4096 2013-07-07 23:54 ..
    drwxrwxrwx  2 admin admin 4096 2013-07-07 23:41 addons
    -rw-r--r--  1 root  root    12 2013-07-04 22:11 .dhcp_server
    -rw-r--r--  1 root  root     0 2013-07-05 10:42 errors_001.log
    drwxrwxrwt  2 root  root  4096 2013-07-04 23:37 .ICE-unix
    srw-------  1 root  root     0 2013-07-07 23:43 pureftpd.sock
    drwxrwxrwt  2 root  root  4096 2013-07-04 23:37 .X11-unix
    ProBiz-NAS:/#


    WhoCares? wrote:
    Next check for space on the /tmp drive and if everything looks fine try another install of the add-on.

    Here you go... All looks normal to me, but maybe not?
    ProBiz-NAS:/# du -ch /tmp/
    4.0K	/tmp/.X11-unix
    4.0K	/tmp/.ICE-unix
    4.0K	/tmp/addons
    20K	/tmp/
    20K	total
    ProBiz-NAS:/# df -h /tmp/
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/md0              4.0G  399M  3.4G  11% /


    WhoCares? wrote:
    If that fails again, leave as is and check the dropbox_errorXXXX file again.

    Installing via Frontview now... Done. Here is the result:
    ProBiz-NAS:/# find -name *dropbox*
    ./usr/share/dropbox
    ./usr/share/dropbox/dropbox_up
    ./usr/share/dropbox/dropboxcheck
    ./usr/share/dropbox/run_dropbox.sh
    ./var/spool/frontview/shutdown/099_dropbox_shutdown
    ./c/.dropbox-dist
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-unsyncable.icon
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-syncing.png
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-app.svg
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-selsync.icon
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-uptodate.icon
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-uptodate.png
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-app.icon
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-selsync.png
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-syncing.icon
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-unsyncable.png
    ./c/.dropbox-dist/images/hicolor/16x16/status/dropboxstatus-blank.png
    ./c/.dropbox-dist/images/hicolor/16x16/status/dropboxstatus-x.png
    ./c/.dropbox-dist/images/hicolor/16x16/status/dropboxstatus-logo.png
    ./c/.dropbox-dist/images/hicolor/16x16/status/dropboxstatus-busy.png
    ./c/.dropbox-dist/images/hicolor/16x16/status/dropboxstatus-idle.png
    ./c/.dropbox-dist/images/hicolor/16x16/status/dropboxstatus-busy2.png
    ./c/.dropbox-dist/dropboxd
    ./c/.dropbox-dist/dropbox
    ./c/.dropbox-dist/run_dropbox.sh
    ./etc/cron.d/dropboxcheck
    ./etc/frontview/addons/ui/DROPBOX/dropbox_logo.gif
    ./etc/default/dropbox
    ./etc/init.d/dropbox
    ProBiz-NAS:/#

    Now, I will try to start the services via Frontview. First, Global Dropbox user... Done. Started with no issues. Now before I move forward, let me check if a error has been logged... Yes, it has:
    ProBiz-NAS:/# find -name *dropbox*
    ./tmp/dropbox.admin
    ./tmp/dropbox_errorXBeTSU.txt
    ./usr/share/dropbox
    ./usr/share/dropbox/dropbox_up
    ./usr/share/dropbox/dropboxcheck
    ./usr/share/dropbox/run_dropbox.sh
    ./var/spool/frontview/shutdown/099_dropbox_shutdown
    ./c/.dropbox-dist
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-unsyncable.icon
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-syncing.png
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-app.svg
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-selsync.icon
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-uptodate.icon
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-uptodate.png
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-app.icon
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-selsync.png
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-syncing.icon
    ./c/.dropbox-dist/images/emblems/emblem-dropbox-unsyncable.png
    ./c/.dropbox-dist/images/hicolor/16x16/status/dropboxstatus-blank.png
    ./c/.dropbox-dist/images/hicolor/16x16/status/dropboxstatus-x.png
    ./c/.dropbox-dist/images/hicolor/16x16/status/dropboxstatus-logo.png
    ./c/.dropbox-dist/images/hicolor/16x16/status/dropboxstatus-busy.png
    ./c/.dropbox-dist/images/hicolor/16x16/status/dropboxstatus-idle.png
    ./c/.dropbox-dist/images/hicolor/16x16/status/dropboxstatus-busy2.png
    ./c/.dropbox-dist/dropboxd
    ./c/.dropbox-dist/dropbox
    ./c/.dropbox-dist/run_dropbox.sh
    ./c/.dropbox
    ./etc/cron.d/dropboxcheck
    ./etc/frontview/addons/ui/DROPBOX/dropbox_logo.gif
    ./etc/default/dropbox
    ./etc/init.d/dropbox
    ProBiz-NAS:/#

    OK, will not move forward from here. Here are the contents of the error:
    ProBiz-NAS:/# cat /tmp/dropbox_errorXBeTSU.txt 
    pid:	19663
    ppid:	19661
    uid:	98
    user_info:	pwd.struct_passwd(pw_name='admin', pw_passwd='x', pw_uid=98, pw_gid=98, pw_gecos='', pw_dir='/c/home/admin', pw_shell='/bin/false')
    effective_user_info:	pwd.struct_passwd(pw_name='admin', pw_passwd='x', pw_uid=98, pw_gid=98, pw_gecos='', pw_dir='/c/home/admin', pw_shell='/bin/false')
    euid:	98
    gid:	98
    egid:	98
    group_info:	grp.struct_group(gr_name='admin', gr_passwd='x', gr_gid=98, gr_mem=[])
    effective_group_info:	grp.struct_group(gr_name='admin', gr_passwd='x', gr_gid=98, gr_mem=[])
    appdata:	u'/c/.dropbox'
    real_path=u'/c/.dropbox'
    	mode=040700	uid=98	gid=98
    parent	mode=040777	uid=0	gid=0
    dropbox_path:	u'/c/Dropbox'
    real_path=u'/c/Dropbox'
    	not found
    parent	mode=040777	uid=0	gid=0
    HOME:	/c
    tempdir:	'/tmp'
    real_path='/tmp'
    	mode=041777	uid=0	gid=0
    parent	mode=040755	uid=0	gid=0
    Traceback (most recent call last):
      File "dropbox/client/main.py", line 1239, in main_startup
      File "dropbox/client/main.py", line 765, in run
      File "dropbox/client/main.py", line 712, in create_keystore_and_unlink_cookie
    Exception: statvfs failed with retval -1
    ProBiz-NAS:/#

    Same error as I am always getting...

    WhoCares? wrote:
    If it still reports the same error, I'd be interested in an ls -al of "/c", "/tmp" and "/c/home".

    -Stefan

    Here you go, first ls -al of "/c":
    ProBiz-NAS:/# ls -al /c/
    total 72
    drwxrwxrwx 11 root     root      4096 2013-07-08 00:27 .
    drwxr-xr-x 23 root     root      4096 2013-07-07 23:54 ..
    -rw-------  1 root     root      8192 2013-07-08 00:27 aquota.group
    -rw-------  1 root     root      8192 2013-07-08 00:27 aquota.user
    drwxrwxrwt  7 nobody   nogroup   4096 2013-07-07 23:03 backup
    drwx------  3 admin    admin     4096 2013-07-08 00:27 .dropbox
    drwxr-xr-x  5 admin    admin     4096 2013-07-08 00:23 .dropbox-dist
    drwxrwsrwx 15 fortress fortress  4096 2013-07-07 23:03 fortressftp
    drwxr-xr-x  5 admin    admin     4096 2013-07-06 21:00 home
    drwx------  2 root     root     16384 2013-07-04 13:12 lost+found
    drwxrwxrwx  2 nobody   nogroup   4096 2013-07-07 23:27 media
    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
    ProBiz-NAS:/#


    Now, ls -al of "/tmp"
    ProBiz-NAS:/# ls -al /tmp/
    total 28
    drwxrwxrwt  5 root  root  4096 2013-07-08 00:27 .
    drwxr-xr-x 23 root  root  4096 2013-07-07 23:54 ..
    drwxrwxrwx  2 admin admin 4096 2013-07-08 00:23 addons
    -rw-r--r--  1 root  root    12 2013-07-04 22:11 .dhcp_server
    -rw-r--r--  1 admin admin    0 2013-07-08 00:27 dropbox.admin
    -rw-------  1 admin admin 1094 2013-07-08 00:27 dropbox_errorXBeTSU.txt
    -rw-r--r--  1 root  root     0 2013-07-05 10:42 errors_001.log
    drwxrwxrwt  2 root  root  4096 2013-07-04 23:37 .ICE-unix
    srw-------  1 root  root     0 2013-07-07 23:43 pureftpd.sock
    drwxrwxrwt  2 root  root  4096 2013-07-04 23:37 .X11-unix
    ProBiz-NAS:/#


    Finally, ls -al of "/c/home":
    ProBiz-NAS:/# ls -al /c/home/
    total 20
    drwxr-xr-x  5 admin admin    4096 2013-07-06 21:00 .
    drwxrwxrwx 11 root  root     4096 2013-07-08 00:27 ..
    drwx------  2 admin admin    4096 2013-07-05 00:08 admin
    drwxr-xr-x  2  1016      103 4096 2013-07-06 21:00 fortress
    drwxr-xr-x  2   100 fortress 4096 2013-07-05 00:15 git
    ProBiz-NAS:/#


    By the way, one thing I am noticing is that in the Add-Ons tab, under "Available Add-Ons" I am getting an error I have never seen before: "The available add-ons cannot be displayed as there is no internet connectivity.". Doing some checking, I found a couple of interesting topics on this:
    viewtopic.php?f=36&t=53686
    viewtopic.php?f=7&t=60845

    Did, all the troubleshooting and my DNS and internet connections on my other ReadyNas Pro was all good! This might be a red-hearing, but still worth a thought...

    I hope this all helps and thanks Stefan for your help in this matter!
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired
    Jul 08, 2013
    Try downloading something from ReadyNAS.com using wget via SSH. Does that work?
  • WhoCares_'s avatar
    WhoCares_
    Mentor
    Jul 08, 2013
    I'm a bit confused about the actual meaning of the error message Dropbox is logging. Together with the problem when displaying available add-ons I'm led to believe that instead of a file system problem we're dealing with a network connectivity problem here. So as mdgm suggested it would be helpful if you could run some connectivity tests from the SSH command line on the ReadyNAS like

    traceroute www.readynas.com
    ping whocares.de


    and similar commands with other targets.

    -Stefan
  • fifer55's avatar
    fifer55
    Apprentice
    Jul 08, 2013
    mdgm wrote:
    Try downloading something from ReadyNAS.com using wget via SSH. Does that work?


    WhoCares? wrote:
    I'm a bit confused about the actual meaning of the error message Dropbox is logging. Together with the problem when displaying available add-ons I'm led to believe that instead of a file system problem we're dealing with a network connectivity problem here. So as mdgm suggested it would be helpful if you could run some connectivity tests from the SSH command line on the ReadyNAS like

    traceroute www.readynas.com
    ping whocares.de


    and similar commands with other targets.

    -Stefan


    Yes guys, all that stuff works. Here are examples:

    Pinging different destinations:
    root@192.168.1.9's password: 
    Last login: Mon Jul  8 07:29:54 2013 from 192.168.1.8
    Last login: Mon Jul  8 09:16:23 2013 from 192.168.1.8 on pts/0
    Linux ProBiz-NAS 2.6.37.6.RNx86_64.2.4 #1 SMP Thu Jul 26 05:00:36 PDT 2012 x86_64 GNU/Linux
    ProBiz-NAS:~# cd /c/backup/
    ProBiz-NAS:/c/backup# ping www.google.com
    PING www.google.com (74.125.239.48) 56(84) bytes of data.
    64 bytes from nuq04s19-in-f16.1e100.net (74.125.239.48): icmp_seq=1 ttl=53 time=36.9 ms
    64 bytes from nuq04s19-in-f16.1e100.net (74.125.239.48): icmp_seq=2 ttl=53 time=32.0 ms
    64 bytes from nuq04s19-in-f16.1e100.net (74.125.239.48): icmp_seq=3 ttl=53 time=22.2 ms
    ^C
    --- www.google.com ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2000ms
    rtt min/avg/max/mdev = 22.269/30.406/36.937/6.094 ms
    ProBiz-NAS:/c/backup# ping whocares.de                                                                                          
    PING whocares.de (81.169.185.227) 56(84) bytes of data.
    64 bytes from h8399.serverkompetenz.net (81.169.185.227): icmp_seq=1 ttl=46 time=190 ms
    64 bytes from h8399.serverkompetenz.net (81.169.185.227): icmp_seq=2 ttl=46 time=189 ms
    ^C
    --- whocares.de ping statistics ---
    3 packets transmitted, 2 received, 33% packet loss, time 2001ms
    rtt min/avg/max/mdev = 189.030/189.622/190.214/0.592 ms
    ProBiz-NAS:/c/backup# ping www.cnn.com
    PING cnn-lax-tmp.gslb.vgtf.net (157.166.240.11) 56(84) bytes of data.
    ^C
    --- cnn-lax-tmp.gslb.vgtf.net ping statistics ---
    5 packets transmitted, 0 received, 100% packet loss, time 3999ms

    ProBiz-NAS:/c/backup# ping www.cnn.com
    PING cnn-lax-tmp.gslb.vgtf.net (157.166.240.11) 56(84) bytes of data.
    ^C
    --- cnn-lax-tmp.gslb.vgtf.net ping statistics ---
    11 packets transmitted, 0 received, 100% packet loss, time 9999ms

    ProBiz-NAS:/c/backup# ping www.yahoo.com                                                                                                                           
    PING ds-any-fp3-real.wa1.b.yahoo.com (206.190.36.45) 56(84) bytes of data.
    64 bytes from ir1.fp.vip.gq1.yahoo.com (206.190.36.45): icmp_seq=1 ttl=48 time=50.9 ms
    64 bytes from ir1.fp.vip.gq1.yahoo.com (206.190.36.45): icmp_seq=2 ttl=48 time=58.1 ms
    64 bytes from ir1.fp.vip.gq1.yahoo.com (206.190.36.45): icmp_seq=3 ttl=48 time=45.4 ms
    ^C
    --- ds-any-fp3-real.wa1.b.yahoo.com ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2003ms
    rtt min/avg/max/mdev = 45.437/51.533/58.175/5.221 ms
    ProBiz-NAS:/c/backup#


    Here is a download using wget:
    ProBiz-NAS:/c/backup# wget --no-check-certificate -O - "https://www.dropbox.com/download?plat=lnx.x86" | tar xzf -    
    --2013-07-08 09:22:55--  https://www.dropbox.com/download?plat=lnx.x86
    Resolving www.dropbox.com... 199.47.216.170
    Connecting to www.dropbox.com|199.47.216.170|:443... connected.
    WARNING: cannot verify www.dropbox.com's certificate, issued by `/C=US/O=Thawte, Inc./CN=Thawte SSL CA':
      Unable to locally verify the issuer's authority.
    HTTP request sent, awaiting response... 302 FOUND
    Location: https://dl-web.dropbox.com/u/17/dropbox-lnx.x86-2.2.8.tar.gz [following]
    --2013-07-08 09:22:56--  https://dl-web.dropbox.com/u/17/dropbox-lnx.x86-2.2.8.tar.gz
    Resolving dl-web.dropbox.com... 23.21.230.11
    Connecting to dl-web.dropbox.com|23.21.230.11|:443... connected.
    WARNING: cannot verify dl-web.dropbox.com's certificate, issued by `/C=US/O=Thawte, Inc./CN=Thawte SSL CA':
      Unable to locally verify the issuer's authority.
    HTTP request sent, awaiting response... 302 FOUND
    Location: https://dl.dropboxusercontent.com/u/17/dropbox-lnx.x86-2.2.8.tar.gz [following]
    --2013-07-08 09:22:56--  https://dl.dropboxusercontent.com/u/17/dropbox-lnx.x86-2.2.8.tar.gz
    Resolving dl.dropboxusercontent.com... 23.21.213.190
    Connecting to dl.dropboxusercontent.com|23.21.213.190|:443... connected.
    WARNING: cannot verify dl.dropboxusercontent.com's certificate, issued by `/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert High Assurance CA-3':
      Unable to locally verify the issuer's authority.
    HTTP request sent, awaiting response... 200 OK
    Length: 20772183 (20M) [application/x-tar]
    Saving to: `STDOUT'

    100%[==========================================================================================================================>] 20,772,183  3.66M/s   in 6.9s    

    2013-07-08 09:23:05 (2.87 MB/s) - `-' saved [20772183/20772183]

    ProBiz-NAS:/c/backup#


    Haven't changed anything else or modified anything since yesterday.

    Again, thanks guys for your help!!
  • fifer55's avatar
    fifer55
    Apprentice
    Sep 11, 2013
    What I am going to attempt to do now is wiping the drives and then trying to install the dropbox as the first add-on.

    We will see how it goes.
  • fifer55's avatar
    fifer55
    Apprentice
    Sep 17, 2013
    Did a complete factory install and compared 1:1 with my other NAS and still cannot get the Available Add-Ons page to display anything, even though I can send alerts to my email address.

    I have not installed any add-on and this was the first thing I noticed. My router and switch are correct.

    I am just baffled that even after a complete factory reset, I cannot get the Available Add-Ons page to display, but I can with the other NAS? Maybe it has something to do with enabling the Dual NIC Bond?

    Any insight would be greatly appreciated.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More