Andy+

Better is to have on both sides the IgnoreList. As editor I use Notepad++, but also you can use similar editors. Simply open the file IgnoreList you find in each .sync folder and write line per line your excludions, e.g.: # Resilio + Syncthing .stglobalignore # IgnoreList is a UTF-8 encoded .txt file that helps you specify single files, paths and rules # for ignoring during the synchronization job. It supports "?" and "*" wildcard symbols. # # ? substitutes any single character in a filename # * substitutes a string of several (any number) characters in a filename # a/**/b ignore between root and target folder, will ignore folders a/b, a/x/b, a/x/y/b and so on # ABC/CDE F will ignore subfolder “CDE F" of “ABC" which is located in a subfolder # ########## OS generated files $RECYCLE.BIN $Recycle.Bin System Volume Information lost+found .DocumentRevisions-V100 .TemporaryItems .fseventsd .iCloud .DS_Store .DS_Store? .Spotlight-V100 .Trashes .Trash-* ~* *~ .~lock.* *.part *.filepart .csync_journal.db .csync_journal.db.tmp *.swn *.swp *.swo .dropbox .dropbox.attr *.crdownload ._* # ########## Firefox, Google Chromium incomplete downloads and other things *.part *.crdownload # ########## Synology files .SynologyWorkingDirectory @eaDir @SynoResource @synoResource .@__thumb # ########## Benutzerdefiniert - nicht synchronisierte Verzeichnisse und Dateien Thumbs.db thumbs.db .Thumbnails .thumbnails Ehthumbs.db ehthumbs.db Desktop.ini desktop.ini sync.ffs_db sync.ffs_lock conflict # ########## ownCloud files ._sync* .csync_journal.* .owncloudsync.* # ########## Resilio files .sync !sync *.rsls # ########## syncthing files .stfolder .stignore .stversions .syncthing .syncthing* .syncthing.*.*.tmp ~syncthing~*.*.tmp # ########## vim files .*.swp The Resilio and Syncthing entrances I have, since I using Resilio and Syncthing in parallel by different reasons.

Thats true. But is fact, used scripts with # at the beginning of lines are ignored from the software or user, which use that script, here is IgnoreList used by Resilio. It means: # bullshit | is ignored #bullshit | is ignored bullshit | is not ignored

Between v2.6.2 from Nov. 2018 and v2.7.2 from Jul. 2020 are a lot of new technology and updates. Maybe there is a confusion between that versions, since v2.7.0 there are also some structural news in the software. Maybe check your .sync/Archiv about deleted and archived files on both sides.

A re-install is not needed. In the moment you use the free version and if you buy a license you have a good benefit from. Store the license on the related device, wnet in the Resilio GUI above right to the settings and then to the License tab. In the filemanager went to the stored license and confirm.

Maybe you have some hidden files or some time problematic files like thumbs.db is transfered from Windows etc. which brake a complete deleting. So for such files are a Ignore List is needed.

Usually such directories are also deleted

In the Linux world it is standard that script lines with # at the beginning is a character for commenting out. Everything that follows a # is at most a comment, nothing else. And it doesn't matter whether there is a space after it or not. Sometimes // are also used, but this is not common. # are not errors, but give the user the choice, e.g. activate or deactivate a parameter etc. More about the IgnoreList here https://help.resilio.com/hc/en-us/articles/205458165-Ignoring-files-in-Sync-Ignore-List-

Usually its a permission problem. Mainly Resilio is not able to manage the file.

This is one of the biggest disadvantages of this software, but also of its biggest competitor, Syncthing. However, since I have Synology servers, I use ownCloud or Synology Drive for sharing links. This means with this is no installation of software required. I can live very well with this solution. I have with Resilio and Syncthing software for all platforms and because of the P2P technology I have very fast data exchange directly to the next device.

At the end maybe is the best, to delete the complet Identity. On a Windows 10 computer you find it C:\Users\>USERNAME<\AppData\Roaming\Resilio Sync Service\.SyncUserXXXXXXXXXX\identity.dat But I think, in the follow you must reconnect all the devices and peers, but Im not sure about that.

