Sync 2.0 Qnap Package Doesn't Work


Recommended Posts

I've just installed the x86_64 Sync 2.0.81 package on my QNAP TS-269L and, while it installs without error, it doesn't seem to run at all. When I click on the link to access the web interface, on port 14859, I can't connect. In addition, my PC's sync 2.0 client shows the NAS peer as offline.

 

Is this package broken? Am I missing something?

 

Thanks for any ideas!

Link to comment
Share on other sites

Howdy MrTorrent,

 

I'm guessing that you were upgrading an existing install from 1.4?

 

Are there any messages within the NAS's notification area?

 

If you're able to SSH in to the NAS as admin, what are the results of running the command "/etc/init.d/btsync.sh stop" and "/etc/init.d/btsync.sh start"?

 

Thanks,

Richard

Link to comment
Share on other sites

Hi, I'm having the same exact problem, except it's on a TS-451 (Intel Celeron Dual Core) and this is a brand new install (no previous versions loaded before). I installed the x86_64 package, and when I try to open the app, the browser won't load. I'm not familiar with SSH so I didn't run the command you listed. Can I provide any other info?

Link to comment
Share on other sites

Most consumer grade QNAP systems work with the x86 packages only (even if "uname -a" tells you something about x86_64). x86 "works" with my TS-469L but... well... it does not sync anything, even though it should.

 

Also be careful what folder you choose as share root directory. The default suggestion is "/share" which is very bad for the 4xx series, as this path is not(!) linked to the installed HDDs. The installed HDDs space is mounted to one of the "/share/CACHEDEV?_DATA" folders, so try to keep the folders in there.

Edited by kreischweide
Link to comment
Share on other sites

For me Sync 2.0 isn't working on my TS-670, too. Linking the device isn't working as expected (i had to refresh the page manual to get to the next screen for choosing the storage path) and syncing is also not working.

 

Syncing a old 1.4-folder: Size is shown correctly in the web gui and the sync is working as expected

Syncing a new 2.0-folder: Size is shown as 0byte, sync is shown as finished and the folder is empty...

 

I've already opened a support ticket for providing my logfile.

 

Regards from Germany!

Link to comment
Share on other sites

Thanks for the fast reply, Richard, and thanks to everyone else for chiming in, too.

 

 

I'm guessing that you were upgrading an existing install from 1.4?

 

Are there any messages within the NAS's notification area?

 

If you're able to SSH in to the NAS as admin, what are the results of running the command "/etc/init.d/btsync.sh stop" and "/etc/init.d/btsync.sh start"?

 

Initially, I did install the 2.0 package as an update to the 1.4 version I had installed. I have also, however, tried uninstalling it completely and installing it fresh, with the same results. Whenever I install the 2.0 package, I do get one notification, saying that the old configuration has been moved.

 

I haven't tried SSHing in yet, but I can try that later.

 

 

Most consumer grade QNAP systems work with the x86 packages only (even if "uname -a" tells you something about x86_64). x86 "works" with my TS-469L but... well... it does not sync anything, even though it should.

 

Also be careful what folder you choose as share root directory. The default suggestion is "/share" which is very bad for the 4xx series, as this path is not(!) linked to the installed HDDs. The installed HDDs space is mounted to one of the "/share/CACHEDEV?_DATA" folders, so try to keep the folders in there.

 

I'm a bit confused about the x86_64 thing -- isn't the Intel Atom in my model a 64-bit processor, so shouldn't I be installing 64-bit packages?

 

I haven't seen anywhere to pick a share root directory yet, but thank you for the tip, I'll keep it in mind!

Link to comment
Share on other sites

I do not remember if I ever had 1.x on the QNAP, but it was not installed when I installed the 2.x version. I also submitted a ticket for this, containing three logfiles, ticket is #19665.

 

The only thing that looks remotely comprehensible in the QNAP logfile and could indicate a problem is:

[20150304 09:38:08.499] FC[6FD7]: started periodic scan for "/share/CACHEDEV1_DATA/BitTorrentSync/Programme"[20150304 09:38:08.500] FC[6FD7]: file updated - processing file /share/CACHEDEV1_DATA/BitTorrentSync/Programme/test-from-nas.zip t:1425457833 s:22 id:64768:2883604[20150304 09:38:08.500] FC[6FD7] (R/O): new file "/share/CACHEDEV1_DATA/BitTorrentSync/Programme/test-from-nas.zip". Skipping

Not sure why it is skipping, but i guess (R/O) means read-only? The was never transfered to two other (working) PCs.

 

Otherwise, after some runtime (some minutes) there are alot of those:

[20150304 09:38:08.543] assert failed /mnt/jenkins/workspace/Build-Sync-x86-glibc23/TunnelConnection.cpp:286

Otherwise, the test-from-nas.zip should have been sent to 192.168.79.80 (main PC, working and syncing to Laptop). The only thing I can see in the QNAP logfiles regarding this IP is:

