Right, I guess I wasn't clear, but you need to to use a specific disk for the Dropbox share since you don't have a cache drive.

Since you already have a Dropbox user share, it probably is on disk1, and you can confirm from the Web UI Shares Tab, Click on Compute for the Dropbox share and it will return where the share is currently saved to.

Edit the docker to change /mnt/user/Dropbox to whichever disk is used for it ie /mnt/disk1/Dropbox for disk1

Some caveats with this configuration. If you create/edit files over Samba to the Dropbox share, there is the possibility that files might end up on the other disks and would then be not seen by the Dropbox container. You should edit the Dropbox share to limit it to only one disk.

 

15 minutes ago, ken-ji said:

Right, I guess I wasn't clear, but you need to to use a specific disk for the Dropbox share since you don't have a cache drive.

Since you already have a Dropbox user share, it probably is on disk1, and you can confirm from the Web UI Shares Tab, Click on Compute for the Dropbox share and it will return where the share is currently saved to.

Edit the docker to change /mnt/user/Dropbox to whichever disk is used for it ie /mnt/disk1/Dropbox for disk1

Some caveats with this configuration. If you create/edit files over Samba to the Dropbox share, there is the possibility that files might end up on the other disks and would then be not seen by the Dropbox container. You should edit the Dropbox share to limit it to only one disk.

 

Thanks for your patience. Very helpful and seems to have actually worked I'm sure it was working before when not constrained to a single disk but hey ho.

 

Appreciate it a lot as now I don't need to run a slow VM.

Hey Ken-ji,

 

I have reconfigured my server to have an XFS standalone drive for Dropbox to use, so I have reinstalled the docker.  But I have had some issues, and I am hoping that you'd be able to help.

 

I installed Dropbox and it did not appear to sync.  I went into the Console and ran "dropbox.py status".  This said that Dropbox wasn't running.  So I tried "dropbox.py start" which said the daemon wasn't running.  So i tried "dropbox.py update" and then "dropbox.py start -i" and it seemed to come up.  

I left the server and when I came back, the Docker drive was full.  Apparently, what ever I did installed the dropbox connection point on the docker.img.  Yikes.   I uninstalled it, wiped all the data and reinstalled the docker.  And here I am.

 

My new log file look like this and I am back to Dropbox isn't running:

Quote

dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-DGRnO6
dropbox: initializing
dropbox: initializing python 3.7.5
dropbox: setting program path '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-96.4.172/dropbox'
dropbox: setting python path '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-96.4.172:/dropbox/.dropbox-dist/dropbox-lnx.x86_64-96.4.172/python-packages.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-96.4.172/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-96.4.172/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-96.4.172/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-96.4.172/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-96.4.172/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-96.4.172/apex._apex.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-96.4.172/tornado.speedups.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-96.4.172/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-96.4.172/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-96.4.172/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so'

 

Any ideas where to start?

 

Thank you.

 

- Wolfman

 

 

You tried to start the dropbox service as the root user.

This made your dropbox sync to /root/Dropbox (inside the container) which is in docker.img

because of some limitations, the container drops you into a root shell, not the user running the dropbox service.

so you actually need to run

su - nobody

before interacting with the dropbox service inside the container.

From within my container:

sh-4.3# su - nobody -c 'dropbox.py status'
Up to date

I have to say you are the first to encounter a bunch of issues... Most of the people using this container have been able to configure without much difficulty, barring the crap Dropbox created with the filesystem limits and the recent dropbox builds now needing graphical libraries to run headless.

 

If your docker logs says just that then there should be nothing wrong. Mine is like this. The killed line at the end indicates dropbox service restarting it self. You can run the status command above or the ls command 'dropbox.py ls /dropbox/Dropbox' to check the sync status.

dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-bUcbWA
dropbox: initializing
dropbox: initializing python 3.7.5
dropbox: setting program path '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/dropbox'
dropbox: setting python path '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460:/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/python-packages.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/apex._apex.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/tornado.speedups.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/wrapt._wrappers.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.460/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so'
dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-crogcX
dropbox: initializing
dropbox: initializing python 3.7.5
dropbox: setting program path '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/dropbox'
dropbox: setting python path '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465:/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/python-packages.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/apex._apex.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/tornado.speedups.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/wrapt._wrappers.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/tmp/.dropbox-dist-new-86fd6rhb/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so'
dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-y31su9
dropbox: initializing
dropbox: initializing python 3.7.5
dropbox: setting program path '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/dropbox'
dropbox: setting python path '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465:/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/python-packages.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/apex._apex.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/tornado.speedups.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/wrapt._wrappers.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-97.3.465/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so'
dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-iKKsTy
dropbox: initializing
dropbox: initializing python 3.7.5
dropbox: setting program path '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/dropbox'
dropbox: setting python path '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150:/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/python-packages.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/apex._apex.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/tornado.speedups.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/wrapt._wrappers.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/tmp/.dropbox-dist-new-ejm8ndtg/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so'
dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-TyX1Rm
dropbox: initializing
dropbox: initializing python 3.7.5
dropbox: setting program path '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/dropbox'
dropbox: setting python path '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150:/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/python-packages.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/apex._apex.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/tornado.speedups.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/wrapt._wrappers.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-98.3.150/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so'
/usr/local/bin/dockerinit.sh: line 19: 19 Killed su -l ${DROPBOX_USER} -c "/dropbox/.dropbox-dist/dropboxd"

 

No errors I can see in the log but no changes to my Dropbox folder are syncing to the cloud.

I have no idea what could be wrong here... are you still at 3 or less devices signed in vs the Free tier of the Dropbox account (you can check on the web site under security)? or are you paying for it monthly?

You might need to go in via a shell and run the dropbox.py command to inspect your files.

19 minutes ago, ken-ji said:

I have no idea what could be wrong here... are you still at 3 or less devices signed in vs the Free tier of the Dropbox account (you can check on the web site under security)? or are you paying for it monthly?

You might need to go in via a shell and run the dropbox.py command to inspect your files.

Seems it's not running? Why would that be? Def only three devices.

 

sh-4.3# dropbox.py status
Dropbox isn't running!
sh-4.3# dropbox.py start
Starting Dropbox...
The Dropbox daemon is not installed!
Run "dropbox start -i" to install the daemon

edit, it's now asking me to relink even though it seems to have been "active" in the last hour:

 

Edited June 30, 20206 yr by cinereus

The dropbox process is running as the nobody user.

So when you go in, you'll need to switch to the nobody user:

sh-4.3# su - nobody
nobody@dropbox:~$ cd  Dropbox
nobody@dropbox:~/Dropbox$ dropbox.py filestatus
.dropbox:                                                                     unwatched
.dropbox.cache:                                                               unwatched
2019-03-07 13.57.05.pdf:                                                      up to date
3D Stuff:                                                                     up to date
nobody@dropbox:~/Dropbox$

 

1 hour ago, ken-ji said:

The dropbox process is running as the nobody user.

So when you go in, you'll need to switch to the nobody user:

sh-4.3# su - nobody
nobody@dropbox:~$ cd  Dropbox
nobody@dropbox:~/Dropbox$ dropbox.py filestatus
.dropbox:                                                                     unwatched
.dropbox.cache:                                                               unwatched
2019-03-07 13.57.05.pdf:                                                      up to date
3D Stuff:                                                                     up to date
nobody@dropbox:~/Dropbox$

 

su - nobody doesn't seem to work

 

sh-4.3# su - nobody
sh-4.3# whoami
root

and while dropbox.py works it still thinks it's unlinked

sh-4.3# dropbox.py
Dropbox command-line interface

commands:

