Syncthing is working here so I’ll leave it as is, as I have been burned yesterday and today by trying to update pihole (on XU4). If I can’t fix this I’ll start a new thread or else wait until v141 comes out. In the meantime a fresh install of pihole on a Pi3 is working fine.
I’m sure it would work, but since Fourdee has added syncthing-inotify to DietPi, I think the least I can do is to provide information/feedback about it.
I can confirm, after reinstalling everything from scratch, that syncthing installs syncthing-inotify correctly, and both are visible as running in htop, but syncthing-inotify does not correctly detect file changes and therefore it does not propagate them to the other syncthing nodes.
I don’t have any syncthing-inotify@.service, just the one without the @ symbol.
I will try your version later and see if it starts working properly.
I have noticed that currently syncthing won’t detect the file changes even during the scheduled rescans. I need to scan manually in order for it to detect the changes properly and propagate them to the other syncthing nodes. There’s definitely something wrong with the default installation.
Oh, I forgot about that…
I will try to recreate the problem as soon as I can. Not today for sure, though… We are too busy with the New Year’s Eve preparations.
Oh, by the way… Happy New Year, everybody!
I can’t seem to have any valid information in the log. It’s always empty, even immediately after I make changes to a synced file.
It really looks like syncthing-inotify does not detect file changes at all.
I have also tried John’s version of the services. Still no go.
I added a file to the shared folder, and syncthing-inotify did not detect it, nor propagated it correctly to the other syncthing nodes.
Since my folder is hosted on a NAS, I’m wondering if this could be a limitation of syncthing and/or inotify, which does not correctly monitor/detect files that are mounted on a NAS.
I will try sharing a real local folder and see if it still fails.
That’s exactly the same behavior I am experiencing.
I guess the only workaround is to set the mounted folders with a high rescan frequency (60 seconds or so) while leaving the native folders managed by inotify. But this, of course, does not reduce the amount of cpu power “consumed” by the board.