jammin

New Members
 View Profile  See their activity

  • Posts

    18

  • Joined

  • Last visited

 Content Type 

Posts posted by jammin

  5. All folders disconnected

    in Sync Troubleshooting

    Posted

    1 minute ago, Helen said:

    @jammin

    We got your ticket, replied. 

    In Sync v2.8 IgnoreList is preserved if a folder gets disconnected. 

    Thanks, am now discussing with support and will post the result back here.  

    Yes after I posted I went back and started re-connecting folders and noticed the ignoreList was still there.  Excellent!

     

  9. All folders disconnected

    in Sync Troubleshooting

    Posted · Edited by jammin

    I just had this problem on two of my machines.  Went to bed last night and everything was OK.  Woke up this morning to all folders being disconnected on 2 out of 3 of my machines.

    On one of the two  laptop I see this in the log (you can see the time difference where nothing happened because everything has become disconnected) 

    [2016-08-17 22:34:48] ScheduledTask: "ConnectMorePeers" invoked: immediately, reason:SyncFolder::Start
[2016-08-17 22:34:48] SF[C44B] [5B89]: Won't connect files, no valid addr
[2016-08-17 22:34:48] SF[C44B] [D95C]: Won't connect files, no valid addr
[2016-08-17 22:34:48] SF[C44B] [32C6]: Won't connect files, no valid addr
[2016-08-17 22:34:48] SF[C44B] [8920]: Won't connect files, no valid addr
[2016-08-17 22:34:48] ScheduledTask: "ConnectMorePeers" invoked: immediately, reason:SyncFolder::Start
[2016-08-17 22:34:48] SF[C44B] [5B89]: State sync finished
[2016-08-17 22:34:48] SyncReq[0x00000275360ad090][None-TCP] [0000]: cancel 360AD090 - outgoing merge
[2016-08-17 22:34:49] SyncReq[0x00000275360ad090][None-TCP] [0000]: destroing 360AD090 cbcnt:5 - outgoing merge
[2016-08-17 22:34:49] Sending broadcast ping for 16 shares
[2016-08-18 11:02:26] Change network from WIRED_NETWORK to NO_NETWORK
[2016-08-18 11:02:28] Change network from NO_NETWORK to WIRED_NETWORK
[2016-08-18 11:02:28] failed to set IP_ADD_MEMBERSHIP for 169.254.241.187:0: -1
[2016-08-18 11:02:28] failed to set IP_ADD_MEMBERSHIP for 169.254.241.158:0: -1
[2016-08-18 11:02:28] setup socket 2388 for local peer discovery for 192.168.55.17: success
[2016-08-18 11:02:28] setup socket 4020 for local peer discovery for 127.0.0.1: success
[2016-08-18 11:02:28] PLC[0x000002751536abf0] binding on 0.0.0.0:12973
[2016-08-18 11:02:28] Socket[0x000002751536abf0][4048] bound listening socket 4048 to IP 0.0.0.0:12973
[2016-08-18 11:02:28] UDP: bound listening socket 920 to IP 0.0.0.0:12973
[2016-08-18 11:02:28] SyncSocket[0x00000275360adf90]: an error has occurred - code: 10051, message: "A socket operation was attempted to an unreachable network. "
[2016-08-18 11:02:28] Closing uTP tracker connection to 52.0.102.230:3000. Error 10051
[2016-08-18 11:02:28] Closing TCP tracker connection to 52.0.102.230:3000. Error 10051
[2016-08-18 11:02:28] Closing uTP tracker connection to 52.1.40.103:3000. Error 10051
[2016-08-18 11:02:28] Closing TCP tracker connection to 52.1.40.103:3000. Error 10051
[2016-08-18 11:02:28] Closing uTP tracker connection to 52.1.1.135:3000. Error 10051
[2016-08-18 11:02:28] Closing TCP tracker connection to 52.1.1.135:3000. Error 10051

    The other machine didn't have debug logging on so has nothing of use in the log.

    I'm guessing maybe some kind of transient network problem caused it, but that really shouldn't happen.  Recreating my ignore lists and reconnecting all the folders takes many hours and I just can't trust the system if it's going to be so fragile.

    edit: I have submitted a support ticket with more of the log.

  12. Network Shares / Mapped Drives

    in Sync Troubleshooting

    Posted · Edited by jammin

    Even if you use a UNC path, I assume Sync wouldn't get notification of file system changes on a network drive.   Changes would only be synced on the scheduled reindex, not as they happen.  

    This may be a pretty subpar experience depending on your use.

     

     

  13. Illegal characters replaced - ???.bit:com.bittorrent.sync was renamed using supported symbols

    in Sync Troubleshooting

    Posted · Edited by jammin

    8 hours ago, Helen said:

    Thanks for the details. Managed to reproduce it with FlexRaid. Actually you're the second person ever with this problem and the first one with it on FLexRaid :) Frankly speaking I don't know details of how that software works, need to read documentation, so adding this case to the fix may take time.

    Awesome, I didn't expect you to go to that much trouble, and greatly appreciate it!  What was the other person who experienced this problem running?

    I've been in touch with FlexRaid support and they are puzzled by it.  Please let me know if you think it's something they need to address with as much info as possible.

    8 hours ago, Helen said:

    So far adding *com.bittorrent.sync to IgnoreList on this window (and other Windows with same problem) helps. Sorry, you'll need to re-add the folders, cause the streams already synced there won't un-sync. And with the stream in Ignore you will not see process bar on a bts in Windows Explorer. 

    Thanks for the workaround.  The problem seems to sort itself out without the IgnoreList entry - the errant file gets synced around and then deleted - so I think I'll leave it and wait hopefully for a fix.  

     

  14. Illegal characters replaced - ???.bit:com.bittorrent.sync was renamed using supported symbols

    in Sync Troubleshooting

    Posted · Edited by jammin

    11 hours ago, Helen said:

    :com.bittorrent.sync is not extension, it's a file stream. this is how Windows keeps them filename:<stream_name>, the streamname being invisible . BTW this is why Windows doesn't allow colon in filename - by colon it recognizes stream. 

    I suspect that your sync share is actually physically located on a Linux (which does not support streams) and mapped to your Windows over smb, or this windows is a Virtual machine on a linux host sharing a host's mapped folder? ....or a similar setup? but the key point here is that when a file arrives at Windows through Sync, NTFS saves it correctly (filename:<stream>), then this file is passed over to the linux for which it looks just like a regular filename: file:stream, which returned back to PC. 

    This was worked around longs ago, so perhaps your case is something yet undiscovered? any details about your setup? 

    Thanks Helen.  There are no linux boxes involved, only Windows 10 machines and a couple of mobile devices (which I have disconnected for now).

    However one of the windows machines has it's folder on a FlexRaid storage array (a software RAID solution) which creates a virtual drive out of a pool of hard drives. I wonder if that has something to do with it, since it's essentially emulating the NTFS file system - perhaps it doesn't have support for streams.  I'll post on their forums and see if I can find out anything.

    I must admit I was curious why searching didn't come up with a single relevant result, as I guess I'm the only person using these two particular pieces of software together.

     

  15. Illegal characters replaced - ???.bit:com.bittorrent.sync was renamed using supported symbols

    in Sync Troubleshooting

    Posted

    1 hour ago, GreatMarko said:

    The issue is due to the fact that a colon character (:) is not a valid character in file names under Windows operating systems. Therefore, if you're syncing a file from another OS where : characters are allowed in filenames, to a Windows system, the : character will be substituted for an underscore.

    To avoid this, ensure that the filenames of the files your syncing contain characters which are legal on all the operating systems you're syncing between.

    Thanks for the reply.  I understand that colon is an illegal character on windows, and my files do not have a colon character in their names.  In the above example, my file is DSC06609.ARW and Sync has added the ";bts:com.bittorrent.sync" part itself when creating some kind of temporary file, which it then tries to sync.

     

     

  16. Illegal characters replaced - ???.bit:com.bittorrent.sync was renamed using supported symbols

    in Sync Troubleshooting

    Posted · Edited by jammin

    I have a rather annoying problem.  Sync usually creates .bts files on the new device as placeholders for the downloading file.  But in my case it's creating files with a ":com.bittorrent.sync" extension which it then attempts to sync to other devices, resulting in the message: 

    Illegal characters replaced