Note: use dropbox help <command> to view usage for a specific command.

 status       get current status of the dropboxd
 throttle     set bandwidth limits for Dropbox
 help         provide help
 puburl       get public url of a file in your dropbox's public folder
 stop         stop dropboxd
 update       download latest version of dropbox
 running      return whether dropbox is running
 start        start dropboxd
 filestatus   get current sync status of one or more files
 proxy        set proxy settings for Dropbox
 autostart    automatically start dropbox at login
 exclude      ignores/excludes a directory from syncing
 lansync      enables or disables LAN sync
 sharelink    get a shared link for a file in your dropbox
 ls           list directory contents with current sync status

sh-4.3# dropbox.py status    
Starting...
To link this computer to a dropbox account, visit the following url:
https://www.dropbox.com/cli_link_nonce?nonce=db1975361235bad5644aa4186c225ec3

The files in the Dropbox folder are owned by my user account not nobody. But if I use the user account I can't start it either.

sh-4.3# su - cinereus
cinereus@6ee6f0503f8b:~$ dropbox.py filestatus
Dropbox isn't running!
cinereus@6ee6f0503f8b:~$ dropbox.py status
Dropbox isn't running!
cinereus@6ee6f0503f8b:~$ dropbox.py start
Dropbox isn't running!
Dropbox is already running!
cinereus@6ee6f0503f8b:~$ dropbox.py filestatus
Dropbox isn't running!
cinereus@6ee6f0503f8b:~$ dropbox.py start
Dropbox isn't running!
Dropbox is already running!

 

 

I think you've misconfigured the container somehow... can you should me the docker configuration again?

1 hour ago, ken-ji said:

I think you've misconfigured the container somehow... can you should me the docker configuration again?

It has been working without issue for weeks and I haven't even rebooted the server.

 

Can you restart the Dropbox container and attach the log? Probably starting from the last dropbox: initializing line

5 hours ago, ken-ji said:

Can you restart the Dropbox container and attach the log? Probably starting from the last dropbox: initializing line

usermod: no changes
dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-4dqNxc
dropbox: initializing
dropbox: initializing python 3.7.5
dropbox: setting program path '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-101.3.424/dropbox'
dropbox: setting python path '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-101.3.424:/dropbox/.dropbox-dist/dropbox-lnx.x86_64-101.3.424/python-packages.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-4dqNxc
dropbox: initializing
dropbox: initializing python 3.7.5
dropbox: setting program path '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-101.3.424/dropbox'
dropbox: setting python path '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-101.3.424:/dropbox/.dropbox-dist/dropbox-lnx.x86_64-101.3.424/python-packages.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-101.3.424/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-101.3.424/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-101.3.424/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-101.3.424/apex._apex.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-101.3.424/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-101.3.424/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-101.3.424/tornado.speedups.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-101.3.424/wrapt._wrappers.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-101.3.424/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-101.3.424/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/dropbox/.dropbox-dist/dropbox-lnx.x86_64-101.3.424/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so'

 

hmm. really odd.

If you now open a shell in the container and su to your user, does dropbox.py status say its running?