[20150304 09:28:05.446] PD[6FD7] [0A2B]: Send ping to peer[20150304 09:28:05.446] PD[6FD7] [0A2B]: ping 192.168.79.80:29431[20150304 09:28:05.446] PD[6FD7] [0A2B]: Checking tunnel connection to peer, transport: TCP, endpoint: 192.168.79.80:29431[20150304 09:28:05.451] PD[5B66] [0A2B]: Failed to open TCP tunnel, endpoint: 192.168.79.80:63323, status: "Connection refused", encryption: SRP[20150304 09:28:05.451] PD[738C] [0A2B]: Failed to open TCP tunnel, endpoint: 192.168.79.80:29431, status: "Connection refused", encryption: TLS[20150304 09:28:05.451] PD[0A06] [0A2B]: Failed to open TCP tunnel, endpoint: 192.168.79.80:29431, status: "Connection refused", encryption: TLS[20150304 09:28:05.451] PD[6FD7] [0A2B]: Failed to open TCP tunnel, endpoint: 192.168.79.80:29431, status: "Connection refused", encryption: TLS

The PC itself had no problem registering and listening to this port though:

[2015-03-04 09:28:41] UPnP(XP): Removed TCP port 0[2015-03-04 09:28:41] UPnP(XP): TCP port 29431 -> 192.168.79.80:29431 mapped successfully.[2015-03-04 09:28:41] UPnP(XP): UDP port 29431 -> 192.168.79.80:29431 mapped successfully.

Also the Laptop (different location connected over wan) had no problems connecting to the PC itself:

[2015-03-04 09:29:10] PD[0A06] [0A2B]: ping 192.168.79.80:29431[2015-03-04 09:29:10] PD[0A06] [0A2B]: Checking tunnel connection to peer, transport: TCP, endpoint: 192.168.79.80:29431[2015-03-04 09:29:10] SSLEH[0x0edd56a0]: hello packet { share:XYZ } has been sent[2015-03-04 09:29:10] SSPI[0x0a42e770]: Create SSPI encryption holder
Edited by kreischweide
Link to comment
Share on other sites

I've tried the Linux build (not the qnap qpkg) and had also no success... Same error as above :-/.

The _64-Builds won't start, but maybe it is okay for the qnap. I am not sure whether the _64-builds should run or not... maybe this error is okay.

 

Hope that the sync-team will find a solution too - i am missing the sync-functionality :-)

Link to comment
Share on other sites

Updated packages for 2.0.85 for QNAP have been posted:

http://help.getsync.com/customer/portal/articles/1888504-qnap

 

If you already installed 2.0.85, please re-install with the latest package.

 

This should resolve the issues having to do with 2.0 folders not being synced.

 

If the x86_64 QNAP packages are still not starting - can someone please SSH in to the NAS as admin, and send me the results of running the commands "/etc/init.d/btsync.sh stop" and "/etc/init.d/btsync.sh start"?

Link to comment
Share on other sites

If the x86_64 QNAP packages are still not starting - can someone please SSH in to the NAS as admin, and send me the results of running the commands "/etc/init.d/btsync.sh stop" and "/etc/init.d/btsync.sh start"?

 

Result from a QNAP-469L, with the 85 x64 version

[~] # /etc/init.d/btsync.sh stopBTSync isn't running[~] # /etc/init.d/btsync.sh startStarting btsync service/share/CACHEDEV1_DATA/.qpkg/BitTorrentSync/btsync: error while loading shared libraries: librt.so.1: wrong ELF class: ELFCLASS32[~] # uname -aLinux NAS 3.4.6 #1 SMP Tue Feb 17 05:18:39 CST 2015 x86_64 unknown
Link to comment
Share on other sites

  • 1 month later...

Updated packages for 2.0.85 for QNAP have been posted:

http://help.getsync.com/customer/portal/articles/1888504-qnap

 

If you already installed 2.0.85, please re-install with the latest package.

 

This should resolve the issues having to do with 2.0 folders not being synced.

 

If the x86_64 QNAP packages are still not starting - can someone please SSH in to the NAS as admin, and send me the results of running the commands "/etc/init.d/btsync.sh stop" and "/etc/init.d/btsync.sh start"?

 

I installed the qpkg for 2.0.93 through the App Center on the NAS interface and got the same error as the OP with the app not loading. I can, however, launch it manually through SSH with the "/etc/init.d/btsync.sh start" command. I'd prefer to not have to SSH in everytime I want to run this, though.

Link to comment
Share on other sites

  • 2 months later...

I'll join in on the thread of people that on a clean install, can't get the latest qpkg 2.0.105 to work for a NAS to NAS sync. Using brand new TS-563 to TS-269L. By adding a computer with the same passkey as a third device, then everything springs to life and sync happens in all directions. Remove the computer and NAS to NAS has zero activity. Uninstalled the version 2 software and manually installed the version 1.4 software and everything works. Click the "update" button on the app expecting it to install the latest of the version 1 series, but without warning it installs version 2.0.105 and while the version 1.4 folders are preserved the sync comes to full stop. Uninstalled again and reinstalled 1.4.48.2 and I am back in business, though the throughput for updates is surprisingly slow at under 5Mbs, but it does work. Is any work being done to get Version 2 to work properly on QNAP devices? The "endorsement" for BT Sync-available on the BT Sync site is a primary reason I selected QNAP hardware. I'm considering a return since real time two-way sync between our two locations was our primary requirement. Thoughts?

Link to comment
Share on other sites

  • 4 weeks later...
  • 3 weeks later...

I also have a problem with the 2.0.125 package.

on both my Imac an Macbook i'm running the 2.0.128 package. Today I updated my QNAP NAS to the 2.0.125 version available through qnap app center.

After that update Bit Sync on both my Imac and Macbook keep saying that my nas is offline ...

 

Seems like the same problem other users had with the 2.0.85 version?

 

I have a QNAP TS 253 PRO system.

 

Hopefully this problem can be soon fixed!

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.