???.bts:com.bittorrent.sync was renamed using supported symbols

    sync.jpg

    The file then gets removed (from all devices) once the actual file has completed syncing.  Ultimately it seems to sort itself out in the end but creates a lot of annoying error messages and unneccessary chatter in the process.  I also end up with a lot of deleted placeholders in my "Archive" folder (see sync2.jpg).

    sync2.jpg

    The problem has occurred with several different folders.   All devices are running Sync Pro 2.3.7, two of them installed as a service and one running as a regular app.  There's also an android device and an iOS device, both with the folder connected in "selective" mode.

    Any ideas what could be causing it?  I am mostly loving sync and this is really my only major complaint.

    edit: originally I stated that it only happened on newly added folders, but this is not the case.  It's also happening on syncing folders that were already connected.

    edit2: originally I was using Sync Pro 2.3.6 but I have since updated to 2.3.7 and am still experiencing the issue.

  17. Identical files are transferring

    in Sync Troubleshooting

    Posted

    Thanks for the reply.  Initially I did hook it up to the wrong folder.  Easy to do when it automatically appends the folder name (so I chose D:\Videos and it changes it to D:\Videos\Videos)!  Won't make that mistake again.

    After rectifying that, it appeared like it was transferring everything again, but I guess it was just transferring hashes.  It took about 24 hrs on a very slow internet connection to resync 3.8TB (almost 10,000 files) so I guess that's not bad!

     

  18. Identical files are transferring

    in Sync Troubleshooting

    Posted

    Recently I had a problem where all of my folders on both of my windows machines running BitTorrent Sync Service 2.3.6 became disconnected.  The reasons for that require more investigation, but my immediate problem is that when I reconnected them, it reindexed the folders and the started to transfer the entire contents of one machine to the other, even though the identical files already existed with the same date & time.

    Is there any way to stop this?  I initially synced the machines when they were on the same LAN, and to fully resync again over WAN would take months!