Synology Nas Isn't Working


Recommended Posts

I've installed DS415+, DS415Play and DS115j with Sync 2.0.81.

None of them are working properly.

 

I've seen the topic with Qnap NAS.

 

Anyone here with Synology?

 

(got too excited when I heard 2.0 came out and bought the pro version, now i'm waiting for the solution... blankly)

Link to comment
Share on other sites

  • Replies 63
  • Created
  • Last Reply

Top Posters In This Topic

Same thing for me. I have the package installed. Devices are Linked, Folders are shared, nothing transfers. Have not gone Pro because i can't get the trial to work and running out of time on the trial. grrrr  

 

I keep reading that you need to approve the link but i think that is only for invitations that are sent out not for manually entered keys. Any one agree with that or do  you have to approve a manually entered key as well. If so then how do you do that?

 

 

I find the terminology frustrating and trying to share folders is more confusing than it needs to be IMO.

 

It would be nice to have the name of each device show up in the header of the sync GUI interface so when using remote access you could keep straight what machine you were looking at. 

 

I think there is something here but as SNL was in the beginning  "not ready for prime-time players" yet.

 

Synology DS1511+ Running version 5 update 3 and Bitsync 2.0.81-1

Link to comment
Share on other sites

I seem to be experiencing similar issues with a DS1812+ and DS1813+, both are running DSM 5.0-4993 Update 5 and Sync 2.0.81-1 cedarview (x64) packages. For simplicities sake I’ll refer to these as Synology1 (DS1812+) and Synology2 (DS1813+) from now on. For this example the directory I want to Sync from Synology1 -> Synology2 is named ‘Samsung Config Data’ and the ‘Scripts’ from Synology2 -> Synology1. I should also mention that both of these devices reside on the same LAN.

 

During initial setup the Synology2 hung whilst trying to link to Synology1 see link (https://i.imgur.com/ieW6act.png), after refreshing the page I was able to progress and setup the default sync location etc. Both Synologies seem to be linked and both appear as online and linked within their respective 'My devices...' menu, see images below.

 

Synology1: https://imgur.com/6TTfOyq.png

Synology2: https://imgur.com/bWxtNqa.png

 

Adding the ‘Samsung Config Data’ folder within Synology1 everything seemed to be working perfectly, the added folder is displayed as ‘Owner – Synced’. This folder is then displayed within the web interface on Synology2, however I then noticed that no data had been copied.

 

Inside the web interface on Synology1 the size of the folder is reported as ‘333.47 KB’, checking the ‘Peer list’ menu shows that all files and directories have been synced to Synology2, see images below.

 

Synology1: https://i.imgur.com/C28UmrM.png

Synology2: https://i.imgur.com/tuylVb4.png

 

Checking the web interface on Synology2 reports that the folder is also ‘Owner – Synced’, however the directory size as 0 KB. The ‘Peer list’ menu on Synology2 reports that it has been successfully synced with Synology1, see images below.

 

Synology1: https://i.imgur.com/GBtY6yS.png

Synology2: https://i.imgur.com/o3OhObJ.png

 

I checked the file structure on both Synologies, Sync 2.0 looks to be creating the ‘Samsung Config Data’ folder structure within Synology2’s default sync location, even the ‘.sync’ folder is created inside, but apart from that no other data is synced between the devices. See images below.

 

Synology1: https://i.imgur.com/0lS3P9E.png

Synology2: https://i.imgur.com/epKhrx5.png

 

I then tried to process in reverse, adding a folder called ‘Scripts’ on Synology2 to be synced to Synology1. As with the previous example ‘Scripts’ is displayed as ‘Owner – Synced’ within the web interface on Synology2, checking the same on Synology1 I noticed that the folder was ‘Pending/Disconnected’  see link (https://i.imgur.com/sHQVO7R.png). After connecting the folder manually it displays as ‘Owner – Synced’.

 

As with the ‘Samsung Config Data’ directory, the ‘Size’ column on Synology2 reports the folder as ‘1.78 KB’, Synology1 displays it as‘0 KB’. ‘Peer list’ menus also display the same, that is, Synology2 reports that ‘Scripts’ and the files inside have been synced, ‘Peer list’ on Synology1 displays ‘Synced with 192.168.x.x’ for the ‘Scripts’ folder.

 

The file structure for the synced ‘Scripts’ directory is also the same, with the directory being created on Synology1 along with the ‘.sync’ directory inside, but no other data is present.

 

I have reinstalled Sync on both devices and have ran into the exact same set of errors twice. I have included debug logs for both NAS’, see links below.

 

Synology1: http://pastebin.com/qxK5HRVA

Synology2: http://pastebin.com/uzqAzX3K

 

Thanks.

Link to comment
Share on other sites

I'm having similar problem.

Setup: Sync 2.0.85 on my PC, Sync 2.0.81 from getsync on Synology DS415+ NAS, Sync 20.064.0 on my Android HTC.

Folders added from PC won't sync on NAS (only the .sync folder is created). They snyc fine on phone if I ask so.

Folders added from phone (at least DCIM backup) are in 1.4 format and sync fine on both NAS and PC.

Is this issue due to a bug, or a manipulation problem on my side (permissions or dunno what) ??

Any help welcome!

Thanks, Florian

Edited by TheFlow
Link to comment
Share on other sites

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
 
Edited by Leftism11
Link to comment
Share on other sites

Yay, thx for the fix!

 

Is it possible to create 1.4 folders using 2.0? And to convert them to 2.0 later?

 

Thank you for the help,

Florian

 

PS

 

PS if it's relevant, here's the glibc info on my DS415+ (DSM 5.1-5022 Update 3)

GNU C Library stable release version 2.13, by Roland McGrath et al.Copyright (C) 2011 Free Software Foundation, Inc.This is free software; see the source for copying conditions.There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR APARTICULAR PURPOSE.Compiled by GNU CC version 4.6.3.Compiled on a Linux 3.6.3 system on 2012-12-03.Available extensions:        crypt add-on version 2.1 by Michael Glad and others        Native POSIX Threads Library by Ulrich Drepper et al        BIND-8.2.3-T5Blibc ABIs: UNIQUE IFUNCFor bug reporting instructions, please see:<http://www.gnu.org/software/libc/bugs.html>.
Edited by TheFlow
Link to comment
Share on other sites

Is it possible to create 1.4 folders using 2.0? And to convert them to 2.0 later?

 

 

I could find no way to do this from the web gui.  You can do it by:

 

1) Generate a secret from the commandline:  

   $ /usr/local/bittorrentsync/bin/btsync --generate-secret

 
2) Click on 'Manual Connection' and then paste the secret generated.  You'll then select the folder for that.  The folder will be setup as a 1.4 folder.
 
Alternatively, install the old version of btsync on another system (eg: old windows machine) and create the shared folder there.  Then copy the secret and use that secret as described above to manually connect.
 
There is no conversion path to 2.0 at this point.  Dunno if that is planned.  You can always unsync and resync at a future date to go to 2.0.
Link to comment
Share on other sites

@all

The issue is identified and fixed. It is bound to glibc2.3 version of Sync only. Please expect updated build with the fix soon. As a workaround, you can use 1.4 folders - they should work fine.

You sure? I have the same issue with very similar logs, as already posted, and I'm using the package sync provides for synology. There is a Linux glibc2.3 package that is separate from that and I'm worried that the synology package will be overlooked.
Link to comment
Share on other sites

You sure? I have the same issue with very similar logs, as already posted, and I'm using the package sync provides for synology. There is a Linux glibc2.3 package that is separate from that and I'm worried that the synology package will be overlooked.

 

The Synology package uses the glibc23 binary, so no worries on Synology being overlooked. You should try the 2.0.85 below.  :)

 

@All - Download links for 2.0.85 for Synology have been updated:

http://help.getsync.com/customer/portal/articles/1888507-synology

 

This should resolve the issue where 2.0 folders were not syncing. 

 

If you already installed 2.0.85, please re-install with this latest version.

 

If anyone can confirm that the issue is resolved for avotron, bromolow, cedarview, or evansport - this would be greatly appreciated. 

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.