If You Have Sync Issue


kos13

Recommended Posts

It seems that some file are not fully synched between peers.

I have three peers and btsync says that one dir it's not fully synchronized with one of the peer.

There are 11,5 giga of file and the UI says that needs to sync 20Mb, but they never synched.

 

I see in the log some info about one of this file

 

[2014-07-22 23:41:01] Torrent \\?\H:\BTSYNCH\PERSONALE\ISO\OracleSOA\oel6-64bit-soasuite-11gr1-ps6-otn.ova.7z.001 status:137 error:<NULL> meta:1 conns:1 io:0

 

Same things happen in other dir 13.4 GB missing to be synchronized.

 

Any help?

Link to comment
Share on other sites

Sorry previous post was a mistake : the folder  that wasn't synchronized was on a external driver not attached :(.

May be in the tab "dispositivi" (Italian may be in English is devices) the folder that is not reacheble (because of the external usb disk not conneccted for example) have to be highlighetd in some way, other way it seems it's not actually synchronized.
 

Link to comment
Share on other sites

  • 3 weeks later...
  • 2 weeks later...

I upgraded to to Android Sync version 1.4.36 on my Samsung GT-P6200 (tablet 7 plus), running Android 3.2.

 

The sync interface keeps jumping back to the previous screen, or right out of the app.  Using the interface is now literally impossible.  This is not a problem with any other apps I use.

 

Could you please make the earlier 1.3 version available as a "classic" version.  

Link to comment
Share on other sites

Hi, 

I've already posted at the topic about WD MyCloud FW update problem but it seems no BT people is following it. (http://forum.bittorrent.com/topic/30993-rebuild-required-for-wd-mycloud-fw-4/)

 

It appears that last firmware version is making the btsync process to be killed as soon as it tries to start.

 

I've already tried to get the dump file according to instructions given on the same topic but no file get generated.

 

Please help!

Link to comment
Share on other sites

  • 4 weeks later...

Either long pathname or ignorelist bug

I have 8 peers, all Win 7 x64 or 8.1 x64.  Many files have pathnames longer than 260 characters.  Two days ago, I noticed that one folder had a duplicate with a truncated name:

 

e.g. "Share/Current Work/..." in same folder as "Share/CURREN~1/..."

 

The truncated folder only had a couple files in it, and many empty subfolders.  The regular folder was still present and all of its data seemingly intact.  I resolved this problem in  BTSync 1.3 by modifying the .syncignore files to include the following:

*~*~**~

Accordingly, I modified one workstation's ignorelist so that any file or folder with a tilda would be ignored.  This is where I think I encountered the bug:  The files inside the truncated folder and the regular folder disappeared on all peers.  Immediately, I changed the ignorelist back to its default, restarted all workstations, and began the tedious process of restoring data.  This took approximately 5 hours for tens of thousands of files. 

 

Finally, when all the files were back to their original state (at 3 a.m.), the data loss occurred again.  Originally, the loss occurred (I think) because I modified the ignorelist to include any file with a tilda, but now, the ignorelist was back to default.  I don't know what caused the data loss the second time.

 

Finally, to restore the data again, I completely uninstalled BitTorrent Sync from every machine, restarted them all, then reinstalled BitTorrent Sync and started from scratch.  Luckily I had a backup this time, but I was up all night.  

 

What I think:

I think there is some conflict with BTSync and long pathnames.  This happened in 1.3 also, where truncated/shortened folders (with a tilda) would appear next to the normal folders.  Additionally, I think BTSync must rely on truncated names because when I edited ignorelist to ignore all files with tildas, normal folders also disappeared.  

 

However, I have no clue what caused the data loss the second time.  Bittorrent Sync was running with default settings (no changes to ignorelist), and all on version 1.4.82. I have no other software that would interfere. 

 

Please let me know if you need additional information.  I don't have logs, unfortunately, as this happened out of the blue.

Link to comment
Share on other sites

I've turned on debugging and I am not able to debug further. Is there a page describing how to be able to get more information as to what is going on? I can't get my peers to detect each other, yet I can connect between them using other apps. I can't really find anything useful in the debug logs to find out why I'm having this problem. I'm using the latest 1.4.83 on Win7-x64 with a ubuntu-14.04-server-x64.

 

Link to comment
Share on other sites

  • 2 weeks later...
  • 1 month later...

Hi there, I’m having an issue whereby newer copies of a file are being overwritten by older ones, every time I try to modify the file.

 

I’m trying to gather debug logs. The syncing machines are 1 Mac and 1 Linux.

 

On the Linux machine, I add a 4-character file called ‘.sync/debug.txt’ (inside the synced directory) containing the characters “FFFF”. However, no “sync.log” file is generated in that directory (and nothing in “/var/log/” that I can see either). I tried restarting the btsync daemon, but still it has not picked up this file.

 

On the Mac, I hold down shift when clicking the BitTorrent Sync icon in the menubar, but I only see the normal options; no option to switch on logging. However, there is a file “~/Library/Application Support/BitTorrent Sync/sync.log” already been generated. Has the menu option been removed? Does it always log?

 

I’m running v1.4.103 on both machines.

 

Thanks

Link to comment
Share on other sites

  • 3 weeks later...

Hi Guys,
 
I am battling with a user who continuously gets locked files and then for some reason his BtSync is out of sync to the other users.
 
I have saved the logs for his machine, and will attach two pictures to try help.
 
I have disconnected his Btsync and re-added and after a while the application just says out of sync.

 

/home/jude/Desktop/sync.log.zip

/home/jude/Desktop/Btsync2.png
/home/jude/Desktop/Btsync1.png
 
Not sure how to add attachments here
Link to comment
Share on other sites

@JudeMBitCo

Send your attachments to syncapp@bittorrent.com - we'll take a look what happens there. Make sure that you send logs not only from the "out-of-sync" PC, but also from some other computer to compare. Collect logs at the same time (as logs containing different timespan are useless).

 

@andrew554

Check if the file that constantly overwrites others has future modification time? If this is not your case - please collect debug logs from all your peers.

Link to comment
Share on other sites

I was having "Out of Sync" issue with one of my shares, it was working fine until a couple of days ago. I only have one R/W and one encrypted node and I just added some new files to R/W node like I always did. When I checked the logs I noticed the lines below keep repeating in the log of R/W node.

 

