Btsync Op Raspberry Pi: Merge: Failed To Verify Group Signature

[tjarra]

I've installed Btsync on my Raspberry Pi (http://blog.bittorrent.com/2013/05/23/how-i-created-my-own-personal-cloud-using-bittorrent-sync-owncloud-and-raspberry-pi/) and it works for some shares.

 

I can use only 5 of my 10 Btsync shared folders. Btsync sees all the other devices, but only displays:

0 B in 0 files

and 

Synced on 05/23/2014 13:13:53

while it never synced at all.

 

I tried to re-add the folders en tried to use the read-only and write keys. With no succes. In the clientside logs (on my Mac), I see no strange entries. In the logs on my Pi I see the following message appear:

Merge: failed to verify group signature of files message, aborting

The shares that don't work on my Pi, work fine on other devices (Other mac, Android tablet and iPhone) and contain files. 

I'm using version 1.2.67 on my Pi and 1.3.94 on my Mac.

 

 

 

[guigolum]

Hello. What is your btsinc version ? Are the folder added on some other device (edit : you say it works, sorry) ? do you have any clue in /var/lib/btsync/sync.log ?

 

Maybe you can give me a key to test ( maybe create a new folder, dump in some bin file)

to create a file(here test.bin) with given size (here 10*1MB) of random data you can use:

dd if=/dev/urandom of=test.bin bs=1M count=10

 

I had a problem with btsync on my device, mounting external network drive with permissions and resovled it by making btsync daemon run with root credentials on my rpi.

[ad89]

Hi, 

 

I have a very similar (identical problem). I have BTsync  v(1.3.94) on my mac and v(1.2.67) on my Raspberry Pi. 

I am syncing files between several macs and windows pc's with some friends and syncing works fine with all of them. 

Below several screenshots and logfiles showing the same problem. 

 

I would be very grateful for a solution to this problem. 

 

P.S. I have already tried adding some names to the .syncignore as described in this thread http://forum.bittorrent.com/topic/28625-issue-syncing-from-osx-to-linux-with-1367/page-2

 

 

Screenshot of showing that my mac sees it has not synced for some folders but fine for other folders 

https://www.dropbox.com/s/sfod8rk7dhju0md/Screenshot%202014-05-25%2018.33.51.png

 

Screenshot showing that the Raspberry Pi thinks it is done syncing but contains no data. 

https://www.dropbox.com/s/4s7aj3cm02cc1rm/Screenshot%202014-05-25%2018.34.58.png

 

 

Copy paste of my sync.log on my Raspberry Pi 

