xfelix

Members
  • Content Count

    22
  • Joined

  • Last visited

About xfelix

  • Rank
    Member
  1. @Egon Heuson, eg. the latest download is https://download-cdn.resilio.com/2.6.3/Synology/resiliosync_88f6281_2.6.3-1.spk, just change 2.6.3 to 2.6.1.
  2. The problem Nas is DS112 which only has 256MB ram I believe. The one I am running docker is DS216+ii which upgraded ram to 8GB.
  3. I use Resilio Sync Synology pack on an old NAS. 2.6.3 has severe load issue which cause whole NAS extremely slow response. Very high CPU, Mem, and Disk usage. I downgraded to 2.6.2 but has 2G file transfer limit issue. So I have to stay on 2.6.1 by now. I have another Synology nas which can run Docker. No issue of 2.6.3 in container environment.
  4. after almost one month i still haven't seen a clear answer for the issue of 2.6.2 on Synology nas. Is it safe to install the 2.6.2 package on Synology NAS or leave it as 2.6.1? I am using an old model of Synology nas which does not support docker. That's why I ask this question. Thanks.
  5. @sauvagii not sure what tool you use to edit photos. If you use lightroom or similar app, why not store the raw images and editing configurations on the Synology NAS directly, then create a schedule backup from Synology NAS to WD NAS? Your desktop PC is just an interface to use those photo editor applications (mount a folder of Synology NAS).
  6. I believe 18 serial was just released. It's quite new. At least you can use Docker to run resilio in Ubuntu.
  7. You need to be patient. Just wait. It will eventually load the folder info after couple minutes. All depends the amount of data you sync and complexity of the folders. It needs to load everything into memory then display the WebUI. That's how ResilioSync webui designed. Because Synology NAS usually does not have big RAM. Sometimes it takes half hour or longer. You may also try to pause/disconnect some big sync folders through command line. Then try the Webui. Good Luck.
  8. just manual install the package you downloaded. Click all 'next'. It will detect the existing old one and update it. Please note the user account for ResilisoSync has been changed from 'admin' to 'rslsync', need to make sure the folders permission for the new user.
  9. you can create a github account, fork that official one and modify the version number to 2.5.5 (no coding skill needed). Then create an auto-build repo on docker hub so that you can create a docker image by your own with the latest resiliosync.
  10. i agree. i have to set ram limit for the docker container that runs ResilioSync otherwise it will eat up all the host RAM. On a resources limited NAS, it will take ages to open the ResilioSync webui because of not enough RAM. If dev can find ways to improve the memory efficiency, that will be great.
  11. you need change ownership of those sync folders to rslsync user account. if your synology nas supports docker, strong recommend to use resiliosync docker container instead of package. Just mount the sync folders and no longer have the permission issues.
  12. @Helen Thanks for the help. After reset the peer, no more SyncDiscovery.cpp assert failed error. However, after using 2.5.5 couple days, i noticed a different assert failed error message. What this means? Thanks. "assert failed /home/jenkins/slave-root/workspace/Build-Sync-Manually/bittorent.cpp:846"or 891
  13. @Helen for me, none of my folders have 'use predefined hosts' checked. But still have the same error message as OP.
  14. Same here. No idea what it is. Running 2.5.4 in Synology Docker.