I installed the container using all the default settings and got to the point where it gave me the link to connect my Dropbox which I did and then that is where the log ends -- I get a confirmation This computer is connected to Dropbox Welcome Carlos but that is it.

No files have synced and there is nothing in the log showing any activity.

CPU and Memory use for the docker show 0s

 

There is no error log in the location specified early in this thread. 

It has been almost 40 minutes -- I have a small Dropbox relative to what I see people posting here (around 4GB).

When I check Dropbox through a browser it shows the unRaid server as a connected device with activity in the last hour.

What have I done wrong or what could possibly cause this?

Edited December 8, 20241 yr by Naldinho

Edit: I (sort of) resolved the crash after a few hours issue by following one of the directions in this post earlier in the thread:

Quote

Finally, in advance view toggle near top, add '--restart unless-stopped' in extra parameter line, because this container will sh*t the bed from time to time

I assume it crashes now, but then it just restarts. That works well enough.

 

Original post: 

I've been using this docker container for over a year with no issues until about two weeks ago. Now the container exits after a few hours. I've tried deleting the appdata dropbox folder and starting it from scratch. The only information I enter is the path on my storage share to sync with dropbox, but the same problem keeps occuring. It does activate properly, and it does work properly for a few hours (i.e. it syncs file properly).

When I check the log, there is an error that starts with: "RUST PANICKING -- "queue size is inconsistent"" but I'm not sure where to go from there.

 

Anyone else experience this or have ideas on how to investigate the issue?

 

Edited February 1, 20251 yr by ramk13
found solution and removed poor text entry

On 12/8/2024 at 6:52 PM, Naldinho said:

I installed the container using all the default settings and got to the point where it gave me the link to connect my Dropbox which I did and then that is where the log ends -- I get a confirmation This computer is connected to Dropbox Welcome Carlos but that is it.

No files have synced and there is nothing in the log showing any activity.

CPU and Memory use for the docker show 0s

 

There is no error log in the location specified early in this thread. 

It has been almost 40 minutes -- I have a small Dropbox relative to what I see people posting here (around 4GB).

When I check Dropbox through a browser it shows the unRaid server as a connected device with activity in the last hour.

What have I done wrong or what could possibly cause this?

I have the excactly same effect. I just started with Unraid and this is the first thing i wanted to setup. The container even crashed one time and afterwards it got a new ID to link. But so far no files are synced at all. I need this to replace my Synology...

OK this does the trick:

Quote

1. `docker run --name dropbox --rm -e DROPBOX_UID=<your UID> -e DROPBOX_GID=<your GID> -v "/volume1/homes/lukas/dropbox_test/settings:/opt/dropbox/.dropbox" otherguy/dropbox` 

2. After authenticating the client make sure that the `settings` folder contains `info.json` and `unlink.db` (if not, the whole process did not work) 

3. stop your container and restart it with `docker run --name dropbox --rm -e DROPBOX_UID=<your UID> -e DROPBOX_GID=<your GID> -v "/volume1/dropbox/client_settings:/opt/dropbox/.dropbox" -v "/volume1/dropbox/data:/opt/dropbox/Dropbox" otherguy/dropbox`

 

It's also mentioned in the docs of the container:

Quote

/opt/dropbox/Dropbox The actual Dropbox folder, containing all your synced files. Note that you may need to omit this on the first run so that Dropbox can have control to create it. Once it is created in the other volume, you can recreate the container with this volume as well.

 

Additional it is important to set network to host to allow LAN-sync.

 

As bonus i added

Quote

sysctl -w fs.inotify.max_user_watches=100000

 

To the go-file to allow monitoring of all folders.

Edited March 8, 20251 yr by Tscherno

On 8/5/2023 at 9:25 AM, Botafoguense1965 said:

Oh, I used Rclone Browser, an app you find in Unraid, command line is still too much for me…it’s easy to use.

Are you referring to the app called...

 

Nacho-Rclone-Native-GUI?

 

