Bug report: Sync ignores Linux group permissions

Recommended Posts

I want to sync a folder which has the owner:group root:system and the permissions drwxrwxr-x (775).

I've edited /lib/systemd/system/resilio-sync.service to run sync as user:group rslsync:system.

I've edited /etc/passwd so tha the user rslsync has the group system.

I've made a systemctl daemon-reload and a systemctl restart resilio-sync.

Sync runs but won't write to the folder and says it has no permission.

When I login as user rslsync I can obviously write to the folder because I have sufficient group permissions.

Only when I change the owner of the folder to rslsync Sync can write to that folder.


Ubuntu 18.04.2 LTS and Resilio Sync 2.6.3 installed with apt.

Link to comment
Share on other sites

Update on further research:

Changing the permissions to 777 has no effect.

After changing the owner to rslsync and accessing the folder with Sync I can change the owner back to root and Sync can still access the folder. So probably Sync has some kind of internal database where it stores assumed permissions?

Link to comment
Share on other sites

  • 2 weeks later...

I don't know if this is a Resilio or Linux issue, as I run into problems with users not having write permissions despite being in the group on Linux from time to time.

Solution has been to use setfacl and give write access to the Resilio dirs to the user. Easier than changing users, systemd files or using chown over and over.

Link to comment
Share on other sites

On 7/18/2019 at 7:45 PM, Stronginthearm said:

Sooo... nobody cares?


same issue. Any ideas about this here? I chengaed the owner of the files to the user Sync is running (with netgear it is user "admin") restartet sync and then changed the owner back. The sync is fine again but like to see this solved.



Link to comment
Share on other sites

  • 4 weeks later...
  • 8 months later...

Same here. Still present ind

Copy of my Bugreport:


Dear Support,

with my to resilio-sync_2.7.0.1366-1_amd64, rslsync introduced two new problems:

Issue 1:

It stopped to honor linux group permissions, reporting countless "cannot update timestamp" problems on files with absolutely proper permissions that had no issues with previous version.


rslsync:x:AAA:BBB:Bittorrent Sync:/home/btsync:/bin/false




cat /etc/systemd/system/resilio-sync.service
Description=Resilio Sync service

ExecStartPre=/bin/mkdir -p /var/run/resilio-sync
ExecStartPre=/bin/chown -R rslsync:rslsync /var/run/resilio-sync
ExecStart=/usr/bin/rslsync --config /etc/resilio-sync/config.json



ps shows rslsync running on user rslsync



ls -la /srv/share/ |grep 0000
drwxrwxrwx  1 root    rslsync   182 Apr  3  2018 0000_Testfile

This directory is so blatantly read-writable... but still reports "cannot update timestamp".

The seems to be a linux problem not specific to my machine, I´d therefore prefer to spare the logs.

Issue 2:

rslsync stopped recognizing storage folders behind symlinks. Exactly this configuration worked before updating. I only updated the resilio deb file, so no other actions were taken between last running config and update. Also my system restarts resilio on every night and resilio was running prior to updating, so the configuration was not accidentially changed without restarting...

Raw folder:

/srv/resilio => /disk/ssd/resilio

"storage_path" : "/srv/resilio/"

Good Bughunting - quick fix appreciated.


Link to comment
Share on other sites

  • 1 year later...

I also experienced the same problem after upgrading my storage system - moving to a new machine, new installation - but still using the most up-to-date Resilio Sync (2.7.2)

The solution I found was https://connect.resilio.com/hc/en-us/articles/360010904799-Can-t-set-modification-time-for-file

Link to comment
Share on other sites

  • 3 months later...

Also experiencing the same problem. 

However, in my case,

  1. First, I incorrectly shared a directory as read-only.
  2. I deleted the remote sync, 
  3. re-shared as read-write, with the same destination directory
  4. only NOW did this problem arise.   

I think that it's an internal resilio sync thing. Resilo sync is not doing some re-check of permissions, (or doing the check and ignoring / not storing the results) and then giving an incorrect error. 


Resilio Sync 2.7.2 (1375)
Linux 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) x86_64 GNU/Linux

Link to comment
Share on other sites

  • 1 year later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.