All new transfers are failing as read-only

Support
1

I’ve had a successfully running instance between and send only windows 10 host running 1.27.11 and ubuntu server 24 receive only running version 1.27.2-ds4. But now all new files have been unable to sync with a file-system marked as read-only.

The umask is 755 or rwxrwxr-x for the owner, which is the same user the service is running under in the linux receive host. I haven’t changed anything on the filesystem as it’s a zfs zpool that’s been humming along without issue. I’m not sure what to check.

I’ve restarted the service on both hosts while they’re running to no avail, and it fails if I create any new file or folder on the windows host. I haven’t checked on this in awhile so it may have gone into this state some time back. I also enabled ignore file permissions on both hosts.

What shall I try next?

1 Like
2

Stupid systemd changes. I added a new directive in the systemd unit file to allow writing to the folder that is being synced. This wasn’t needed before and is now a required part of systemd.

The directive in the unit-file is: BindPaths=/path/to/syncthing/root

and it’s working again as expected. D’oh!

2 Likes
3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.