poescp Posted February 19, 2016 Report Share Posted February 19, 2016 Hi, Very interesting case ... BTSync on my NAS Synology DS 715 automatically stopps running and is deactivated, without myself having done anything. Every few days I have to manually restart BTSync. I have 2.3 as a version. Any ideas what this could be? Phil Quote Link to comment Share on other sites More sharing options...
Zeppo VA Posted February 21, 2016 Report Share Posted February 21, 2016 I have had the same issue for months. Haven't pinned the cause down, but it always seems to occur after an update of BT Sync. The only way I know the app is topped on the Synology is by noticing when files have not synced and then going into the Package app on Synology. Would be happy to hear a solution ... Quote Link to comment Share on other sites More sharing options...
RomanZ Posted February 22, 2016 Report Share Posted February 22, 2016 Hi, The first step would be finding out if your Sync is crashing or is gracefully shut down. It's rather easy to check. Once you noticed it is down - check the "/usr/local/bittorrentsync/var/sync.log" - it should end with something like: [2016-02-19 12:09:04] SyncFolderScanner: shut down [2016-02-19 12:09:04] Shutdown. Saving config sync.dat This indicates a graceful shutdown. If it is different for you - it is likely Sync crashed and we'll be happy to see the core dump(s). Core dumps by default may be found in: /usr/local/bittorrentsync/var/ /usr/local/bittorrentsync/bin/ /volume1/ Quote Link to comment Share on other sites More sharing options...
poescp Posted February 26, 2016 Author Report Share Posted February 26, 2016 None of the above show up, only following ... will PM you with the dump [20160224 00:17:18.724] PD[AEC4] [4732]: failed to open TCP tunnel - endpoint: 192.168.43.22:29458, status: "offline (timed out)", enc: TLS, socket: 0x3b4f3a08, tunnels: 0 [20160224 00:17:19.234] PD[AEC4] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.43.22:29458 [20160224 00:17:19.234] PeerTLSEH[0x3bc6beb0]: hello packet { share:6965F2C12CCDA2043471F1F3E04601D8992B25F2 } has been sent [20160224 00:17:19.235] PD[AEC4] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.0.16:29458 [20160224 00:17:19.235] PeerTLSEH[0x3ae0edb8]: hello packet { share:6965F2C12CCDA2043471F1F3E04601D8992B25F2 } has been sent [20160224 00:17:43.202] LF[8A8B]: LicenseFolder::IsActive(user): return FALSE, id is not in active list, total ids = 1 [20160224 00:17:43.202] LF[3A89]: LicenseFolder::IsActive(trial): return FALSE, license expired [20160224 00:17:47.061] SyncSocket[0x3bac4150]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:47.062] PD[64D4] [4732]: failed to open TCP tunnel - endpoint: 192.168.43.22:29458, status: "offline (timed out)", enc: TLS, socket: 0x3bac4150, tunnels: 0 [20160224 00:17:47.062] PD[64D4] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.43.22:29458 [20160224 00:17:47.063] PeerTLSEH[0x3b485f98]: hello packet { share:E9314AB25C848C29D921B31E43F34154A404211F } has been sent [20160224 00:17:47.741] SyncSocket[0x3aeea3e8]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:47.742] SyncSocket[0x3b8303d8]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:47.742] PD[62E7] [4732]: failed to open TCP tunnel - endpoint: 192.168.0.16:29458, status: "offline (timed out)", enc: TLS, socket: 0x3aeea3e8, tunnels: 0 [20160224 00:17:47.742] SyncSocket[0x3b5eb5b0]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:47.742] SyncSocket[0x3aef7398]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:47.742] SyncSocket[0x3b5c7f68]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:47.742] SyncSocket[0x3b81bed8]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:47.742] SyncSocket[0x3b6fc600]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:47.742] SyncSocket[0x3b3feeb8]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:47.742] SyncSocket[0x3b898928]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:47.742] PD[62E7] [4732]: failed to open TCP tunnel - endpoint: 192.168.43.22:29458, status: "offline (timed out)", enc: TLS, socket: 0x3b8303d8, tunnels: 0 [20160224 00:17:47.742] PD[64D4] [4732]: failed to open TCP tunnel - endpoint: 192.168.0.16:29458, status: "offline (timed out)", enc: TLS, socket: 0x3b5eb5b0, tunnels: 0 [20160224 00:17:47.743] PD[63C0] [4732]: failed to open TCP tunnel - endpoint: 192.168.43.22:29458, status: "offline (timed out)", enc: TLS, socket: 0x3aef7398, tunnels: 0 [20160224 00:17:47.743] PD[63C0] [4732]: failed to open TCP tunnel - endpoint: 192.168.0.16:29458, status: "offline (timed out)", enc: TLS, socket: 0x3b5c7f68, tunnels: 0 [20160224 00:17:47.743] PD[9209] [4732]: failed to open TCP tunnel - endpoint: 192.168.43.22:29458, status: "offline (timed out)", enc: TLS, socket: 0x3b81bed8, tunnels: 0 [20160224 00:17:47.743] PD[9209] [4732]: failed to open TCP tunnel - endpoint: 192.168.0.16:29458, status: "offline (timed out)", enc: TLS, socket: 0x3b6fc600, tunnels: 0 [20160224 00:17:47.743] PD[C73C] [4732]: failed to open TCP tunnel - endpoint: 192.168.43.22:29458, status: "offline (timed out)", enc: TLS, socket: 0x3b3feeb8, tunnels: 0 [20160224 00:17:47.743] PD[C73C] [4732]: failed to open TCP tunnel - endpoint: 192.168.0.16:29458, status: "offline (timed out)", enc: TLS, socket: 0x3b898928, tunnels: 0 [20160224 00:17:48.251] PD[64D4] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.0.16:29458 [20160224 00:17:48.252] PeerTLSEH[0x3b567558]: hello packet { share:E9314AB25C848C29D921B31E43F34154A404211F } has been sent [20160224 00:17:48.287] PD[63C0] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.43.22:29458 [20160224 00:17:48.287] PeerTLSEH[0x3b593088]: hello packet { share:6B14A88C904FEB4F03A074F93D746872B2495A30 } has been sent [20160224 00:17:48.288] PD[63C0] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.0.16:29458 [20160224 00:17:48.288] PeerTLSEH[0x3bd295b8]: hello packet { share:6B14A88C904FEB4F03A074F93D746872B2495A30 } has been sent [20160224 00:17:48.289] PD[9209] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.43.22:29458 [20160224 00:17:48.289] PeerTLSEH[0x3b4f3a08]: hello packet { share:1A3844245205DDCD73573C8FBE9061662043383C } has been sent [20160224 00:17:48.289] PD[9209] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.0.16:29458 [20160224 00:17:48.289] PeerTLSEH[0x3bd9cca0]: hello packet { share:1A3844245205DDCD73573C8FBE9061662043383C } has been sent [20160224 00:17:48.290] PD[C73C] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.43.22:29458 [20160224 00:17:48.290] PeerTLSEH[0x3bac4150]: hello packet { share:89598492886EE7A58248C2D7AF0A2637E45C3FF7 } has been sent [20160224 00:17:48.291] PD[C73C] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.0.16:29458 [20160224 00:17:48.291] PeerTLSEH[0x3b34d218]: hello packet { share:89598492886EE7A58248C2D7AF0A2637E45C3FF7 } has been sent [20160224 00:17:48.292] PD[62E7] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.43.22:29458 [20160224 00:17:48.292] PeerTLSEH[0x3bb0c348]: hello packet { share:1B90BB1D3968AD63DFA7BAC47FAF8EDEDFF82DF4 } has been sent [20160224 00:17:48.292] PD[62E7] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.0.16:29458 [20160224 00:17:48.292] PeerTLSEH[0x3bc34480]: hello packet { share:1B90BB1D3968AD63DFA7BAC47FAF8EDEDFF82DF4 } has been sent [20160224 00:17:48.741] SyncSocket[0x3bc6beb0]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:48.741] SyncSocket[0x3ae0edb8]: an error has occurred - code: 110, message: "offline (timed out)" [20160224 00:17:48.742] PD[AEC4] [4732]: failed to open TCP tunnel - endpoint: 192.168.43.22:29458, status: "offline (timed out)", enc: TLS, socket: 0x3bc6beb0, tunnels: 0 [20160224 00:17:48.742] PD[AEC4] [4732]: failed to open TCP tunnel - endpoint: 192.168.0.16:29458, status: "offline (timed out)", enc: TLS, socket: 0x3ae0edb8, tunnels: 0 [20160224 00:17:49.252] PD[AEC4] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.43.22:29458 [20160224 00:17:49.252] PeerTLSEH[0x3b6cfb50]: hello packet { share:6965F2C12CCDA2043471F1F3E04601D8992B25F2 } has been sent [20160224 00:17:49.253] PD[AEC4] [4732]: checking tunnel connection to peer, transport: TCP, endpoint: 192.168.0.16:29458 [20160224 00:17:49.253] PeerTLSEH[0x3b3feeb8]: hello packet { share:6965F2C12CCDA2043471F1F3E04601D8992B25F2 } has been sent [20160224 00:18:08.070] UPnP: Could not map UPnP Port on this pass, retrying. [20160224 00:18:10.160] Requesting folder config from config.getsync.com Quote Link to comment Share on other sites More sharing options...
poescp Posted February 26, 2016 Author Report Share Posted February 26, 2016 How can I send you the dump/log files RomanZ? Quote Link to comment Share on other sites More sharing options...
RomanZ Posted February 26, 2016 Report Share Posted February 26, 2016 If none appear and log terminates kind of unexpectedly - its a crash. Answered in PM where to send dumps. Thanks! Quote Link to comment Share on other sites More sharing options...
poescp Posted February 26, 2016 Author Report Share Posted February 26, 2016 Thanks, which files exactly should I send to the support system? You only mention paths. Quote Link to comment Share on other sites More sharing options...
RomanZ Posted February 26, 2016 Report Share Posted February 26, 2016 Core dumps should be named something like "@btsync.core". Sync.log also would be great. Quote Link to comment Share on other sites More sharing options...
thejae Posted March 8, 2016 Report Share Posted March 8, 2016 I have the same issue, it has been happening for months. I've been hoping for a fix. As a personal user who bought 3 licenses for each computer, this is pretty inconvenient. Device: Synology DS1513+ with DSM 5.2-5644 Update 5 Quote Link to comment Share on other sites More sharing options...
RomanZ Posted March 9, 2016 Report Share Posted March 9, 2016 @thejae Any dumps in mentioned locations? 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.