AntoniosHadji

I have it working now, but I feel there must have been a better way to fix the original problem. I changed the group on the parent folder to rslsync, I added user rslsync to group rslsync I had to delete the synced files on my android device (otherwise a duplicate copy was created) I relinked the android device to the sync folder Here is my current config { "storage_path" : "/var/lib/resilio-sync/", "pid_file" : "/var/run/resilio-sync/sync.pid", "agree_to_EULA": "yes", "directory_root" : "/home/antonios/Music/sync", "directory_root_policy" : "all", "webui" : { "listen" : "127.0.0.1:7962" } } What I have set up is a folder called 'sync' in the Music directory under my home directory on Ubuntu 16.04. I have the resilio app on my android device. I want to be able to drop audio files into the 'sync' folder and have them automatically sync to my android device. This is all working now. But I basically had to start over from scratch to get it working. It would have been nice if the android app could have known that the 'sync' folder that already existed was the folder that I wanted to sync into. Also the permissions issues on the Ubuntu machine seemed unclear why they were not handled automatically.

When I install resilio-sync using apt-get, I see these messages: Processing triggers for man-db (2.7.5-1) ... Setting up resilio-sync (2.4.1-1) ... initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' Processing triggers for systemd (229-4ubuntu10) ... Is this anything to be concerned about? When I start resilio-sync it fails to start. ● resilio-sync.service - Resilio Sync service Loaded: loaded (/lib/systemd/system/resilio-sync.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Wed 2016-10-05 13:06:42 EDT; 21s ago Docs: http://help.getsync.com/ Process: 1521 ExecStart=/usr/bin/rslsync --config /etc/resilio-sync/config.json (code=exited, status=1/FAILURE) Process: 1517 ExecStartPre=/bin/chown -R rslsync:rslsync /var/run/resilio-sync (code=exited, status=0/SUCCESS) Process: 1511 ExecStartPre=/bin/mkdir -p /var/run/resilio-sync (code=exited, status=0/SUCCESS) Oct 05 13:06:42 antonios-linux systemd[1]: Failed to start Resilio Sync service. Oct 05 13:06:42 antonios-linux systemd[1]: resilio-sync.service: Unit entered failed state. Oct 05 13:06:42 antonios-linux systemd[1]: resilio-sync.service: Failed with result 'exit-code'. Oct 05 13:06:42 antonios-linux systemd[1]: resilio-sync.service: Service hold-off time over, scheduling restart. Oct 05 13:06:42 antonios-linux systemd[1]: Stopped Resilio Sync service. Oct 05 13:06:42 antonios-linux systemd[1]: resilio-sync.service: Start request repeated too quickly. Oct 05 13:06:42 antonios-linux systemd[1]: Failed to start Resilio Sync service. ~ I have edited the config file to show as follows: { "storage_path" : "/home/antonios/Music/sync/", "pid_file" : "/var/run/resilio-sync/sync.pid", "agree_to_EULA": "yes", "webui" : { "listen" : "127.0.0.1:7962" } }

@Helen, currently I'm running rslsync manually from the ~/bin folder. If I install the resilio-sync using apt, how do I make sure the config stays the same? I am currently redirecting the web gui to a different port and I have it syncing one folder with my android phone.

@Helen this is an error message that displays when the package is installed or removed. My understanding is that Ubuntu 16.04 uses systemd where previous versions used upstart.

The official package complains of 'unable to connect to upstart' on Ubuntu 16.04