[Solved] Unable to sync on Linux, get "assert failed"

[Marco Pracucci]

Hi there,

I'm trying to setup rslsync to run inside a Docker container. The client successfully get the list of peers (the peers IPs are the expect ones), but then it doesn't sync any file and in other clients I can't see the new client in the peers list.

The rslsync app continuously logs this group of messages (please note I replaced the real IP with "x.x.x.x"):

[...]
[20161126 05:47:46.152] SF[A262] [B866]: Going to sync state with peer x.x.x.x:51025
[20161126 05:47:46.152] D! 10SyncTcpReq[0x00007f56c818f0a0][TCP] [0000]: debug C818F0A0 - outgoing merge
[20161126 05:47:46.152] SF[A262] [B866]: ConecurrentMergeController has started request[0x00007f56c818f0a0] processing
[20161126 05:47:46.152] ScheduledTask: "SyncState" invoked: timer, reason:FinishStateSync - sync not completed
[20161126 05:47:46.153] SF[A262] [B866]: connected, endpoint: x.x.x.x:51025
[20161126 05:47:46.153] assert failed /home/jenkins/slave-root/workspace/Build-Sync-Manually/SyncSecret.cpp:449
[20161126 05:47:46.153] MC[A262] [B866]: generating intial request with root 0000000000000000000000000000000000000000
[20161126 05:47:46.257] D! 10SyncTcpReq[0x00007f56c818f0a0]: EOF or error occurred -  code: 0, message: "Success"
[20161126 05:47:46.257] D! 10SyncTcpReq[0x00007f56c818f0a0][TCP-TUNNELL] [0000]: eof - outgoing merge
[20161126 05:47:46.257] SF[A262] [B866]: State sync finished
[...]

I'm wondering if the following error is somewhat related to the problem, but I didn't find anything googling it:

assert failed /home/jenkins/slave-root/workspace/Build-Sync-Manually/SyncSecret.cpp:449

May you give me any hint, please?

 

[Helen]

what exactly sync version you have? I mean build number 

[Marco Pracucci]

I do run 2.4.2 installed from tar.gz.

[Helen]

that assert means that the key to the share is somehow wrong. Did you use a custom key? 
To fix that remove the share from Sync and add again, re-share the key and make sure that it's not altered when being shared. 

[Marco Pracucci]

Let me share some details with you.

I have a PRO license and I have a shared folder on Mac. I would like to share an "Advanced Folder" in read-only with linux user (running the CLI app version 2.4.2), who is experiencing the issue described above (and for which you say "the key to the share is somehow wrong").

I'm actually unsure I got the secret from my Mac in the right way. To re-start from scratch, can you tell me how can I get the secret for an "Advanced Folder" on my Mac, so that I can copy-and-paste it into the "rslsync" config file?

 

[Helen]

Advanced folders do not have key, so I'm not sure how you got it. I suppose you just copied a part of a link, right? That won't work.

In your setup, where linux runs with config and shares are configured there, you need to use Standard folders, not Advanced. Standard folders have key, add such to Sync on Mac and just copy the key from "share" screen. 

[Marco Pracucci]

Helen,

sorry to bother you. Just to be clear: do you confirm me the linux app "rslsync" does NOT support Advanced Folders?

Marco

[Helen]

no, I do not say that rslsync does not support Advanced folder. It does. 
I say that when you use config file and setup shared_folders there, only Standard folders can be configured there. Config file does not support links, only keys (parameter "secret"), you can put only a valid secret (key) there, not link. 

if you do not configure shared_folders in config file, but rather use webui instead, you can use either -Standard or Advanced folder. 
Hope it's clear. 

[Marco Pracucci]

Ok got it.

Thanks for the help. The issue has been now solved, and I've been able to add Advanced Folders through the Web UI.