Leftism11

Members
  • Posts

    4
  • Joined

  • Last visited

Leftism11's Achievements

New User

New User (1/3)

  1. After 2.0.85 successfully sync'd my two 2.0 folders today on the Synology, at some point it stopped working. I tried to connect tonight, and got nothing. I checked the package in Synology and the status was Stopped. I restarted it, and it seems fine again, but based on the note by @linenoise, there may be a crashing issue. I've turned on debug logging in case it happens again.
  2. Just installed 2.0.85 Cedarview on a DS1813+ and it started syncing the 2.0 folders right away. I'll keep an eye on it for reliability, but it's looking good so far. Thanks!
  3. Same issue here. 1.4 folder syncs fine, 2.0 folder won't sync on my Synology. This is what was in my Synology log: [12:18:21] Can't open file /usr/local/bittorrentsync/var/webui/js/templates.js.gz with mode 0 permissions 666 - 2 No such file or directory[12:18:21] Can't open file /usr/local/bittorrentsync/var/webui/js/templates.js with mode 0 permissions 666 - 2 No such file or directory[12:18:21] Can't open file /usr/local/bittorrentsync/var/webui/js/templates.js.gz with mode 0 permissions 666 - 2 No such file or directory[12:18:21] Can't open file /usr/local/bittorrentsync/var/webui/js/templates.js with mode 0 permissions 666 - 2 No such file or directory[12:18:22] Can't open file /usr/local/bittorrentsync/var/webui/version.json.gz with mode 0 permissions 666 - 2 No such file or directory[12:18:22] Can't open file /usr/local/bittorrentsync/var/webui/version.json with mode 0 permissions 666 - 2 No such file or directory[12:18:22] assert failed /mnt/jenkins/workspace/Build-Sync-x64-glibc23/TunnelConnection.cpp:286[12:18:22] assert failed /mnt/jenkins/workspace/Build-Sync-x64-glibc23/TunnelConnection.cpp:286 I bought Pro, so I've submitted a support case. Initial response from support tech indicated he was clueless or didn't bother to actually read the initial logs I submitted. I have since submitted the debug logs from both my windows machine and the Synology, so I'm waiting for a response. The debug logs are a pile of undecipherable gibberish to me, but there appears to be some type of connection issue. [20150306 08:22:08.464] Incoming connection from 192.168.25.200:10823[20150306 08:22:08.464] SF[0DE5] [1796]: Received request "state_notify"[20150306 08:22:08.464] Incoming connection from 192.168.25.200:50355[20150306 08:22:08.464] assert failed /mnt/jenkins/workspace/Build-Sync-x64-glibc23/TunnelConnection.cpp:286[20150306 08:22:08.464] PD[F150] [1796]: Lost tunnel - id: 629, transport: TCP, status: "Connection has been closed by a peer", endpoint: 192.168.25.200:50355, encryption: TLS[20150306 08:22:08.465] Disconnect: Connection closed [20150303 21:14:19.196] Incoming connection from 192.168.25.216:27790[20150303 21:14:19.196] assert failed /mnt/jenkins/workspace/Build-Sync-x64-glibc23/TunnelConnection.cpp:286[20150303 21:14:19.196] Disconnect: Connection closed[20150303 21:14:19.196] Incoming connection from 192.168.25.200:10823[20150303 21:14:19.197] assert failed /mnt/jenkins/workspace/Build-Sync-x64-glibc23/TunnelConnection.cpp:286[20150303 21:14:19.197] Disconnect: Connection closed
  4. I wasn't able to confirm a folder sync request for a few days and it expired. I eventually added a new folder sync request which I did properly confirm, and the sync is now working fine. However, the prior "Request expired" folder entry is still listed in Sync and I can't figure out how to remove it. I read the documentation that simply says "remove the folder". http://sync-help.bittorrent.com/customer/portal/articles/1691237-list-of-sync-status-icons But I don't see any buttons, menus, or options to remove it. Restarting Sync doesn't clear it out either. Can the expired folder be removed? If so, what is the trick to removing it?