If not what's the name of the App?

I have setup otherguy/dropbox on unRaid 7 using the CA setup.  It ran this:

 

docker run
  -d
  --name='Dropbox-by-otherguy'
  --net='bridge'
  --pids-limit 2048
  -e TZ="America/New_York"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="nas"
  -e HOST_CONTAINERNAME="Dropbox-by-otherguy"
  -e 'DROPBOX_UID'='1000'
  -e 'DROPBOX_GID'='100'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/mgutt/unraid-docker-templates/main/mgutt/images/dropbox.png'
  -v '/home/gaa/Dropbox/':'/opt/dropbox/Dropbox':'rw'
  -v '/home/gaa/.dropbox':'/opt/dropbox/.dropbox':'rw' 'otherguy/dropbox'

 

I looked at the logs, copied the ;link and registered this with Dropbox:

Please visit https://www.dropbox.com/cli_link_nonce?nonce=XXXXXXXXXXXX to link this device.
This computer is now linked to Dropbox. Welcome Gary

 

I checked the status:

root@nas:~# docker exec -it Dropbox-by-otherguy gosu dropbox dropbox status
Starting...

 

And later I see:

root@nas:~# docker exec -it Dropbox-by-otherguy gosu dropbox dropbox status
Dropbox isn't responding!

 

It looks like it does not really start.   Any ideas?

 

BTW, those mounted locations are ZFS (there is no non-ZFS storage here):

root@nas:~# docker exec -it Dropbox-by-otherguy  mount | grep /opt/dropbox
heart on /opt/dropbox type zfs (rw,relatime,xattr,noacl,casesensitive)
placid/home/gaa on /opt/dropbox/Dropbox type zfs (rw,relatime,xattr,noacl,casesensitive)
placid/home/gaa on /opt/dropbox/.dropbox type zfs (rw,relatime,xattr,noacl,casesensitive)

 

Viewed from the host these are on /home/gaa:

root@nas:~# zfs list placid/home/gaa
NAME              USED  AVAIL  REFER  MOUNTPOINT
placid/home/gaa  7.59M  8.51T  7.59M  /home/gaa
root@nas:~# ls -lnd /home/gaa/{.dropbox,Dropbox}
drwxrwxrwx 9 1000 100 16 May  1 19:36 /home/gaa/.dropbox/
drwxr-xr-x 2 1000 100  2 May  1 11:07 /home/gaa/Dropbox/

 

The /opt/dropbox/.dropbox directory has the code, etc and /opt/dropbox/Dropbox is empty.   They both belong to the correct UID:GID = 1000:100.

 

I can't see anything else in the logs.

I can see the dropbox executable is running but there is no strace on unRAID so I don't know what it is doing.

 

Could they have re-disabled ZFS?   

Any way I can troubleshoot this?

Any suggestions?

 

I have an update...

 

I tried this container on my Fedora 42 laptop where I can strace.   No better results.

1.  Once it settles down, it shows endless FUTEX calls and nothing else.

2. I was able to see a lot of messages about library loads as it started up and among those was:

    <frozen zipimport>:259: UserWarning: google.protobuf.service module is deprecated. RPC implementations should provide code generator plugins which generate code specific to the RPC implementation. service.py will be removed in Jan 2025

It is after January 2025.   I don't know if this matters.

 

Note that on my laptop I can run the same dropbox code on the host OS as a --user level systemd service.   I can't do that on unRAID because it has no real users or systemd.

+1 to the March 8 post from Tscherno

I installed dropbx-by-theotherguy on a fresh unraid install. like others, once I linked the account I had no further log messages. i tried a bunch of different stuff - consoling in, changing permissions, etc... but what Tscherno listed did the trick: on first install remove the volume linking the container's /opt/drobox/Dropbox to your file system, start the container and link to your account, then edit it to add back in the volume mapping and restart... worked great. The tip to switch the type of host enabled lan sync. Thanks.