^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^$[20140525 18:16:07.067] Incoming connection from 192.168.178.15:53812[20140525 18:16:07.068] Incoming connection from 192.168.178.15:53812[20140525 18:16:07.983] Merge: failed to verify group signature of files message, aborting[20140525 18:16:08.165] Incoming connection from 192.168.178.15:53812[20140525 18:16:09.124] Merge: failed to verify group signature of files message, aborting[20140525 18:16:11.188] Incoming connection from 213.103.207.196:45356[20140525 18:16:13.126] Merge: failed to verify group signature of files message, aborting[20140525 18:16:14.300] Incoming connection from 217.122.205.131:44269[20140525 18:16:15.961] Merge: failed to verify group signature of files message, aborting[20140525 18:16:17.390] Incoming connection from 192.168.178.15:53812[20140525 18:16:17.390] Incoming connection from 192.168.178.15:53812[20140525 18:16:17.393] Incoming connection from 192.168.178.15:53812[20140525 18:16:18.277] Merge: failed to verify group signature of files message, aborting[20140525 18:16:19.326] Incoming connection from 192.168.178.15:53812[20140525 18:16:20.306] Merge: failed to verify group signature of files message, aborting[20140525 18:16:23.094] Incoming connection from 213.103.207.196:45356[20140525 18:16:26.735] Merge: failed to verify group signature of files message, aborting[20140525 18:16:27.424] Incoming connection from 192.168.178.15:53812[20140525 18:16:27.424] Incoming connection from 192.168.178.15:53812[20140525 18:16:28.436] Incoming connection from 192.168.178.15:53812[20140525 18:16:29.463] Merge: failed to verify group signature of files message, aborting[20140525 18:16:30.484] Incoming connection from 192.168.178.15:53812[20140525 18:16:31.655] Merge: failed to verify group signature of files message, aborting[20140525 18:16:36.331] Incoming connection from 213.103.207.196:45356[20140525 18:16:37.451] Incoming connection from 192.168.178.15:53812[20140525 18:16:37.451] Incoming connection from 192.168.178.15:53812[20140525 18:16:39.496] Incoming connection from 192.168.178.15:53812[20140525 18:16:41.088] Merge: failed to verify group signature of files message, aborting[20140525 18:16:41.241] Incoming connection from 192.168.178.15:53812[20140525 18:16:42.213] Merge: failed to verify group signature of files message, aborting[20140525 18:16:47.385] Incoming connection from 192.168.178.15:53812[20140525 18:16:47.386] Incoming connection from 192.168.178.15:53812[20140525 18:16:49.413] Incoming connection from 192.168.178.15:53812[20140525 18:16:50.390] Merge: failed to verify group signature of files message, aborting[20140525 18:16:51.148] Incoming connection from 213.103.207.196:45356[20140525 18:16:52.335] Incoming connection from 192.168.178.15:53812[20140525 18:16:53.021] Merge: failed to verify group signature of files message, aborting[20140525 18:16:53.876] Merge: failed to verify group signature of files message, aborting[20140525 18:16:54.250] Incoming connection from 217.122.205.131:44269

Part of my sync log on my mac 

