• Content Count

  • Joined

  • Last visited

About luckman212

  • Rank
    Advanced Member
  1. Really strange. I guess there was something broken on the global tracker. Can anyone from Resilio comment so we know it wasn't some kind of hack etc? @Helen or @RomanZ ?
  2. Still not sure WHY this worked, BUT in case it helps anyone... what I did was revert from the "Service Mode" to "Standard App Mode". Something about running it as a Windows service was preventing sync. Again, not sure what or why (firewall disabled, nothing else changed in the environment afaik). To do this, I re-installed Resilio Sync in non-service mode. Then I copied the contents of "C:\Windows\System32\config\systemprofile\AppData\Roaming\Resilio Sync Service" into "%APPDATA%\Resilio Sync" and just disabled the service for now. Then I ran Resilio Sync.exe—folders were picked up and peers were restored and began syncing immediately.
  3. Today my problem got worse... now all folders show 0 / 0 for peers. I hope this turns out to be some DNS problem or something that Resilio can fix on their end. My last successful sync was Dec 24. Anyone found any temporary workarounds?
  4. @radiofun If you have a Windows machine, see this link for how to get at your logs: If you're using a NAS (Synology, QNAP etc) then try this:
  5. @jimger Did you ever figure this out?
  6. Did you ever get your answer? I would imagine carefully copying ALL the config files (including hidden) from the "service folder" (probably something like "C:\Windows\System32\config\systemprofile\AppData\Roaming\Resilio Sync Service") into the regular location which should be "%APPDATA%\Resilio Sync" ... and then re-installing the app in non-service mode should work. But I haven't tested this. Update: I actually tested the yesterday. It works!
  7. Hmm. I wonder if this is the same problem I'm having... I opened a case w/ Support about it. Haven't been able to figure it out yet. Suddenly after working fine for months, all non-local peers are showing as offline (they are not). Could something be misconfigured on Resilio's side (trackers)?
  8. So far, setting the resync interval to 3600 is at least allowing the background scanning to finish. The iSCSI option is definitely a possibility but since it requires moving all the files, reformatting the storage etc that's going to have to wait. This works for now.
  9. Thanks, I guess there are too many files like you said, and the background indexing is just never completing. I'll try setting it to 1 hour and see. I am realizing that the main problem is that due to all the files being on a Synology NAS that is accessed over SMB from the Windows machine that has Rslsync running. So Rslsync isn't getting filesystem change notifications, and relies 100% on the background scan to detect changes. I tried running the Sync package directly on the Synology, but the CPU on the Synology was just too weak to handle this many files. Thus we moved to the Windows server but kept the files on the NAS. Now I guess the "real" solution will be to eliminate the NAS and move the storage locally to the Windows server.
  10. Anyone got any idea on this? Do I just have to try it and cross my fingers?
  11. Any chance you guys would consider starting a #resiliosync IRC channel on freenode? It would be a great addition to the forum for realtime chat about the software, for users to help each other out etc.
  12. Today I noticed that there was a "Disk" tab in the lower left of the Rslsync stats area, so I clicked on it and saw that the "Disk" was hovering at >90% endlessly. I checked in Task Manager to see if that matched up. It didn't - according to Task Manager, the C drive was basically idle (0-1%). So, not sure where this phantom activity is coming from. Is Rslsync doing a re-index of a network share and counting this as "Disk" access? That's the only thing I can think of, since my shared folders are all on mapped drives. Again I don't know how to tell from looking at this what it's doing -- the logs don't clearly indicate it either.
  13. Hmm, in that case I think I've got something else going on. I don't see anything in my logs about corrupt or unreadable files, and no repeating messages etc.
  14. @barrycarey Did you ever get this issue worked out? I think I'm hitting the same issue over here (also running Rslsync on Windows and sync folders are on a mapped SMB drive from a NAS)