BTSu Posted January 30, 2016 Report Share Posted January 30, 2016 There is no much sense to send "ping" to "local IP" every second, if there is no response. It wastes network traffic and populates "sync.log" file with myriads of completely unnecessary lines... Prerequisites: * BTSync runs on a PC, that is in IP segment 192.168.1.0/24 * Remote Sync/Android client runs from NAT router, that has similar local segment 192.168.1.0/24 When Sync/Android connects to BTSync/Windows, the latter logs: [2016-01-29 19:02:34] Got list of 1 peers for share FD74..3594 [2016-01-29 19:02:34] Peer 0: WAN.IP.ADD.RES:55891 11ED..47D5 [2016-01-29 19:02:34] Peer 0: local IP 192.168.1.2:14248 Then log confirms connection to WAN IP of the remote client: [2016-01-29 19:02:35] ping WAN.IP.ADD.RES:1794 [2016-01-29 19:02:35] Checking connection to WAN.IP.ADD.RES:1794:TCP [2016-01-29 19:02:35] Incoming connection from WAN.IP.ADD.RES:1794 [2016-01-29 19:02:35] Incoming connection from WAN.IP.ADD.RES:39402 [2016-01-29 19:02:35] Incoming connection from WAN.IP.ADD.RES:39403 And after that, there is endless sequence of "ping" attempts to "local IP", that all failed: [2016-01-29 19:02:34] Peer 0: local IP 192.168.1.2:14248 [2016-01-29 19:02:35] Send ping to peer (11ED..47D5) for share FD74..3594: [2016-01-29 19:02:35] Checking connection to 192.168.1.2:14248:TCP [2016-01-29 19:02:35] Send ping to peer (11ED..47D5) for share [2016-01-29 19:02:36] Send ping to peer (11ED..47D5) for share FD74..3594: [2016-01-29 19:02:36] ping 192.168.1.2:14248 [2016-01-29 19:02:37] Send ping to peer (11ED..47D5) for share FD74..3594: [2016-01-29 19:02:37] ping 192.168.1.2:14248 ... Presumption, that the client on "local IP" is always accessible, could be wrong (see Prerequisites above). And in such case, there is no need to continue sending "ping" requests every second. It's completely pointless... I'm running BTSync v1.3.109. Quote Link to comment Share on other sites More sharing options...
Moe Posted January 30, 2016 Report Share Posted January 30, 2016 May I ask why you are still running 1.3.109? You can/should update to at least 1.4 if you are not comfortable with the 2.0 release. But if you just have forgotten about it: We just had a release of the version 2.3 which you can get at https://getsync.com for your clients. If you are curious on what that all bring and if you can still have your shares using the secrets/keys - you can get all that information on http://help.getsync.com Since 1.3 is so old - I can just not comment on why it was doing that back then.. there is a big possibility that this has changed after a good portion of releases ;-) Quote Link to comment Share on other sites More sharing options...
BTSu Posted January 30, 2016 Author Report Share Posted January 30, 2016 Sure. It's because I'm using Windows Server 2003/32 to run it and I believe 1.3.109 is the latest version to run on that OS. It looks like the official download site doesn't offer anything newer. Could you please provide me a link to download 1.4. I'd be glad to check, if the issue was fixed there. Thanks. Quote Link to comment Share on other sites More sharing options...
GreatMarko Posted January 30, 2016 Report Share Posted January 30, 2016 3 hours ago, BTSu said: Sure. It's because I'm using Windows Server 2003/32 to run it and I believe 1.3.109 is the latest version to run on that OS. It looks like the official download site doesn't offer anything newer. Could you please provide me a link to download 1.4. I'd be glad to check, if the issue was fixed there. Sync 1.4 win run on Win2k3, however the UI will only be accessible via a modern web browser (Sync 1.4 required IE9+, which isn't available on 2k3, so you'll need Firefox/Chrome, etc) Sync 1.4 may be obtained via the links in this topic. Quote Link to comment Share on other sites More sharing options...
BTSu Posted January 31, 2016 Author Report Share Posted January 31, 2016 (edited) @GreatMarko Thank you for the link. I've downloaded BTSync-1.4.111.exe file (MD5: 315C72EDBA8D359C61FE325BE2FA5155). But when I try to run it in Win2K3, it silently exits. There is no error or any kind of message... It's strange. I'm a bit confused with "UI will only be accessible via a modern web browser" thing. Do I have to do something special to access the BTSync UI dialog box now? In 1.3 I open its dialog box from tray icon. Do I have to connect to it now via port 80? My W2003 server runs my web site (along with some other services). Could it be the reason why BTSync just silently exits? Edited January 31, 2016 by BTSu Removing bold formatting Quote Link to comment Share on other sites More sharing options...
GreatMarko Posted January 31, 2016 Report Share Posted January 31, 2016 9 hours ago, BTSu said: Thank you for the link. I've downloaded BTSync-1.4.111.exe file (MD5: 315C72EDBA8D359C61FE325BE2FA5155). But when I try to run it in Win2K3, it silently exits. There is no error or any kind of message... It's strange. Right-click the file, go to Properties -> Unblock (Win2k3 blocks running of unknown downloaded .exe's by default - you'll need to unblock it first) 9 hours ago, BTSu said: I'm a bit confused with "UI will only be accessible via a modern web browser" thing. Do I have to do something special to access the BTSync UI dialog box now? In 1.3 I open its dialog box from tray icon. Do I have to connect to it now via port 80? My W2003 server runs my web site (along with some other services). Could it be the reason why BTSync just silently exits? Sync 1.3 (and earlier) used standard windows-based dialogs/forms. For Sync 1.4, the UI has become HTML based. If you have IE9 (or later) installed, you can click Sync's tray icon as normal, and the HTML UI will open in a dedicated window. Because you can't install IE9 on win2k3, this option is not available, and you can instead access sync's UI via http://127.0.0.1:8888 through Firefox/Chrome instead 9 hours ago, BTSu said: Could it be the reason why BTSync just silently exits? No, Sync exits because you've not unblocked the exe Quote Link to comment Share on other sites More sharing options...
BTSu Posted January 31, 2016 Author Report Share Posted January 31, 2016 8 hours ago, GreatMarko said: Right-click the file, go to Properties -> Unblock (Win2k3 blocks running of unknown downloaded .exe's by default - you'll need to unblock it first) Are you talking about :Zone.Identifier ADS here? It's not the reason because I don't use that. Executable file is ADS free. 9 hours ago, GreatMarko said: Sync 1.3 (and earlier) used standard windows-based dialogs/forms. For Sync 1.4, the UI has become HTML based. ... Because you can't install IE9 on win2k3, this option is not available, and you can instead access sync's UI via http://127.0.0.1:8888 through Firefox/Chrome instead OK. I've checked server for used ports and port 8888 available for binding. So, inability to bind listening port to 8888 is not the case here too... 9 hours ago, GreatMarko said: No, Sync exits because you've not unblocked the exe There is no lock on .EXE file. It simply exits when I try to launch it. There is no any warnings or error messages... It could give me a message box if there is a problem to solve. Or program may start with initiating its logging module first and put all its problems in a local "sync.log" file. But there is nothing. How to find out the problem in such case? Quote Link to comment Share on other sites More sharing options...
GreatMarko Posted January 31, 2016 Report Share Posted January 31, 2016 2 hours ago, BTSu said: Are you talking about :Zone.Identifier ADS here? It's not the reason because I don't use that. Executable file is ADS free. There is no lock on .EXE file. It simply exits when I try to launch it. There is no any warnings or error messages... It could give me a message box if there is a problem to solve. Or program may start with initiating its logging module first and put all its problems in a local "sync.log" file. But there is nothing. How to find out the problem in such case? No, I'm not talking about ":Zone.Identified ADS". It's normal (blame Microsoft!) for the behavior you described when the .exe file you've downloaded hasn't been "unblocked" - when you run it, nothing happens, no warning - nothing! However, once you "unblock" the file on your Win2K3 as outlined (Right click the .exe file, select "Properties" and click the "Unblock" button): ..you'll then be able to execute the .exe file as normal. Quote Link to comment Share on other sites More sharing options...
BTSu Posted January 31, 2016 Author Report Share Posted January 31, 2016 Here is what I see in Properties box for BTSync.exe v1.4.111.0 Quote Link to comment Share on other sites More sharing options...
GreatMarko Posted February 1, 2016 Report Share Posted February 1, 2016 The exe file you downloaded was "BTSync-1.4.111.exe", yet your screenshot shows "BTSync.exe" - therefore, please can you clarify whether your issue relates to the installing Sync 1.4 (BTSync-1.4.111.exe), or whether you've installed Sync 1.4, and your issue relates to running Sync 1.4 (BTSync.exe)? Quote Link to comment Share on other sites More sharing options...
BTSu Posted February 2, 2016 Author Report Share Posted February 2, 2016 That's correct. I've downloaded file "BTSync-1.4.111.exe" and renamed it as "BTSync.exe". It's located in folder "C:\Sys\bin\BTS". As you can see on the Properties box picture (see my previous post) it has size 4,173,664 bytes and it's MD5 check sum I posted earlier. It was the "first run" (although I made many attempts to do that) and its launch always failed. I tried to run it using old settings ("settings.dat" placed in the same folder as "BTSync.exe"). In this case it should run, using old configuration. And I tried to run it without that settings file. In this case it could run a setp. The result in both cases was always the same - it simply failed to launch... P.S. This is the second attempt to make my post today in the same thread. The first post was accepted OK, but then just disappeared BTW, to moderators - changing domain name in this forum brakes all my old links to it... It's worst decision, that could be made in any forum Please keep that in mind. Thank you. Quote Link to comment Share on other sites More sharing options...
Trfac Posted July 14, 2016 Report Share Posted July 14, 2016 Has there been any progress on this issue so far? I have two Raspberry Pi-s on two remote locations behind NATs, one has 2.3.8 and the other one 2.3.7 version, and in both of them I see this kind of behaviour. They repeatedly try to ping the local ip of the other rpi. Snippets from the sync.log: rpi1 (local ip: 192.168.1.2) V2.3.8: Quote [20160714 10:04:05.496] SD[44CC]: Got list of 3 peers [20160714 10:04:05.496] SD[44CC]: Peer 1 - external addr ... [20160714 10:04:05.496] SD[44CC]: Peer 1 - local IP: 192.168.0.103:27483 ... [20160714 10:04:06.148] PD[44CC] [392E]: Sending ping to "192.168.0.103:27483" [20160714 10:04:06.149] PD[44CC] [392E]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.0.103:27483 [20160714 10:04:07.191] PD[44CC] [392E]: Sending ping to "192.168.0.103:27483" [20160714 10:04:07.192] PD[B667] [392E]: Sending ping to "192.168.0.103:27483" [20160714 10:04:07.193] PD[154D] [392E]: Sending ping to "192.168.0.103:27483" [20160714 10:04:07.193] PD[4EB2] [392E]: Sending ping to "192.168.0.103:27483" ... [20160714 10:04:36.011] SyncSocket[0xafa0a890]: an error has occurred - code: 110, message: "offline (timed out)" [20160714 10:04:36.011] SyncSocket[0xafaa2698]: an error has occurred - code: 110, message: "offline (timed out)" [20160714 10:04:36.013] PD[44CC] [392E]: failed to open TCP tunnel - endpoint: 192.168.0.103:27483, status: "offline (timed out)", enc: SRP, socket: 0xaf777fe8, tunnels: 1 [20160714 10:04:36.014] PD[44CC] [392E]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.0.103:27483 [20160714 10:04:36.016] PD[B667] [392E]: failed to open TCP tunnel - endpoint: 192.168.0.103:27483, status: "offline (timed out)", enc: SRP, socket: 0xafa128c8, tunnels: 1 and this goes on and on... rpi2 (local ip: 192.168.0.103) V2.3.7: Quote [20160714 12:04:06.633] SD[B667]: Got list of 3 peers [20160714 12:04:06.633] SD[B667]: Peer 0 - external addr ... [20160714 12:04:06.633] SD[B667]: Peer 0 - local IP: 192.168.1.2:11923 ... [20160714 12:04:06.967] PD[8A72] [D41F]: failed to open TCP tunnel - endpoint: 192.168.1.2:11923, status: "offline (timed out)", enc: SRP, socket: $ [20160714 12:04:07.474] PD[154D] [D41F]: Sending ping to "192.168.1.2:11923" [20160714 12:04:07.476] PD[B667] [D41F]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.1.2:11923 [20160714 12:04:07.477] PD[B667] [49EE]: Sending ping to "192.168.1.47:64756" [20160714 12:04:07.970] PD[0737] [D41F]: failed to open TCP tunnel - endpoint: 192.168.1.2:11923, status: "offline (timed out)", enc: SRP, socket: 0x6e898f58, tunnels: 1 [20160714 12:04:07.971] PD[F09C] [D41F]: failed to open TCP tunnel - endpoint: 192.168.1.2:11923, status: "offline (timed out)", enc: SRP, socket: 0x6bebc470, tunnels: 1 [20160714 12:04:07.971] PD[65CA] [D41F]: failed to open TCP tunnel - endpoint: 192.168.1.2:11923, status: "offline (timed out)", enc: SRP, socket: 0x6e6706d8, tunnels: 1 Both sync logs are filled with similar lines. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.