luckman212

Members
  • Content Count

    56
  • Joined

  • Last visited

Everything posted by luckman212

  1. Pretty quiet around here...too quiet
  2. What type of system(s) are these? Linux, macOS, Windows? Should be pretty easy to periodically run a script that compares the hash of a file to a previously known value and does something when it changes. If your system is Linux you can run the script every minute with cron etc. Here's a bash script I slapped together... you'll need the sha256sum binary, which you can get for just about any platform. See GNU coreutils or if you're on macOS and have Homebrew, `brew install coreutils`. This won't work for Windows but something similar can be done in PowerShell if needed. #!/usr/bin/env bash function calculateHash() { sha256sum "$srcfile" >"$oldhash" return } [ $# == 0 ] && { echo "usage: $0 <filename>"; exit; } srcfile="$1" fName="${srcfile##*/}" oldhash="/tmp/$fName.sha256sum" if [ ! -e "$oldhash" ]; then echo "creating hashfile for $fName" calculateHash exit fi if sha256sum -c --quiet "$oldhash"; then echo "hashes match, taking no action" else echo "file change detected! doing stuff..." # do stuff here # calculateHash fi
  3. I noticed today just by accident that one of my folders was stuck at 100% - sync was not completing for some reason. I had to enable debug mode and found a file that had a weird resource fork for whatever reason was causing the sync to hang. I deleted that file, restarted Sync on both ends and it was green again. So the question is: I would like to know if there is any way to get the sync status via command line / Terminal / bash? I would make a periodic script (cron, LaunchAgent on mac etc) to run and if the sync is not complete then maybe pop a notification, send an alert to Pushover etc. Bonus points if the command could output in an easy to parse format such as JSON. maybe e.g.: $ rslsync --status [foldername] { "status": [ { "name": "folder1", "peer_count": 4, "sync_complete": false, "unsynced_files": 2, "file_count": 4124, "total_bytes": 104230636, "last_change": 1559231815 }, { "name": "folder2", "peer_count": 3, "sync_complete": true, "unsynced_files": 0, "file_count": 192, "total_bytes": 5263463, "last_change": 1559215804 } ] } (In the above example, last_change represents a timestamp in Unix epoch time) I see there is (was?) an API but I am not sure if it's supported anymore and I checked the API docs and don't see any method there to query for sync status anyway. This would be so useful... please
  4. Hey guys I saw Rsl Connect is up to 2.7.x now. So I assume core sync engine is up to 2.7, which is also used by Rsl Sync Home /Pro. Is there going to be an updated client release soon? Thx
  5. Old thread but- what was the eventual solution for this? @kos13 Can IgnoreList function be enhanced to differentiate between files & folders? e.g. "Icon\r" might be safe to ignore as a file, but as a Folder name a user might want to include it... Regex would be very nice as well instead of just simple ? and * wildcards...
  6. 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 ?
  7. 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.
  8. 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?
  9. @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-
  10. @jimger Did you ever figure this out?
  11. 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!
  12. 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)?
  13. 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.
  14. 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.
  15. Anyone got any idea on this? Do I just have to try it and cross my fingers?
  16. 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.
  17. 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.
  18. 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.
  19. @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)
  20. 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...
  21. 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.
  22. 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?