shaman

Hash doesn't match. Terminate.

Recommended Posts

Hi,

I am having troubles getting btsync to work on one of my computers. It starts ok, it finds peers and peers find this computer byt it syncs nothing. I found this message in the logfiles:

"Hash doesn't match. Terminate."

What does it mean and how can I fix it?

It is Win7, x64. On other machines with the same OS no problem. Can it be some library missing, outdated...?

Thanks for help!

Share this post


Link to post
Share on other sites

I though that if the peers are found and visible to each other they must have the same secret. If I would enter wrong secret the peers would not connect because they will not find each other, am I right? But they find each other, I can see this peer on other computers (only IP address, not device name - not sure if this matters), but the synch does not start. I also see on other peers that they wait to upload the directory - there is arrow pointin up and dir size.

Any other ideas?

Share this post


Link to post
Share on other sites

It would be helpful if someone could tell me from which part of code this message comes from. I have some programming experience so it may point me to the right direction. There must be some reason why on this single computer it is not working...

Thanks!

Share this post


Link to post
Share on other sites

I know that it is closed source, of course. I was asking because if this comes from e.g. file validation it may be different problem than if it comes from some connection handling. Now I am totally blind, the message itself is very general and could mean anything.

Share this post


Link to post
Share on other sites

Do you have two instances of BTSync running? I ran into that today, everything looked correct, but it just wasn't syncing. I noticed I had two processes going, and once I closed one, the syncs started.

Unfortunately I didn't check the debug logs.

Share this post


Link to post
Share on other sites

I noticed one suspicious thing. In the sync.dat file there is string fileguard40:<some hash>, where on the working computers is something looking like real hash, but on the non working computer there are all zeroes and 7 at end. This looks like the hash is not generated properly. Why?

Share this post


Link to post
Share on other sites

I think it means that the hash of the secret isn't matching with your peers. So maybe you set up another computer with incorrect secret?

no i don't thing so, because for the devices to find each other they need the same key

Share this post


Link to post
Share on other sites

I noticed one suspicious thing. In the sync.dat file there is string fileguard40:<some hash>, where on the working computers is something looking like real hash, but on the non working computer there are all zeroes and 7 at end. This looks like the hash is not generated properly. Why?

well try to delete all config files and start from zero, check if it persists.

and report back

Share this post


Link to post
Share on other sites

FWIW, I'm having the same problem on a 64-bit Win7 machine, down to there being a long string of zeros terminated with 7 in the first line of sync.dat after "fileguard40:"

Basically, the following interaction takes place periodically:

[...]

[2013-04-30 17:14:24] Sending broadcast ping for share 08E942A81E7902731D380771C18BF8BC98B0B965

[2013-04-30 17:14:25] Sending broadcast ping for share 08E942A81E7902731D380771C18BF8BC98B0B965

[2013-04-30 17:14:26] Going to sync state with peer 192.168.1.81:55506 (627ED77E0B743645905DE0671900B1FC2F485AA4)

[2013-04-30 17:14:26] Merge: generating intial request with root 0000000000000000000000000000000000000000

[2013-04-30 17:14:26] Sending broadcast ping for share 08E942A81E7902731D380771C18BF8BC98B0B965

[2013-04-30 17:14:27] State sync finished for folder G:\foobar

[2013-04-30 17:14:27] Got ping (broadcast: 0) from peer 192.168.1.81:55506 (627ED77E0B743645905DE0671900B1FC2F485AA4) for share 08E942A81E7902731D380771C18BF8BC98B0B965

[2013-04-30 17:14:27] Found peer for folder G:\foobar 627ED77E0B743645905DE0671900B1FC2F485AA4 192.168.1.81:55506 direct:1

[2013-04-30 17:14:27] Sending broadcast ping for share 08E942A81E7902731D380771C18BF8BC98B0B965

[...]

What raises questions in my mind is that there are ~450 MB of files to move, which is not happening.

If you feel another set of log files is of value, please let me know. In the meantime, I'll be monitoring this thread.

Share this post


Link to post
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.