sergey@bt

Employees
 View Profile  See their activity

  • Posts

    86

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Everything posted by sergey@bt

  1. sergey@bt
    It should be fixed in version 1.1.33.
  2. sergey@bt
    Can you please send us Sync debug log both from sending and receiving computers? Here are details how to collect logs:
  3. sergey@bt
    Could you please try to start Sync with empty settings? On Mac settings are stored in ~/Library/Application Support/BitTorrent Sync. Just rename this folder into any other name and try to start Sync again.
  4. sergey@bt
    Please include into your report full debug log from both machines, since error could happen either on sending or receiving side.
  5. sergey@bt
    There was a bug in 1.1.26 when frequently updated files could be overwritten with old version from another computer. Please upgrade to 1.1.30. Make sure your folders are synced before doing upgrade. If you still see this issue with 1.1.30, please send us debug logs so we can analyze and fix it.
  6. sergey@bt
    Thanks for details. Indeed Sync may report incorrect timestamp error for files which it's not able to access. We will correct it.
  7. sergey@bt
    Currently Sync skips files with modification time set to 0 (Jan 1, 1970). Try to update timestamp (open & save file), it should fix this error.
  8. sergey@bt
    This message means file has been modified in read-only folder. Currently Sync does not overwrite such files.
  9. sergey@bt
    In OSX you have to use both SO_REUSEADDR and SO_REUSEPORT. BTSync sets these flags for SSDP listen socket. But if some other app doesn't use SO_REUSEPORT (since SO_REUSEADDR is enough in Linux), it will fail to bind to the same port.
  10. sergey@bt
    The problem is in second timestamp (0), which is file modification date. Please find files with modification time set to 0 and fix them (touch), it should resolve the issue. The date in log is correct, month is numerated from 0 to 11, we will fix it to avoid confusion.
  11. sergey@bt
    Can you please send us debug log from both computers?
  12. sergey@bt
    "Ping" packets should not cause 100% CPU. Do you see anything it log besides ping? Can you please create process sample with Activity Monitor and send it to us? Also if you saw crash with 1.1.15, send it as well.
  13. sergey@bt
    This error means BTSync is not able to find or read .SyncID file in shared folders. Can you check manually if this file really exists? .SyncID is hidden file on Windows. So if you look for it in Explorer, you need to configure it to show hidden files first.
  14. sergey@bt
    How many files do you have in shared folders?
  15. sergey@bt
    BTSync itself does not require root privileges. Make sure all files in shared folder and in .sync folder are writable for your system account.
  16. sergey@bt
    The only option for now is to re-add shared folder on read only machine.
  17. sergey@bt
    Can you please send us BTSync process sample from either of your Macs? 20-40% is not normal when there are no active transfers.
  18. sergey@bt
    Try to disable DHT for all shared folders and restart the client.
  19. sergey@bt
    If you see the same issue with 1.0.132 (i.e. newly added files and folders are moved to .SyncTrash), could you please send us debug logs from your machines? Here are instructions how to collect it: Log message started with Torrent... is just a status message. It does not mean any error.
  20. sergey@bt
    This is in our bug list. We are planning to fix it soon.
  21. sergey@bt
    Did it start to transfer your VHD file? Sync should transfer only changed blocks. But before it starts the transfer, it does not know how much it should download/upload and UI shows full file size.
  22. sergey@bt
    Do you have debug log enabled? You can check it by looking for file debug.txt near sync.log. If you see debug.txt, try to delete it. Size is normal for debug log.
  23. sergey@bt
    All computers are independent for BTSync. B and C will continue to sync without A.
  24. sergey@bt
    Files which are not removed or modified, will continue to be downloaded and seeded.
  25. sergey@bt
    If you still see the case when sync gets stuck, can you please install latest version 1.0.132 and send us debug log from both computers? Here are instructions how to collect log: