We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
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.
Walter
Dropbox Staff
Dropbox StaffHI Walter,
Thank you for your message.
To summarize I installed the headless dropbox on a headless ubuntu 16.04 and confired a systemd service unit to run at system boot time (using my username as opposed to root). Finally, I enabled the auto-start at system boot as any other systemd service unit by issuing the following command: $sudo systemctl enable dropbox
My understanding is the above will setup the system to always run the dropboxd after system reboot. No manual intervention is required.
The dropbox.py (Dropbox Desktop App) and dropboxd work together yes?
Every time I run dropbox status is always returns Dropbox isn't running yet some files appeared to sync correctly. So I'm really confused and do not feel confident the system is setup correctly.
jainraje wrote:...
Every time I run dropbox status is always returns Dropbox isn't running yet some files appeared to sync correctly. ...
Hi jainraje,
Did you make sure you have run 'dropbox status' under the same user context like the Dropbox daemon? Take in mind that every user can have independent Dropbox context and running the control script in one context targets the Dropbox daemon on the same context, not any other! 😉
Hope this helps.
I believe yes to your question.
Upon closer inspection is appears the daemon is having errors starting.
$sudo journalctl -u dropbox.service
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'.
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
