Andy+

Members
  • Posts

    584
  • Joined

  • Last visited

Posts posted by Andy+

  1.  On 7/13/2020 at 5:48 PM, laurin1 said:

    I've had numerous issues with 2.7.1, including this one:

     

    The only solution I found was downgrading to 2.7.0.

    My problems started with a database error. I removed and added back the folder in question, but never would finish on all machines. 

     

     

    A similar issue I have also with one of my 3 Synology´s since a couple of days, maybe since running v2.7.1 and the Synology is connected over the Internet to all my other 2 Synology´s and other devices. All my devices with v2.7.2 are running, but this one have a problem. The connection to this Synology is good, all peers are connected, but nothing with syncing. Also after stopping Resilio, deleting the database, starting Resilio again, the same situation.

    To help me, I run for the relevant peers Syncthing, so in the moment I have a solution, but is not the final. Up to v2.6.4 or 2.7.0 I had never problems, its not clear for me, what I can doe.

  2. In such cases, it’s normally not a issue of Resilio. In your case it seems that the content is blocked for Resilio and is more a thing of the right permissions.

    To fix this again, I recommend resetting recursiv the System-ACLs inside of the related folders for all content with root:root, octal 0777 and then resetting the ACLs back in the system by inheriting them from the root folder back into the files and subdirectories. Then it should work again.

  3. The first thing to check is whether the new router has all the necessary ports open. These normally have 5 digits. As a rule, UPnP can be activated for this, but fixed ports can also be defined and released for this. However, UPnP is more convenient.

    The second step is to check whether a firewall, which could also be at the service provider, prevents a port connection, often it is restrictive firewalls. For this reason, I use Syncthing for restrictive firewalls, because Syncthing http:// and https://, meaning port resolution 80 and 443 is also mastered, Resilio cannot do that, at least for me so far not understandable.

    Then the settings would have to be checked again to see whether all relevant tracker servers that are required for the connection are activated. But often such problems are related to the ports.

  4. I'm basically just as concerned. I had some problems, which is why I also looked at Syncthing...

    I don't want to give up so quickly. After I had properly compared, I deleted all identities and databases, renewed the identities, the indexings and databases were newly created. Since then, the Android APP has been running well again.

    Nevertheless, I was to some extent forced to use syncthing in advance, as there were non-solvable problems with the Android APP. Another fact is that one of my Synology's is located in a location with low internet bandwidth.

    So I was not only forced to use Syncthing, but also parallel to Resilio, in that peers were interlinked. This works very well with the matching ignore pattern and I will preemptively use it and see what the future holds.

  5. If selective sync is not used, a 1:1 copy is made on the connected peer side. On all 2 peers are a synced dataset. With 3 peers it is triple. That is so wanted.

    If selective sync is set, there are no copies on the affected peers, only the directory structure and placeholders for the files. Then the files or directories must be activated if the files are to be physically available on the respective peer. That is also wanted.

    To share something, it doesn't have to be an extended folder, you can also share standard folders. But then the keys have to be exchanged.

    Maybe you are working intensively on the documentation.

    https://help.resilio.com/hc/en-us

  6. So I have understood you have on Resilio side

    /sync/Music/Music

    /sync/Music/Master

    /sync/Music/TestSync

    so on server side you have

    /srv/dev-disk-by-label-Hippo/Music/Music/Music

    /srv/dev-disk-by-label-Hippo/Music/Music/Master

    /srv/dev-disk-by-label-Hippo/Music/Music/TestSync

    That is what I see with the sequence

    /srv/dev-disk-by-label-Hippo/Music:/sync