dropbox startup problems

New to Debian (Or Linux in general)? Ask your questions here!

dropbox startup problems

Postby ollie2017 » 2017-12-06 18:56

Hoping someone can help. Although I have some level of experience with Mac OS X and linux at the command line, delving into editing the start up processes is entirely new. After trawling the internet I haven't been able to find a solution to the problem and haven't seen similar error logs posted.

I'm running Debian 9 with no desktop environment/x11 on old an old mac mini (already taken a while figure out rEFInd and dual booting a backup installation of OS X due to 32-bit EFI but 64-bit CPU) and intend to use it as a file server and music server.

I Installed dropbox and ran python script and succesfully sync'd Dropbox folder to server.

However when I follow instructions on unoffical dropbox wiki (http://www.dropboxwiki.com/tips-and-tri ... nvironme...) to try to use an init.d script to automatically start dropbox as a service (using their script for debian) on start up I get these error messages below. I'm sure I have overlooked something which is probably very obvious but would be grateful for anyone's help to solve this problem.



Thanks,



Ollie





● dropbox.service - LSB: dropbox service
Loaded: loaded (/etc/init.d/dropbox; generated; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2017-12-04 23:53:42 GMT; 1min 31s ago
Docs: man:systemd-sysv-generator(smiling face with sunglasses
Process: 534 ExecStart=/etc/init.d/dropbox start (code=exited, status=2)

Dec 04 23:53:42 mac-mini systemd[1]: Starting LSB: dropbox service...
Dec 04 23:53:42 mac-mini dropbox[534]: /etc/init.d/dropbox: 15: /etc/init.d/dropbox: : not found
Dec 04 23:53:42 mac-mini dropbox[534]: /etc/init.d/dropbox: 17: /etc/init.d/dropbox: : not found
Dec 04 23:53:42 mac-mini dropbox[534]: /etc/init.d/dropbox: 20: /etc/init.d/dropbox: Syntax error: "do" unexpected (expecting "}")
Dec 04 23:53:42 mac-mini systemd[1]: dropbox.service: Control process exited, code=exited status=2
Dec 04 23:53:42 mac-mini systemd[1]: Failed to start LSB: dropbox service.
Dec 04 23:53:42 mac-mini systemd[1]: dropbox.service: Unit entered failed state.
Dec 04 23:53:42 mac-mini systemd[1]: dropbox.service: Failed with result 'exit-code'.





and





Dec 04 23:54:09 mac-mini sudo[852]: ollie : TTY=tty1 ; PWD=/home/ollie ; USER=root ; COMMAND=/bin/systemctl service
Dec 04 23:54:09 mac-mini sudo[852]: pam_unix(sudo:session): session opened for user root by ollie(uid=0)
Dec 04 23:54:09 mac-mini sudo[852]: pam_unix(sudo:session): session closed for user root
Dec 04 23:54:12 mac-mini sudo[854]: ollie : TTY=tty1 ; PWD=/home/ollie ; USER=root ; COMMAND=/bin/systemctl
Dec 04 23:54:12 mac-mini sudo[854]: pam_unix(sudo:session): session opened for user root by ollie(uid=0)
Dec 04 23:54:13 mac-mini systemd-timesyncd[388]: Timed out waiting for reply from 195.219.205.9:123 (2.debian.pool.ntp.org).
Dec 04 23:54:13 mac-mini systemd-timesyncd[388]: Synchronized to time server 178.79.152.182:123 (2.debian.pool.ntp.org).
Dec 04 23:54:16 mac-mini sudo[854]: pam_unix(sudo:session): session closed for user root
Dec 04 23:54:20 mac-mini sudo[857]: ollie : TTY=tty1 ; PWD=/home/ollie ; USER=root ; COMMAND=/bin/systemctl dropbox.service
Dec 04 23:54:20 mac-mini sudo[857]: pam_unix(sudo:session): session opened for user root by ollie(uid=0)
Dec 04 23:54:20 mac-mini sudo[857]: pam_unix(sudo:session): session closed for user root
Dec 04 23:54:24 mac-mini sudo[859]: ollie : TTY=tty1 ; PWD=/home/ollie ; USER=root ; COMMAND=/bin/systemctl dropbox
Dec 04 23:54:24 mac-mini sudo[859]: pam_unix(sudo:session): session opened for user root by ollie(uid=0)
Dec 04 23:54:24 mac-mini sudo[859]: pam_unix(sudo:session): session closed for user root
Dec 04 23:54:31 mac-mini sudo[861]: ollie : TTY=tty1 ; PWD=/home/ollie ; USER=root ; COMMAND=/bin/systemctl status dropbox.service
Dec 04 23:54:31 mac-mini sudo[861]: pam_unix(sudo:session): session opened for user root by ollie(uid=0)
Dec 04 23:54:31 mac-mini sudo[861]: pam_unix(sudo:session): session closed for user root
Dec 04 23:55:14 mac-mini sudo[864]: ollie : TTY=tty1 ; PWD=/home/ollie ; USER=root ; COMMAND=/bin/systemctl status dropbox.service
Dec 04 23:55:14 mac-mini sudo[864]: pam_unix(sudo:session): session opened for user root by ollie(uid=0)
Dec 04 23:55:14 mac-mini sudo[864]: pam_unix(sudo:session): session closed for user root
Dec 04 23:55:40 mac-mini sudo[868]: ollie : TTY=tty1 ; PWD=/home/ollie ; USER=root ; COMMAND=/bin/systemctl status dropbox.service
Dec 04 23:55:40 mac-mini sudo[868]: pam_unix(sudo:session): session opened for user root by ollie(uid=0)
Dec 04 23:55:40 mac-mini sudo[868]: pam_unix(sudo:session): session closed for user root
Dec 04 23:55:47 mac-mini sudo[871]: ollie : TTY=tty1 ; PWD=/home/ollie ; USER=root ; COMMAND=/bin/systemctl
Dec 04 23:55:47 mac-mini sudo[871]: pam_unix(sudo:session): session opened for user root by ollie(uid=0)
Dec 04 23:55:54 mac-mini sudo[871]: pam_unix(sudo:session): session closed for user root
Dec 04 23:56:01 mac-mini sudo[874]: ollie : TTY=tty1 ; PWD=/home/ollie ; USER=root ; COMMAND=/bin/journalctl -xe
Dec 04 23:56:01 mac-mini sudo[874]: pam_unix(sudo:session): session opened for user root by ollie(uid=0)
Dec 04 23:56:07 mac-mini sudo[874]: pam_unix(sudo:session): session closed for user root
Dec 04 23:56:11 mac-mini sudo[877]: ollie : TTY=tty1 ; PWD=/home/ollie ; USER=root ; COMMAND=/bin/journalctl -xe
Dec 04 23:56:11 mac-mini sudo[877]: pam_unix(sudo:session): session opened for user root by ollie(uid=0)
ollie2017
 
Posts: 2
Joined: 2017-12-06 18:50

Re: dropbox startup problems

Postby ollie2017 » 2017-12-07 19:12

After more reading about init.d and systemd and their history and differences I found another helpful webpage https://github.com/joeroback/dropbox summarising how to setup dropbox on systemd:

Place the dropbox@.service file into /etc/systemd/system
Reload the daemons: systemctl daemon-reload
Enable the service for users: systemctl enable dropbox@username
Start service: systemctl start dropbox@username

It appears to be syncing in the background without the need to login which is good news as that is how I wanted it, as this is to be a headless server.

Although my undertanding is their seems to be more than one way of sorting this out, I suppose I am just wondering if this is the "correct" way of doing things or not?

Thanks.
ollie2017
 
Posts: 2
Joined: 2017-12-06 18:50


Return to Beginners Questions

Who is online

Users browsing this forum: No registered users and 3 guests

fashionable