.syncthing tmp files not owned by user

I have syncthing running on several machines. Syncthing is enabled and started as syncthing@jack.service on all machines. The UID and GID are the same on all machines.

Host A - v0.14.50

$ ps -aux | grep -i syncthing


jack 2544 0.4 0.4 1241576 75980 ? Sl Sep18 19:16 /usr/bin/python2 /usr/bin/syncthing-gtk

jack 5557 27.5 0.7 2543644 123848 ? SNsl Sep19 701:45 /usr/bin/syncthing -no-browser -no-restart -logflags=0

Host B - v0.14.18-dfsg1, Linux (ARM)

jack 11988 157 32.6 948896 310332 ? Ssl Sep20 2434:54 /usr/bin/syncthing -no-browser -no-restart -logflags=0

The issue is that all the .syncthing tmp files are owned by root:root on Host B. The only way to keep the syncing process running (not stalling at some point) is to run

sudo chmod -cR jack:jack /mnt/Sync

in a loop very three minutes. I use the -c option to check progress.

After each loop the syncing continues. If I stop the loop at some point the syncing stalls. I also get in the WebUI under failed items it reports operation not permitted.

Host C - v0.14.18-dfsg1, Linux (ARM)

$ ps -aux | grep -i syncthing

jack 13908 2.0 4.0 899904 38400 ? Ssl Sep18 85:31 /usr/bin/syncthing -no-browser -no-restart -logflags=0

All files sync with no issues.

What am I not seeing?

I figured it out with some additional testing. Host B is also running encfs (as root). The encfs clear text directory is what Syncthing syncs into. There is obviously an interaction between encfs creating the encrypted files and syncthing bring in new files.

If I figure out a work around I will post the results.

Thank you for a great product.

1 Like

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