[20141214 05:32:53.017] SF[452E] [141F]: Going to sync state with peer [peer ip]:62981[20141214 05:32:53.017] ScheduledTask:SyncState invoked:immediately reason:FinishStateSync - sync not completed[20141214 05:32:53.097] MC[452E] [141F]: generating intial request with root 5FC72698660EA36CE07200AEBC64FCDCCB9DDBDA[20141214 05:32:53.215] API: --> getsyncfolders(discovery=1&t=1418563973210)[20141214 05:32:53.283] SF[452E] [141F]: Received request "id"[20141214 05:32:53.283] SF[452E] [141F]: Got id message from peer [peer name] (102799A00B7C0CCF2109A7B15031C0FB72B7141F) 1.4.103[20141214 05:32:53.283] SF[452E] [141F]: Received request "peers"[20141214 05:32:53.283] SF[452E] [141F]: Received request "root"[20141214 05:32:53.283] MC[452E] [141F]: processing root message, remote hash 0C835821E09CBD93F42AF04B32407BF623EB9B4A, timediff: 0[20141214 05:32:53.283] MC[452E] [141F]: requesting nodes for root[20141214 05:32:53.714] SF[452E] [141F]: Received request "nodes"[20141214 05:32:53.714] MC[452E] [141F]: processing nodes message for /[20141214 05:32:53.714] MC[452E] [141F]: will request nodes for /GTEYJ6PCKK34PTZ75ZVKXTE5WR6BARDX2QOYDQY[20141214 05:32:53.714] MC[452E] [141F]: sending get_nodes message[20141214 05:32:53.922] SF[452E] [141F]: Received request "nodes"[20141214 05:32:53.922] MC[452E] [141F]: processing nodes message for /GTEYJ6PCKK34PTZ75ZVKXTE5WR6BARDX2QOYDQY[20141214 05:32:53.922] MC[452E] [141F]: will request files for /GTEYJ6PCKK34PTZ75ZVKXTE5WR6BARDX2QOYDQY[20141214 05:32:53.922] MC[452E] [141F]: will request nodes for /GTEYJ6PCKK34PTZ75ZVKXTE5WR6BARDX2QOYDQY/4UKXRMQGSKUQRXEJXBQ7XCMTTUGFNGCWF2KVKN4SRRJBQRPOVXTQ[20141214 05:32:53.922] MC[452E] [141F]: will request nodes for /GTEYJ6PCKK34PTZ75ZVKXTE5WR6BARDX2QOYDQY/5QUU3CMTLUIKTC2NRAHZXXDKIRP7TIUMNDNEEEUGLGSTFXQ3EF5A---- REDACTED ----[20141214 05:33:01.270] MC[452E] [141F]: will send file /GTEYJ6PCKK34PTZ75ZVKXTE5WR6BARDX2QOYDQY/RKQEVBVXUV42L3YIS63EVOXG34P6IM5WNDDT4WGR2YMKA3KMFSZQ/JUV3AF6VA24XZHRGNV6FVMDWAA/O6I37AKQ72ETFUCAR6WI4FGPWU[20141214 05:33:01.271] MC[452E] [141F]: Local file [folder1]/[folder2]/[folder3]/[folder4] is newer than remote t:1418539030/1409580159 ot:1019765/737 o:10DB722EA4A96E5B2FDCE0308490D2CC335D453B/10DB722EA4A96E5B2FDCE0308490D2CC335D453B[20141214 05:33:01.271] MC[452E] [141F]: will send file /GTEYJ6PCKK34PTZ75ZVKXTE5WR6BARDX2QOYDQY/T74PJI2SINIPQHS3J62QSC5FXFGDDIV7PWH3NLTMUTZZICQ7KSZQ/RN4TQJDFU2OCFCNXTYVYJWXJ4A/NQOAJBXTAFXEW2LDZVRZUDQXDU[20141214 05:33:01.271] MC[452E] [141F]: Local file [folder1]/[folder5]/[folder6]/[folder7] is newer than remote t:1418364710/1409580129 ot:1019415/441 o:10DB722EA4A96E5B2FDCE0308490D2CC335D453B/10DB722EA4A96E5B2FDCE0308490D2CC335D453B[20141214 05:33:01.271] MC[452E] [141F]: will send file /GTEYJ6PCKK34PTZ75ZVKXTE5WR6BARDX2QOYDQY/UQLH65NIA6PYVEV3YSO5DBF227IQRDB4TV4FGX6GFGOXITDTIQ4Q/BOCZ27GR6WGSPB7EWBIQC3KMMQ/TXF75XD2R5BWDYXDRUEQ4IG5BU[20141214 05:33:01.271] MC[452E] [141F]: Local file [folder1]/[folder5]/[folder6]/[folder7]/[folder8] is newer than remote t:1418364710/1409580129 ot:1019414/456 o:10DB722EA4A96E5B2FDCE0308490D2CC335D453B/10DB722EA4A96E5B2FDCE0308490D2CC335D453B[20141214 05:33:01.271] MC[452E] [141F]: will send file /GTEYJ6PCKK34PTZ75ZVKXTE5WR6BARDX2QOYDQY/UQLH65NIA6PYVEV3YSO5DBF227IQRDB4TV4FGX6GFGOXITDTIQ4Q/BOCZ27GR6WGSPB7EWBIQC3KMMQ/TXF75XD2R5BWDYXDRUEQ4IG5BU/DCADFUS47MILQIS5PFEDPBQW3E[20141214 05:33:01.271] MC[452E] [141F]: Local file [folder1]/[folder5]/[folder6]/[folder7]/[folder8]/[folder9] is newer than remote t:1418364643/1409580129 ot:1019399/474 o:10DB722EA4A96E5B2FDCE0308490D2CC335D453B/10DB722EA4A96E5B2FDCE0308490D2CC335D453B[20141214 05:33:01.271] MC[452E] [141F]: will send file /GTEYJ6PCKK34PTZ75ZVKXTE5WR6BARDX2QOYDQY/UQLH65NIA6PYVEV3YSO5DBF227IQRDB4TV4FGX6GFGOXITDTIQ4Q/BOCZ27GR6WGSPB7EWBIQC3KMMQ/TXF75XD2R5BWDYXDRUEQ4IG5BU/DCADFUS47MILQIS5PFEDPBQW3E/2JRDCERIMWLCRUJGV2WFPHKHZM[20141214 05:33:01.271] MC[452E] [141F]: Local file [folder1]/[folder5]/[folder6]/[folder7]/[folder8]/[folder10] is newer than remote t:1418364710/1409213823 ot:1019413/457 o:10DB722EA4A96E5B2FDCE0308490D2CC335D453B/10DB722EA4A96E5B2FDCE0308490D2CC335D453B[20141214 05:33:01.271] MC[452E] [141F]: will send file /GTEYJ6PCKK34PTZ75ZVKXTE5WR6BARDX2QOYDQY/UQLH65NIA6PYVEV3YSO5DBF227IQRDB4TV4FGX6GFGOXITDTIQ4Q/BOCZ27GR6WGSPB7EWBIQC3KMMQ/TXF75XD2R5BWDYXDRUEQ4IG5BU/DCADFUS47MILQIS5PFEDPBQW3E/G5MDB74BO443LXDKYWE2V7EVWY[20141214 05:33:01.271] MC[452E] [141F]: Local file [folder1]/[folder5]/[folder6]/[folder7]/[folder8]/[folder9]/[folder11] is newer than remote t:1418364643/1409580129 ot:1019398/476 o:10DB722EA4A96E5B2FDCE0308490D2CC335D453B/10DB722EA4A96E5B2FDCE0308490D2CC335D453B[20141214 05:33:01.271] MC[452E] [141F]: will send file /GTEYJ6PCKK34PTZ75ZVKXTE5WR6BARDX2QOYDQY/UQLH65NIA6PYVEV3YSO5DBF227IQRDB4TV4FGX6GFGOXITDTIQ4Q/BOCZ27GR6WGSPB7EWBIQC3KMMQ/TXF75XD2R5BWDYXDRUEQ4IG5BU/DCADFUS47MILQIS5PFEDPBQW3E/2JRDCERIMWLCRUJGV2WFPHKHZM/64LXQEKCKFRC73WF3MFBAESZTE[20141214 05:33:01.272] MC[452E] [141F]: failed to verify signature of remote file [folder1]/[folder5]/[folder6]/[folder7]/[folder8]/[folder10]/[filename].jpg, aborting[20141214 05:33:01.272] SF[452E] [141F]: State sync finished[20141214 05:33:01.297] API: --> getsyncfolders(discovery=1&t=1418563981292)[20141214 05:33:02.307] API: --> getsyncfolders(discovery=1&t=1418563982302)[20141214 05:33:03.285] SF[452E] [141F]: Going to sync state with peer [peer ip]]:62981[20141214 05:33:03.285] ScheduledTask:SyncState invoked:timer reason:FinishStateSync - sync not completed

 

