Search the Community

Showing results for tags 'windows service'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Resilio Sync
    • Sync General Discussion
    • Sync Troubleshooting
    • Sync for NAS (Network Attached Storage)
    • Sync Stories
    • Developers
    • Feature Requests

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 5 results

  1. I have installed BitSync as a service on a Windows 2012R2 server. After a day of being online, the btsync process has some 20Gb of private bytes allocated and 7Gb of Working Set. If I don't restart the service, the system becomes unusable (as expected). Any ideas?
  2. I used 2.2 for a short time, then upgraded to 2.3 for the service feature. I did a complete uninstall of 2.2 before installing 2.3. I'm using Win7 and Win10. It seemed to install successfully, but when I try to open the BitTorrent Sync Service desktop shortcut, My browser opens, shows in the address bar, and displays: "This webpage is not available ERR_CONNECTION_REFUSED". I'm using Chrome on Win10. I tried pasting the address into IE on Win10, but similar result. Same result on a different PC with Win7 with Chrome and IE. I searched and found "Sync doesn't start when opening Link in browser", which says: Check registry keys: Your PC should have these two keys: 1. HKEY_CLASSES_ROOT\btsync\shell\open\command "C:\Program Files\BitTorrent Sync\BTSync.exe" /ADDURL "%1" (ot it'll be C:\Program Files (x86)\ path, depending on your PC specs) 2. HKEY_CLASSES_ROOT\btsync\DefaultIcon ""C:\Program Files\BitTorrent Sync\BTSync.exe" /ADDURL,0" My Win10 PC doesn't have btsync, but it does have btskey. I also tried ping, which was successful. There isn't a BitTorrent or Sync folder in "All Apps" nor in Program Files, so I don't know how to get the log files. Thanks, Keith
  3. When is the bittorrent sync service coming?
  4. I've been testing out a particular solution and it seems pretty legit, but any clarification or insight is appreciated. I have a source server that will be dropping small XML files into a BTSync folder. There are 5 destination machines with full access keys and each will sync to shared folder (UNC path) on 6th another machine. Another application will be consuming the XMLs from the UNC path, deleting them from the folder. The objectives: 1) the XMLs make it to the shared folder from the source 2) the XMLs are consumed only once by the XML pickup (i.e., they can sync multiple times, as long as it's not after the pickup) 3) the XMLs are archived from the source folder The 1st and 3rd are easy. I've not gotten the 2nd to fail, but this is where I could use clarification since it seems a few events could all occur here, and this is the most critical objective. Less relevant is that all devices have BTSync installed as a Windows service and the XMLs aren't modified. Also, if you're wondering about the 5 machines, don't ...the bottom line there is that a higher degree of redundancy is needed. The environment isn't that volatile, but the data is. The less latency the better, too, of course. So far, my tests have been positive, though I've only reproduced it in a smaller controlled VM environment of 1 source and 2 destinations (1 of which also hosts the shared drive). Also, folder_rescan_interval was set to 10s (from 600s). That said, my questions: 1) Assume a 50KB file. Race conditions to download that file by n machines? If the file exists in the destination, do other machines attempt to download it? If yes, are newer files discarded (file is unmodified) or do they overwrite the older file? Is the file locked during either process? 2) Assume a BTSync service is stopped before a file reaches the destination folder by another BTSync instance (i.e., it's not aware of the file in the folder). If I delete the file from the destination folder, but then start up the BTSync instance before the file deletion has occurred at the source, will the newly-started instance see the to-be-deleted file in the source and attempt to re-sync it? My tests indicate that it does not download the file, but how does it know not to? 3) Similar to the previous, assume a BTSync service is stopped after a file reaches the destination folder either by another BTSync instance or itself (i.e., it's aware of the file in the folder). Same tests results, but same questions (and perhaps the same answers). Again, all my tests look good. Any oversights? What events might violate objective #2? Will it scale? Thanks for any input. Let me know if I need to clarify anything.
  5. After a few false starts at getting BTSync to run as a Windows Service - here is what works for me. Trying various options (srvany, nssm etc) to get the BTSync executable to run as a service did not work for me. Although everything looked right (service running, task manager shows BTSync.exe running under administrator), synchronisation of folders between servers did not work. It worked fine when BTSync was run from a user desktop on each server. So, we tried another approach - configuring a scheduled job on each server to run when the server starts - this job to run BTSync under user administrator. (suggested in another post here). This works. With no-one logged in to the servers, folder synchronisation between them works fine. Downsides? If it is necessary to change anything - which requires use of the BTSync GUI, it is necessary to: log in to the server stop the running copy of BTSync.exe start it again from the desktop icon - to get the GUI make changes close the GUI reboot the server (to get the scheduled job to start BTSync again) << that bit is a bit unfortunate, as we dont want to reboot servers at all if we can avoid it. All in all though, this seems to be a way forward to use BTSync. Now we have 'automatic' folder synchronisation between unattended servers. This is exactly what we were looking for. Hope this is of use to others. p.s. Hopefully the BTSync development WILL produce a proper Windows Service version!