Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Solved
headless ubuntu not syncing
Hi All,
I sucessfully installed dropbox on a headless ubuntu server using the following guide:
https://www.linuxbabe.com/ubuntu/install-dropbox-headless-ubuntu-server
The dropbox file/folde...
The headless ubuntu Dropbox sync is syncing now without any manual intervention).
1) Use this link to install dropbox on ubuntu: https://www.dropbox.com/install-linux
2) Use this link to setup dropbox systemd service unit: https://www.linuxbabe.com/ubuntu/install-dropbox-headless-ubuntu-server
Modify the dropbox.service file to call dropboxd using the install location in step 1 (not location in step 2 guide)
What was not clear to me before is the dropbox systemd daemon is running in superuser mode under the "username" account. To access/control the dropbox daemon from command line, sudo -u username dropbox <options> must be done.
That sums it up. Thanks to the knowledgble members who posted in the thread.
jainraje wrote:I believe yes to your question.
...
Hm... 🤔... What's the meaning of 'believe' above? What's it actually?! That's the matter! What's getting back following:
ps axo user,comm | grep dropbox
Nothing comes back:
$ ps axo user,comm | grep dropbox
A few additional data points:
1) After a fresh reboot the dropbox systemd service unit fails during start-up:
$sudo journalctl -u dropbox.service
systemd[1]: Started Dropbox Daemon.
dropboxd[29288]: dropbox: load fq extension '/opt/dropbox/dropbox-lnx.x86_64-163.4.5456/cryptography.hazmat.bindings._openssl.cpython-38-x86_64-linux-gnu.so'
dropboxd[29288]: dropbox: load fq extension '/opt/dropbox/dropbox-lnx.x86_64-163.4.5456/cryptography.hazmat.bindings._padding.cpython-38-x86_64-linux-gnu.so'
dropboxd[29288]: dropbox: load fq extension '/opt/dropbox/dropbox-lnx.x86_64-163.4.5456/apex._apex.cpython-38-x86_64-linux-gnu.so'
dropboxd[29288]: dropbox: load fq extension '/opt/dropbox/dropbox-lnx.x86_64-163.4.5456/psutil._psutil_linux.cpython-38-x86_64-linux-gnu.so'
dropboxd[29288]: dropbox: load fq extension '/opt/dropbox/dropbox-lnx.x86_64-163.4.5456/psutil._psutil_posix.cpython-38-x86_64-linux-gnu.so'
dropboxd[29288]: dropbox: load fq extension '/opt/dropbox/dropbox-lnx.x86_64-163.4.5456/tornado.speedups.cpython-38-x86_64-linux-gnu.so'
dropboxd[29288]: dropbox: load fq extension '/opt/dropbox/dropbox-lnx.x86_64-163.4.5456/wrapt._wrappers.cpython-38-x86_64-linux-gnu.so'
dropboxd[29288]: dropbox: load fq extension '/home/user/.dropbox-dist/dropbox-lnx.x86_64-164.4.7914/cryptography.hazmat.bindings._padding.cpython-38-x86_64-linux-gnu.so'
dropboxd[29288]: dropbox: load fq extension '/home/user/.dropbox-dist/dropbox-lnx.x86_64-164.4.7914/apex._apex.cpython-38-x86_64-linux-gnu.so'
dropboxd[29288]: dropbox: load fq extension '/home/user/.dropbox-dist/dropbox-lnx.x86_64-164.4.7914/psutil._psutil_linux.cpython-38-x86_64-linux-gnu.so'
dropboxd[29288]: dropbox: load fq extension '/home/user/.dropbox-dist/dropbox-lnx.x86_64-164.4.7914/psutil._psutil_posix.cpython-38-x86_64-linux-gnu.so'
dropboxd[29288]: dropbox: load fq extension '/home/user/.dropbox-dist/dropbox-lnx.x86_64-164.4.7914/cryptography.hazmat.bindings._openssl.cpython-38-x86_64-linux-gnu.so'
dropboxd[29288]: dropbox: load fq extension '/home/user/.dropbox-dist/dropbox-lnx.x86_64-164.4.7914/tornado.speedups.cpython-38-x86_64-linux-gnu.so'
dropboxd[29288]: dropbox: load fq extension '/home/user/.dropbox-dist/dropbox-lnx.x86_64-164.4.7914/wrapt._wrappers.cpython-38-x86_64-linux-gnu.so'
systemd[1]: dropbox.service: Main process exited, code=killed, status=9/KILL
systemd[1]: dropbox.service: Unit entered failed state.
systemd[1]: dropbox.service: Failed with result 'signal'.
systemd[1]: dropbox.service: Service hold-off time over, scheduling restart.
systemd[1]: Stopped Dropbox Daemon.2) A dropbox process is running in memory:
2) A dropbox process is running in memory:
$top | grep dropbox
12229 user 20 0 398112 39552 20472 R 100.0 0.5 0:00.26 dropbox
jainraje wrote:Nothing comes back:
$ ps axo user,comm | grep dropbox
If nothing comes back (at that moment at least), no any Dropbox daemon is running. I cannot support your service setup. You should check what's going wrong there; it's not a Dropbox issue.
jainraje wrote:...
...
2) A dropbox process is running in memory:
$top | grep dropbox
12229 user 20 0 398112 39552 20472 R 100.0 0.5 0:00.26 dropboxAs seems, for some reason, it starts later. Why? 🧐 It's something you should figure out.
As can be seen the context is different! Now if you just run:
dropbox status
..., you will get "Dropbox isn't running!" for sure. Cosa it's so: there is not running Dropbox daemon in "rajeev" context; it's running in "user" context.
Your default context is rajeev, but you can switch to user using something like:
sudo -u user dropbox status
Now you will get the actual context (the user context). 😉
Good luck.
the `user` in the log was me removing my actual username. sorry that was misleading. there are only 2 contexts rajeev and root. i'm going to try to sort this out. i'm going to disable the dropbox systemd and run dropbox manually. i'll keep this thread updated. any comments or suggestions from you or others are well received. again, many thanks for your messages.
Update:
After disabling the dropbox systemd service unit and rebooting no dropbox was running in memory according to `top`. I was then able to successfully run dropbox from the command-line. All desired file/folders are synching at this point.
Now that via the command-line dropbox is working correctly I'll focus my attention on getting dropbox to auto synch after system boot using the systemd service unit. i recall reading somewhere a delay is required to get that scheme to work.