It seems like it keeps aborting and restarting, it never starts sending the new files.

 

Any idea why this might be happening, and how to solve this?

Link to comment
Share on other sites

  • 1 month later...

Either long pathname or ignorelist bug

I have 8 peers, all Win 7 x64 or 8.1 x64.  Many files have pathnames longer than 260 characters.  Two days ago, I noticed that one folder had a duplicate with a truncated name:

 

e.g. "Share/Current Work/..." in same folder as "Share/CURREN~1/..."

 

The truncated folder only had a couple files in it, and many empty subfolders.  The regular folder was still present and all of its data seemingly intact.  I resolved this problem in  BTSync 1.3 by modifying the .syncignore files to include the following:

*~*~**~

Accordingly, I modified one workstation's ignorelist so that any file or folder with a tilda would be ignored.  This is where I think I encountered the bug:  The files inside the truncated folder and the regular folder disappeared on all peers.  Immediately, I changed the ignorelist back to its default, restarted all workstations, and began the tedious process of restoring data.  This took approximately 5 hours for tens of thousands of files. 

 

Finally, when all the files were back to their original state (at 3 a.m.), the data loss occurred again.  Originally, the loss occurred (I think) because I modified the ignorelist to include any file with a tilda, but now, the ignorelist was back to default.  I don't know what caused the data loss the second time.

 

Finally, to restore the data again, I completely uninstalled BitTorrent Sync from every machine, restarted them all, then reinstalled BitTorrent Sync and started from scratch.  Luckily I had a backup this time, but I was up all night.  

 

What I think:

I think there is some conflict with BTSync and long pathnames.  This happened in 1.3 also, where truncated/shortened folders (with a tilda) would appear next to the normal folders.  Additionally, I think BTSync must rely on truncated names because when I edited ignorelist to ignore all files with tildas, normal folders also disappeared.  

 

However, I have no clue what caused the data loss the second time.  Bittorrent Sync was running with default settings (no changes to ignorelist), and all on version 1.4.82. I have no other software that would interfere. 

 

Please let me know if you need additional information.  I don't have logs, unfortunately, as this happened out of the blue.

I'm not in any way official support, but I will tell you that windows itself, the windows api, doesn't support files names longer than 260 characters (and that includes the full path and extension). Even beyond Bittorrent Sync, you're asking for headaches to have long file names.

Link to comment
Share on other sites

  • 1 month later...

Your steps do not account for the case of when I don't have a tray icon because I'm running as a service...

 

The overall experience is rather annoying:

 

1. There are 500 files left to sync

2. The peers see each other as online

3. And yet nothing's happening.

 

If you want to see what's happening, whip out the debug log. Bah! Honestly, a techie error message displayed right next to the folder is a gazillion times better than sitting idle doing nothing! At least I can google that without trying to figure out how to enable the log file or how to read it.

Link to comment
Share on other sites

  • 4 months later...

Hi Guys,

 

New to the forum and was wondering if someone can help me? I have been using bit sync without much trouble and now files are repeating themselves with .1 or .2 or .3 etc. after the same file name?

 

example:

costs.1

cost.2

cost.3 

 

all have different dates and don't know if to trust bit sync now!!!!!

 

 

Can someone help and be my saviour?

 

Best,

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.