Take Your Search Game to the Next Level with Dropbox Dash 🚀✨ Curious how it works? Ask us here!
Forum Discussion
Dropbox on debian server does not start
On a Debian server I created the user named UserDB, with its credentials.
In its Home Folder (/srv/dev-disk/Home/UserDB) I installed Dropbox as in the official guide.
I also saved the dropbox.py file in the ~/Dropbox folder.
Now, if I connect via SSH with this user, I enter in the ~/Dropbox folder and launch dropbox.py I can start Dropbox, stop it, see its status, add folders to exclude, ...
So everything looks OK.
I then created the file: /etc/systemd/system/dropbox.service with:
[Unit] Description=Dropbox Daemon After=network.target [Service] Type=simple User=UserDB ExecStart=/srv/dev-disk/Home/UserDB/.dropbox-dist/dropboxd ExecStop=/bin/kill -HUP $MAINPID Restart=always [Install] WantedBy=multi-user.target
Now, if I connect via SSH as UserDB and run systemctl status dropobox.service I see the service as active and if I run dropbox.py I see that Dropbox is running and is synchronizing.
If instead I connect as root and run systemctl status dropbox.service, I still see the service active, but with dropbox.py status I see the message: Dropbox isn't running!
If write ./dropbox.py start I see:
Starting Dropbox... The Dropbox daemon is not installed! Run "dropbox start -i" to install the daemon
Where am I doing wrong?
6 Replies
GioSomma wrote:...
Where am I doing wrong?
Hi GioSomma,
Actually, you weren't doing anything wrong, anywhere. 😉 Might be pointed some imperfections in your service file, but it's fine still.
The problem comes from your expectations! 🧐 Note that Dropbox application is a client mode application, as noted in users guide, despite not very noticable. That's why when you run Dropbox control script in particular context (local user), it expect the daemon to be installed and run in the same context!
GioSomma wrote:On a Debian server I created the user named UserDB, with its credentials.
In its Home Folder (/srv/dev-disk/Home/UserDB) I installed Dropbox as in the official guide.
...
If instead I connect as root and run systemctl status dropbox.service, I still see the service active, but with dropbox.py status I see the message: Dropbox isn't running!If write ./dropbox.py start I see:
Starting Dropbox... The Dropbox daemon is not installed! Run "dropbox start -i" to install the daemon
...Yes, of course! The daemon is running (and got installed) in 'UserDB' context, but the control script is running in 'root' context. 😉 That's where the confusion comes from.
To workaround the above, change control script' running context. For the 'root' it's enough something like:
su UserDB -c 'dropbox status'
Consider 'status' more as a example. Could be any valid option/subcommand. For other users above should be extended to:
sudo su UserDB -c 'dropbox status'
Hope this helps.
Many thanks Здравко
I understand your answer.
Having been installed on a server it is enough for me that Dropbox works when the server is up.To give instructions to Dropbox I can also connect with the UserDB user. What is important is that when I log out of the terminal, Dropbox continues to work.
Since there is no GUI I cannot verify what is happening.
I can only see if adding or deleting a file replicates it correctly, but I can't do anything else to check if Dropbox is working.
GioSomma wrote:...
Since there is no GUI I cannot verify what is happening.
I can only see if adding or deleting a file replicates it correctly, but I can't do anything else to check if Dropbox is working.Hi GioSomma,
That's not entirely correct. Yes, you can't check current status on status bar or similar. If you have installed Nautilus (or compatible) on your server and the Dropbox plugin together your can redirect graphical output to the machine you are working on. The bottleneck here is that your workstation setup should support X redirection. If your machine match this requirement it's not a problem to run Nautilus with redirected output and see what's going on live.
Hope this gives an idea.