[20140525 18:31:21.117] Send ping to peer (10DAC055A3F55F63BC232C337EFAA7D7EE4942D1) for share 7C487AA478C7EB5E3BCFEBCFB2D92A82BA7879B2:[20140525 18:31:21.117] ping 192.168.0.100:56555[20140525 18:31:21.117] Send ping to peer (10DAC055A3F55F63BC232C337EFAA7D7EE4942D1) for share 7C487AA478C7EB5E3BCFEBCFB2D92A82BA7879B2:[20140525 18:31:21.117] ping 145.118.113.229:56555[20140525 18:31:21.117] Send ping to peer (105C0C33A06D12D3890E0E4B1820460059DBF98B) for share 7C487AA478C7EB5E3BCFEBCFB2D92A82BA7879B2:[20140525 18:31:21.117] ping 192.168.1.68:47573[20140525 18:31:21.117] Send ping to peer (105C0C33A06D12D3890E0E4B1820460059DBF98B) for share 7C487AA478C7EB5E3BCFEBCFB2D92A82BA7879B2:[20140525 18:31:21.117] ping 83.117.138.253:47573[20140525 18:31:21.127] Got ping (broadcast: 1) from peer 192.168.178.24:63028 (0043A22FB2DA28ADB0109FF51EEB4BFC04F221D4) for share A805AA16D9BD308B6C06C2DB12A2A3073CC1402C[20140525 18:31:21.129] Got ping (broadcast: 1) from peer 192.168.178.24:63028 (0043A22FB2DA28ADB0109FF51EEB4BFC04F221D4) for share 405BECC6BDBC6B5439D97BCAC848144AC3C4BE38[20140525 18:31:21.134] Got ping (broadcast: 1) from peer 192.168.178.24:63028 (0043A22FB2DA28ADB0109FF51EEB4BFC04F221D4) for share EA89901DF44F22DB96CDC3986E5F9DE59F1294DD[20140525 18:31:21.136] Got ping (broadcast: 1) from peer 192.168.178.24:63028 (0043A22FB2DA28ADB0109FF51EEB4BFC04F221D4) for share 7C487AA478C7EB5E3BCFEBCFB2D92A82BA7879B2[20140525 18:31:22.137] Going to sync state with peer 192.168.178.24:63028 (0043A22FB2DA28ADB0109FF51EEB4BFC04F221D4)[20140525 18:31:22.138] Going to sync state with peer 192.168.178.24:63028 (0043A22FB2DA28ADB0109FF51EEB4BFC04F221D4)[20140525 18:31:22.138] Going to sync state with peer 192.168.178.24:63028 (0043A22FB2DA28ADB0109FF51EEB4BFC04F221D4)[20140525 18:31:22.139] Send ping to peer (106F5C4397878A535886179261AFB11183950EB5) for share 7C487AA478C7EB5E3BCFEBCFB2D92A82BA7879B2:[20140525 18:31:22.140] ping 192.168.0.13:45444[20140525 18:31:22.140] Send ping to peer (106F5C4397878A535886179261AFB11183950EB5) for share 7C487AA478C7EB5E3BCFEBCFB2D92A82BA7879B2:[20140525 18:31:22.140] ping 80.57.95.59:61325[20140525 18:31:22.140] Send ping to peer (10DAC055A3F55F63BC232C337EFAA7D7EE4942D1) for share 7C487AA478C7EB5E3BCFEBCFB2D92A82BA7879B2:[20140525 18:31:22.140] ping 192.168.0.100:56555[20140525 18:31:22.140] Send ping to peer (10DAC055A3F55F63BC232C337EFAA7D7EE4942D1) for share 7C487AA478C7EB5E3BCFEBCFB2D92A82BA7879B2:[20140525 18:31:22.140] ping 145.118.113.229:56555[20140525 18:31:22.140] Send ping to peer (105C0C33A06D12D3890E0E4B1820460059DBF98B) for share 7C487AA478C7EB5E3BCFEBCFB2D92A82BA7879B2:[20140525 18:31:22.140] ping 192.168.1.68:47573[20140525 18:31:22.140] Send ping to peer (105C0C33A06D12D3890E0E4B1820460059DBF98B) for share 7C487AA478C7EB5E3BCFEBCFB2D92A82BA7879B2:[20140525 18:31:22.140] ping 83.117.138.253:47573[20140525 18:31:22.151] Got ping (broadcast: 1) from peer 192.168.178.24:63028 (0043A22FB2DA28ADB0109FF51EEB4BFC04F221D4) for share A805AA16D9BD308B6C06C2DB12A2A3073CC1402C[20140525 18:31:22.157] Got ping (broadcast: 1) from peer 192.168.178.24:63028 (0043A22FB2DA28ADB0109FF51EEB4BFC04F221D4) for share 405BECC6BDBC6B5439D97BCAC848144AC3C4BE38[20140525 18:31:22.158] Got ping (broadcast: 1) from peer 192.168.178.24:63028 (0043A22FB2DA28ADB0109FF51EEB4BFC04F221D4) for share EA89901DF44F22DB96CDC3986E5F9DE59F1294DD[20140525 18:31:22.160] Got ping (broadcast: 1) from peer 192.168.178.24:63028 (0043A22FB2DA28ADB0109FF51EEB4BFC04F221D4) for share 7C487AA478C7EB5E3BCFEBCFB2D92A82BA7879B2[20140525 18:31:22.160] Merge: generating intial request with root 4AC44E8E1065238D1046DF3E713F3903C7799B36[20140525 18:31:22.161] Merge: generating intial request with root D63B565221D2A95CD66DCAC17685075C7702D02F[20140525 18:31:22.161] Merge: generating intial request with root 470FA4A7C8D3ABCA9C60204EAF8F23B4377EAD89[20140525 18:31:22.170] Got id message from peer DeKleineBes (0043A22FB2DA28ADB0109FF51EEB4BFC04F221D4) 1.2.67[20140525 18:31:22.170] Merge: processing root message, remote hash 4AC44E8E1065238D1046DF3E713F3903C7799B36, timediff: 0[20140525 18:31:22.170] Merge: sending get_have_pieces, prevhash: A4E5FB09C846B8DD4CE8A8BC02758E3B37D1175E[20140525 18:31:22.170] State sync finished for folder /Users/Adriaan/Sync/De Kleine Consultant Algemeen[20140525 18:31:22.172] Got id message from peer DeKleineBes (0043A22FB2DA28ADB0109FF51EEB4BFC04F221D4) 1.2.67[20140525 18:31:22.172] Merge: processing root message, remote hash 470FA4A7C8D3ABCA9C60204EAF8F23B4377EAD89, timediff: 0