If it is, then there should be no problem (and I'm out of clues or ideas)

If it isn't, I'm actually stumped as to why the dropboxd binary is stopping for you.

 

9 hours ago, ken-ji said:

hmm. really odd.

If you now open a shell in the container and su to your user, does dropbox.py status say its running?

If it is, then there should be no problem (and I'm out of clues or ideas)

If it isn't, I'm actually stumped as to why the dropboxd binary is stopping for you.

 

Okay. I haven't changed anything but weirdly now it says it is running:

 

$ dropbox.py status
Syncing 3,215 files
Uploading 3,190 files...
Downloading 25 files...

 

But that can't be right because it will have been running for 24 hours now and still not synced (at max it wasn't working for a week or so and I have about 100 MB of changes in that time).

I can only guess, but the dropboxd process probably crashed or something without showing anything in the logs.

Well restarting the container would restart the process, but as for the runningand syncing for 24h, I have no idea what happened there...

19 minutes ago, ken-ji said:

I can only guess, but the dropboxd process probably crashed or something without showing anything in the logs.

Well restarting the container would restart the process, but as for the runningand syncing for 24h, I have no idea what happened there...

The thing is I'd already restarted the container a bunch of times. If it's not in the logs is there a way to see how long the daemon has been running? 

 

The only thing I can think of is since I last posted I also rebooted the whole machine so could it be that's whst fixed it? I'll have to check in again about this frozen sync though. 

I've just checked again and the sync is stuck at exactly the same place. Desktop client is synced fine even when I add a few large files it runs at full speed. 

Sorry. I give up.

You are the first to have this error, and I have no obvious clues or ideas as to why the client is stalling.

Maybe Dropbox can provide support, but the headless client seems to have the absolute minimum of support (at least for free users)

Hoping someone can help with my problem below. Apologies in advance, I've no experience with python and not a lot more using docker but I am learning slowly so excuse my ignorance if I have done something stupid.

These are the steps I followed to end up where i am;

- Install the docker to Unraid

- Open the console from the the Dropbox docker menu

- run dropbox.py start -i [If I try to run it without the -i it tells me to use the -i] this installs something.

- obtained the url to link my account

- type Dropbox.py start for the first time and I get this;

sh-4.3# dropbox.py status
Dropbox isn't running!
sh-4.3# dropbox.py start 
Starting Dropbox...dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-x5v0tL
dropbox: initializing
dropbox: initializing python 3.7.5
dropbox: setting program path '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/dropbox'
dropbox: setting python path '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431:/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/python-packages.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/apex._apex.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/tornado.speedups.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/wrapt._wrappers.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/root/.dropbox-dist/dropbox-lnx.x86_64-102.4.431/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so'
Dropbox isn't running!
Done!
sh-4.3# dropbox.py status
Syncing 75,611 files
Uploading 1 file...
Downloading 75,610 files...

 

So it appears from that last part that Dropbox has started downloading my files to the server however I can't find them. I used the default options when I installed the docker as per the attached image. The only thing I do know is that my docker image is filling up so I think for some reason the files are being stored in the docker rather than the share on disk1.

Unraid version 6.8.3

Any help would be greatly appreciated.

You've done something really wrong.

Please refer to the first page for some details, but in a nutshell, you used the container to run a copy of dropbox client as the container root user, which now places the files inside the container image.

 

Start over (delete the container, and re add it)

When the container has started up, view the logs of the container (which will show you the link url)

Link your account, and wait a bit as it will now populate the directory for the Data files.

 

If you ever access the shell to check anything, you'll need to run

su - nobody

before doing anything else, as the dropbox client is running as nobody user instead of the default root.

Thanks Ken-ji, Works now. Apologies for the Noob mistakes.

Hi there!

So happy to get the Docker container working but I just realised the sync is not ptogressing for me either. Looks a bit like I have the same problem as @cinereus 

 

I got the dropbox folder structure on the array and some files are there. But realised that not all files are synced. I left it for around 2 night but the sync status has not changed yet.

The console says its running and syncing but nothing is happening.

If I create new folders they do get synced with some files in it. For example .txt files are getting synced. Most image files as well. 

One problem are After Effect files (.aep) and Photoshop files (.psd)

 

So the sync seems to work but not for all files.

Any help would be appriciated!

Have you linked your dropbox account to the docker container? Does your dropbox container log give you any information?

3 minutes ago, Energen said:

Have you linked your dropbox account to the docker container? Does your dropbox container log give you any information?

Yes, the container is linked and sows some of the files that are present on my Dropbox I am running in my VM.

On a side note I am using the VM Dropbox with smart sync. Tested if it makes a difference if files are synced or just online but unfortunately that does not seem to be a problem.

 

The log does not throw any errors or warnings at all.