luckman212

Members
  • Content Count

    50
  • Joined

  • Last visited

Everything posted by luckman212

  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: https://help.resilio.com/hc/en-us/articles/206664730 If you're using a NAS (Synology, QNAP etc) then try this: https://help.resilio.com/hc/en-us/articles/208800446-How-to-collect-logs-on-NAS-manually-
  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)
  15. Is there a way to tell when Rslsync is in this "scanning" phase? I just posted what seems to be the same issue earlier today. There doesn't seem to be anything in the logs or any status shown in the UI when scanning is going on...
  16. I have a 2-core VM running Rslsync 2.6.2-1330 on Windows Server 2012. Sync is set up to run as a Windows service. Not sure when it started, but I have noticed now that Resilio Sync.exe is constantly keeping the CPU at 25-50% usage. I am talking about endlessly... for 24 hrs+. I have enabled debug logging and looked at the log file, there's lots of stuff but not really any errors, warnings or failure messages. Sync is working fine, etc. Just that the CPU is being heavily hit and not sure why (this is even when no filesystem changes are occurring). I have tried the usual stuff— restarting the machine, giving it more memory (it has 16GB allocated now, and only ~3GB in use), and stopping/starting the sync service. Is there any way to debug this further to figure out what is causing the CPU load? I tried running SysInternals Process Explorer and viewing the threads but without the debug symbol files for rslsync I can't really "see" what the threads are so busy doing.
  17. I had a situation where someone moved the invisible .sync folder at the top level of a synced folder. This caused major havoc as would be expected. My question is: can I lock down this folder so it is only readable/writable by the "rslsync" user? Any consequences of that, other than a user not being able to browse into the Archive?
  18. I have a 2-node Sync Home setup - both sides running 2.6.2 This was not a date/time mismatch or old vs. new file, it was a few folders were simply not synced (folders existed on "A" but not at all on "B"). Similarly, there were a couple of files on "B" that did not exist on "A". Sync UI reported 100% in sync on both sides, no errors or warnings in the activity tab in the UI. Nothing special about the folders as far as filenames/permissions/pathnames too long etc. Basically, I have no idea why these files weren't picked up. I had to manually copy the files from A to B and vice versa. How can I troubleshoot this? Is there any way to tell Sync to re-check its database, rescan the folders etc?
  19. Answering my own question: Yes 2.6.2 hit the app store today... thanks
  20. Trying the beta build (2.6.10006) now - will keep posted if the problem returns.
  21. @Gane O'dwyer Thanks. I just opened support ticket #85314. Will keep this thread updated as well.
  22. reference post: https://forum.resilio.com/topic/34371-how-to-remove-device-in-my-devices/?do=findComment&comment=101225 Regarding this (old) issue. I'm running Sync 2.6.0 on a few devices (Mac Mini, MacBook, iOS, Synology NAS). Every day or so, I am finding in Settings > Identity that there are duplicate devices being created. E.g. "macbook" will show up 4 or 5 times. When I see this, I can shut down Sync, go into the Sync storage folder e.g. $HOME/Library/Application Support/Resilio Sync/.SyncUserXXXXXXXX/ and examine the info.dat files to see which duplicate identity belongs to which device. Then I can throw away all the duplicates, keeping only the most recent identity (1 for each device). But this is very tedious to do, and I don't understand why it's happening. I think it may have something to do with connecting to VPNs - which I do a lot from my macbook, maybe Sync is seeing the network change and somehow (mis)detecting it as a whole new device? Not sure. I have already tried a "full reset" - unlinking all devices, deleting Sync and then re-installing/re-linking folders. This didn't work, and I am still finding that the dupes are appearing regularly. This is mostly an annoyance/cosmetic issue since the actual Sync functionality is working normally. But I'd like to see it get fixed, as it apparently has been a known issue for at least 3 years... edit: before someone suggests it, I've already gone into power user preferences and set peer_expiration_days to 0. All that does is help keep the peer list down, so instead of saying "peers online: 2 of 9" it will say "2 of 2" - but it does nothing to prevent or remove the zombie identities.