[denis4inet]

Hi everyone! 

 
I have analyzed represented logs.
The error message was issued by file name encoding error on linux (RPi).

1. You can check file names on valid UTF8. 

You need iconv tool.

# cd <shared_folder_path># ls -R | iconv -f utf8 | grep illegal --color=auto

If you see message:

iconv: illegal input sequence at position

 

that mean in your file tree exists files with non-valid file names.

2. Or you can wait new releases in which this bug will be fixed.

Thanks.

[ad89]

Hi Denis4inet, 

 

I have tried locating the invalid files. 

I have both tried your method (had to replace utf8 with utf-8) and tried with a custom python script. 

In both methods it tells me there are no utf-8 invalid filenames... 

 

I do think filenames could be an issue, next thing I'm going to try to search for illegal characters. 

I don't know exactly how the decode command works but I assume it works because the files work on my OS. No clue tough, could be I'm chasing a phantom here but I kinda want this to work. 

cd <shared_folder_path>ls -R | iconv -f utf-8 | grep illegal --color=auto

import osdef loop_over_files_in_dir(directory, prnt  = False):    bad_names =[]    for dirname, dirnames, filenames in os.walk(directory):        # print path to all subdirectories first.        for subdirname in dirnames:            if prnt ==True:                print os.path.join(dirname, subdirname)            for filename in filenames:                if (test_bad_filename(filename))==False:                    bad_names.append(filename)                    if prnt ==True:                        print os.path.join(dirname, filename)    print bad_namesdef test_bad_filename(filename):    bad_filenames =[]    valid_utf8 = True    try:        filename.decode('utf-8')    except UnicodeDecodeError:        valid_utf8 = False    return valid_utf8

[tjarra]

Hi everyone! 

 

I have analyzed represented logs.

The error message was issued by file name encoding error on linux (RPi).

1. You can check file names on valid UTF8. 

You need iconv tool.

# cd <shared_folder_path># ls -R | iconv -f utf8 | grep illegal --color=auto

If you see message:

that mean in your file tree exists files with non-valid file names.

2. Or you can wait new releases in which this bug will be fixed.

Thanks.

Hi denis4inet,

 

Thank you for your response. I've tried your suggestion with no succes. I don't see any message. Hopefully this will be fixed in the next version as you say.

[denis4inet]

@tjarra,

Please, create ticket at syncapp.zendesk.com with link to this topic. You could create ticket via web-based UI or feedback feature in the BitTorrent Sync context menu.

[mitra]

I have exactly the same problem.   I see the question asked multiple times in these forums with no clear answer,

 

In my case its a Mac (1.3.106) talking to Raspberry (1.2.67)

 

If I create a file on the Raspberry it ends up on the Mac;

If I create a file on the Mac it doesn't get to the Raspberry.

btsync is running with sudo on the Raspberry.

The iconv check above doesnt show any problems, nor would I expect them - its my Mac desktop

Both these directories sync just fine with another Mac.

 

The Raspberry is putting on a USB drive formatted with ext4 as recommended here ...

http://jack.minardi.org/raspberry_pi/replace-dropbox-with-bittorrent-sync-and-a-raspberry-pi/

 

In fact, I followed those instructions exactly.

[Helen]

mitra,

 

This issue is discussed and reasons are revealed in this forum topic