Helen

Administrators
  • Posts

    2,719
  • Joined

  • Last visited

Posts posted by Helen

  1. MacGyverDude,

     

    If the files have the same hash, BitTorrent Sync will just check them through and if files have't changed (still have the same hash) data will not re-transfer.

     

    As for conflicts, they are caused by different letter case in the filenames, and will appear if:

    1) On your NASes you have a Filename.txt and a filename.txt (which are two different files for Linux), they will be producing Conflicts on Windows (for which they are one file). 

    2) You had Filename.txt on NAS and filename.txt on Win, you will have a conflict on Win (same reason - Windows doesn't support different letter case). 

     

    So a solution here would be to make sure that all files have the same letter case when folders with files are added to BitTorrent Sync. 

    - Find the healthy file and make sure it's in the same letter case on all devices (!). 
    - Move this healthy file to another non-syncing directory. 
    - Remove those Conflict copies (not rename the files, but remove the files with conflicts in their names) from syncing folder. 
    - Put the healthy file to synced folder again.

     

    Please, do not rename filename.Conflict.txt files since it will cause Conflicts to multiply, and do not delete such files since it will remove the healthy file from other devices. 

  2. @Nicholas Chan,
     
    Do you have Sync launched on all machines all day long? This problem is know to us and it happens when some PCs are offline for a while, files are updated on them, and then they come back and delete the files which never existed on them from other peers. 
    This problem will be addressed in the next release, since Sync's behavior will be changed a bit. 

     

    On some of the computers, a certain set of files and folders will be regularly deleted at a random timing (ie. Computer A will have folders A, B and C and files D, E and F deleted) and only those files. The deleted files will always be found in .syncarchive of that particular computer.

     

    Files will be placed to .SyncArchive on PC1 if they were deleted/modified on some other PC2. In other words, if you see a file in Archive on Computer A, then they were initially deleted on some other computer and this deletion propagated to Computer A. You may see which of them initially deleted the file on tab History (for Windows), it will say "Peername removed file ....." Go to this peer and check time settings (yes, incorrect time adds to the problem) and see if a file is placed to Bin. 

     

    So far, please try not to touch the file on machines where BitTorrent Sync is off. 

  3. mosteo, 

     

     

    it is possible that these files would have been in the device but outside btsync folders. Would that count?

     

    don't think it would. Sync doesn't care about files outside its folders, unless these files ever passed through BitTorrent Sync. It will keep the sync_entry of a file by its name (for each sync folder), that's where this issue with the same names arises. 

     

    glad to hear that the problem hasn't appeared yet. If it does, first of all try renaming the files.

  4. mosteo,

     

    did you ever have files with exactly the same filenames, as of these files' names,  synced to your Android? These might be actually different files but having the same name. 

     

    The thing is that if you ever had a filename.mp3 (for example) file downloaded to your phone, then you delete it from the phone (and thus from PC) and then put some filename.mp3 to PC, it will be autodownloaded to the phone. This issue is known to us. 

     

    So try renaming the problematic files on PC and see if they will still be autodownloaded.

  5. @all,

     

    It's not compulsory that the folder which you try to add as read-only should be empty. You still can use the folder which already has files in it and add the RO secret to it.

     

    The message you see (This will not share the contents of "__folderName__" with everyone who has the key because it is a read-only secret) is just the warning that the files in this folder will not be uploaded to other peers so that you didn't expect to see them there, since it becomes a read-only folder, as jasondupreez correctly noticed - a one-way syncing. 

  6. Betogonza,

     

    Do you have Sync launched on both machines all day long? On which of then files are initially deleted? Here's how to determine it: If they are initially deleted on Windows, they will be moved to .SyncArchive on Mac and vice versa.  SyncArchive is a hidden folder in each sync folder and from there you may restore the deleted files, if you haven'd disabled it.

     

    Also, could you please describe your use case. Do you edit the files on a PC when Sync is turned off on it? Any details will be appreciated. 

  7. datroubler, 

     

    do you have a flag "Run as administrator" on shortcut properties on Compatibility tab? If yes, uncheck it. 

     

    Also, try going yo Control panel-> Power options -> Change what the power button does (on the left). In Shutdown settings section uncheck option "Turn on fast startup (recommended)". 

  8. Merk7,

     

    Please, provide more details: what are the OS of your devices, what types of files.

     

    Do I understand you right and uploading devices shows files in sync queue whereas the downloading device doesn't have those temp .!sync version of these files? 

    in this case I would suggest trying to re-add those files to sync folder on the uploading peer.

  9. colesear,

     

    Do you touch or open the files on Mac before starting Sync on it? If yes, then this is a known issue, since in this case Sync on Mac will consider its file to be the newest and thus sync it to other peer. I would recommend not touching the files on the device where Sync is off, if there is a newer version of this file on the remote peer.

     

    As for SyncArchive - did you disable it on Debian? Otherwise the replaced version would be placed there.

     

    As for not opening in LibreOffice, why exactly? Do you receive any error messages or somethings? 

     

    Keep logging enabled on both devices and when you see this problem again collect full debug logs from both (!) of peers and send them to syncapp@bittorrent.com. In the message put link to this topic. Thank you. 

  10. trevellyan

    Of course, the entire contents of both folders have not changed. 

     

    Do you mean on Macs and Linux or only on Macs? If files were changed (mtime updated) on Linux side, Macs will indicate the corresponding amount of files to be uploaded to it, but they will not be uploaded. 

     

    Were files in these two folders previously synced to Linux before you saw 'upload' on Macs' side? 

     

    Could you please collect full debug logs from one Mac and Linux and send them to syncapp@bittorrent.com. In the message put link to this topic and please, provide the requested details. Thank you. 

  11. pcjamesy,

     

    Yes, please, send this report to syncapp@bittorrent.com 

     

    Put link to this topic to your message, provide some more details (like, which folders you sync, where they are located/mounted, what types of files are there), which exactly Sync you have installed on Ubuntus and any other details about your setup, what Sync usually does before it crashes. Do they all three crash at the same time? 

     

    Also, please collect full debug logs from at least two of them (all three would be perfect) and attach them to your mail. Keep logging enabled all the time and collect the logs right after crash. 

     

    I will give you some additional instructions there. Thank you! 

  12. If I enable the relay server the problem usually goes away and I do not have to restart the sync app, So I don't know if there are any known problems with the "Search LAN" function as this problem rarely happens if I use predefined hosts.

     

    It looks like your multicast/broadcast packets (for LAN discovery) are either dropped or switched to unicasts. Sync sends broadcasts to port 3838 for LAN discovery. 

     

    As for Android seeing only wired peers, your LAN settings - are they applied to both wired and wireless? Could you please elaborate how your network is configured "to pass all traffic through the LAN interface"? Which is this interface? 

  13. 4195c50c-11b8,

     

    yes, thank you! now it's much clearer and I see that I got it right at first. Yes, in this case Android DCIM will be paired with Linux share_phone, so it'll be DCIM/*** <-> share_phone/*** setup. 

     

    At present only one such pair is allowed by application. We have similar feature requests allowing to store multiple folders from different devices in one folder on local device. We will consider them for future releases. Thank you! 

  14. psla,

     

    What is the actual IP and listening port of your Linux? You tell your win to connect to 192.168.5.60:8888 (please, note that 8888 - is not the listening port of Sync, it's the WebUI port), and it fails, because it seems to be not the linux node: 
     

    here is the log file on win32 btsync client before connection of vpn

     

    [2014-08-01 15:56:06] ping 192.168.5.20:32982
    [2014-08-01 15:56:06] Failed to open tunnel to 192.168.5.60:49575:TCP
    [2014-08-01 15:56:06] Failed to open tunnel to 192.168.5.20:32982:TCP
    [2014-08-01 15:56:07] Lost peer for folder \\?\C:\Users\Mathew\Documents
    [2014-08-01 15:56:07] Lost peer for folder \\?\C:\Users\Mathew\Documents

    here it sends pings to all nodes in the network (these are sent during first 10 seconds after Sync is loaded), including 192.168.5.20:32982. Fails. 

     

    here is log after connection of vpn

    [2014-08-01 15:59:08] Send ping to peer (0000000000000000000000000000000000000000) for 
    [2014-08-01 15:59:08] ping 192.168.5.60:8888

    when network is available, it pings the wrong IP:port. again - fails. 

     

     

    Ithen if i restart win32 btsync

     
    [2014-08-01 16:12:41] Got ping (broadcast: 0) from peer 192.168.5.20:32982 (100F6E6A88A15EFCB11BF701357995E92563CE85) for share 
    [2014-08-01 16:12:41] Incoming connection from 192.168.5.20:32982
    [2014-08-01 16:12:41] Incoming connection from 192.168.5.20:2098
    [2014-08-01 16:12:41] Got tunnel to 192.168.5.20:32982:TCP, total tunnels: 1
    [2014-08-01 16:12:41] Best tunnel now is 192.168.5.20:32982:TCP
    [2014-08-01 16:12:41] Found peer for folder \\?\C:\Users\Mathew\Documents\Market Analyst 7 100F6E6A88A15EFCB11BF701357995E92563CE85 192.168.5.20:32982 direct:1 transport:1
    [2014-08-01 16:12:41] Failed to open tunnel to 192.168.5.60:49575:TCP

    now when the network is available and Sync is reloaded, it will again send pings (again those 10 seconds) to all nodes and discover Linux (I suppose it's Linux) on192.168.5.20:32982 address. 

     

    So, in predefined hosts on win32, please, put 192.168.5.20:32982, or please, recheck the correct  IP and listening port of your Linux peer. Listening port can be found in Sync settings. Port 8888 that you used is not the one you need to "predefine".

  15. stanha,

     

    1) RO nodes can upload files *if they were not updated on them*. in other words, they just "pass the files over" to other peers. So if a RO peer gets a file from a RW peer and there are some other peers that need this file as well, RO peer will send the file. 

     

    2,3) rewriting the version and restoring the deleted file is related to RW peer being actually behind in time.

    Sorry, I'm not sure I understand your setup:

    So, while the r/w node was syncing with the node that had an out of range timediff error, the updated version of file that was edited on the r/w node was uploaded to the r/o nodes.

    Then, after I finished syncing with the node with timediff error, I existed BTSync, reset the box's clock to correct time and restarted BTSync again.

    What happened is
    2) The r/w node got updated with the file from the r/o node which overrode actually newer version of the file with the older one from the r/o node. 
     

    If the updated version was uploaded to RO peer, which "older" version of the file then replaced the the updated version? 

  16. 4195c50c-11b8,

     

    Oh yeah, sure, you may always add the folder with camera photos as a regular sync folder to connect it to an already existing folder on your Linux. However mind those read-only/full-access secrets. If you connect Android to Linux with a RO secret, Android will not upload photos. If you connect it with FA secret, be careful deleting /editing of them on either side, since these changes will be propagated. 

     

     

     however this places all the camera files in the root folder, while I want them in a subfolder.

     

    not sure I understand this 100%.

    The files and subfolders within the sync folder are mirrored, i.e.: 

    On android you have DCIM/2014/photoname.jpg and you add DCIM to BitTorrent Sync, connect it to a "Photos" folder on Linux. So on Linux inside "Photos" folder you will have "2014" subfolder with "photoname.jpg" in it. 

    Similarly, if you have DCIM/photoname2.jpg on Android you will have Photos/photoname2.jpg (in the root) on Linux. 

  17. @sinmantky, @basovink,

     

    Would love to help, could you please provide the following information: 

     

    1) Share usage scenario (which data is synced? Any specific app is changing data in sync folders?)

    2) Is there a possibility to turn on full debug logging and send them to syncapp@bittorrent.com to catch the issue so we can see how (and hopefully why) it happens in the logs? If yes, we'll need a filename / folder name that was mistakingly restored.