You are welcome ... 👍

Normally you can see over the GUI, but this is not available on your NAS. So I only can speak about Synology and is /volume1/@appstore/resiliosync/var/sync.log

Doe you analyse any logs and other files? Doe you have enough space on storage and also enough RAM? How much peers you have with which no. of files and folders? Because it seems that Resilio starts normal, but doesnt run continously because of other reasons. Fragments means, after de-installation there are maybe a rest of any files from Resilio, you delete manually.

No comments of Resilio development?

If you user the "camera" peer of the Android APP, its a one way solution to a client, here your NAS. Its better to implement that as a normal peer as two way sync.

Thats fine. Otherwise maybe reboot your NAS. If that also not help, maybe uninstall Resilio and search afterwards for all fragments to delete. Then reboot and try a very new installation.

You have also updated Resilio? https://help.resilio.com/hc/en-us/articles/206178964-QNAP

As tools I use the Synology Filestation and WinSCP https://winscp.net/eng/download.php look at "https://winscp.net/eng/docs/screenshots" dwon to "Changing Properties of Files and Folders" to see the menu to set the above.

Maybe the problem has to do with Synology’s partly strange ACL system. In my opinion maybe this have nothing to doe directly with Resilio. However, in most cases I can remove such things with a standard procedure. In such cases, I’ve deleted the Synology ACLs by setting the owner and group to root and octal rights to 0777 for all files and subdirectories in the affected peers. Then I go back to Synology DSM into filestation and inherit the permissions again in these peers in all files and subdirectories. This is kind of a standard procedure if I have any kind of permission issue. But I outline, is also a procedure more for experts and people, which know the background of such things.

Also here, from time to time doesnt start from boot on my DS415+

I think, Resilio is installed in any condition. In which way you had installed, as service or normal? And other websites are visible properly?

Unfortunately there seems to be a little bit less staff and that is counterproductive.

I think, at least is understood from all people. But what the people see regarding activities to solve Bugs and to have regular Updates etc. is another thing.

Depending on the OS on your PC you find a working folder, in which files like *.db and *.db-wal are stored. Stop Resilio and delete such files and start again. Then a new indexing is starting.

Regarding the confusion of the DSM 7 permissions (root/user) during the installation process I got today the follow message from Synology: Start Yes, you may continue using root privilege ONLY if you apply a token from us to bypass the lower privilege setting this time round, without which, your package installation would fail in DSM7.0 Beta. As mentioned in point 2 in my previous email: To avoid future update issues, It is highly recommended that your package can be modified to match our new lower privilege framework. Please develop according to the new developer’s guide provided, and your users will still be able to carry out manual installation even if the package has yet to be approved and signed by Synology. In case of development time or technical constraints, we provided a tentative alternative for the benefit of existing third-party packages in our Package Center. To ensure that your current package remains functional in DSM7.0, you will be allowed to continue using the same privilege level settings for your new versions until further notice. However, you have to apply for an exemption token from us to be able to develop smoothly on your NAS device. Please note that your package will have to be officially approved and signed by Synology before your package can be released in our Package Center or to users for manual installation. If you wish to continue running as root rather than user, please follow the instructions below: i) Log in to the DSM of NAS device(s) that you want to develop / test on ii) Open Support Center → Support Services → Log Generation → Check “System” → Generate logs → Download “debug.dat” iii) Send this “debug.dat” to us by replying to this email (if you have more than one NAS device, please label the respective debug.dat clearly.) iv) We’ll then send you the token file (each token is only valid for one specific NAS device), for which you’ll have to rename it to syno_dev_token and place it under this location → /var/packages/ v) You are all set to develop the new version using your current privilege level setting. Our ultimate goal is still hoping for all of our package developers to be able to abide by our new privilege setting in future versions. End I try to install the related Resilio package with the following message: