Latest Sync Build: 1.1.70

[yield]

Did you try the daemon-mode? It works fine here.

Yep, with daemon mode there is no error, it just doesn't get executed.

[yield]

Yep, with daemon mode there is no error, it just doesn't get executed.

Well I changed the path from .sync to a new folder just to try like it was a new install and it worked, the problem started when I updated from 1.1.30 to 1.1.33, after that it never worked again even downgrading to 1.1.30, it's a little inconvenience because I have about 120Gb from a backup repository so apparently it's going to reindex everything again. At least 1.1.42 is up and running.

[dearnold]

1. Is 1.1.42 the beta version?

2. Auto-update doesn't seem to work for me.

3. I got an email saying that the beta version is now available. When I click the link, it takes me to a window to download the beta which turns out to be named "BTSync.exe". I download it and click on Run, etc. Error message pops up "It seems like BitTorrent Sync is already running, but not responding. Please close all BitTorrent Sync processes and try again."

Why doesn't the installer auto-close the current processes and move on to the installation, OR ask me if I want to close it myself or have the installer do it?

Running Win 7 Home Prem 64-bit on this desktop

4. I have the same experience when a window pops up saying that there is a newer version to install. I click on the link, download the .exe, Run, and get the "already running" message. Click out of that, close processes, find the .exe, blah, blah, blah.

Running Win 7 Pro on 2 other desktops and a laptop. Auto-update doesn't work on any of them.

[GreatMarko]

1. Is 1.1.42 the beta version?

Yes

2. Auto-update doesn't seem to work for me.

This is normal - but it does cause a great deal of confusion for users! It can often take several days/weeks before new builds are pushed out via auto-update. If you don't want to wait, you can always manually grab the latest build here: http://forum.bittorr...ync-build-1142/

3. I got an email saying that the beta version is now available. When I click the link, it takes me to a window to download the beta which turns out to be named "BTSync.exe". I download it and click on Run, etc. Error message pops up "It seems like BitTorrent Sync is already running, but not responding. Please close all BitTorrent Sync processes and try again."

Why doesn't the installer auto-close the current processes and move on to the installation, OR ask me if I want to close it myself or have the installer do it?

Running Win 7 Home Prem 64-bit on this desktop

Yep, I asked this several months back! It is a little frustrating, but it affects all users who manually update.

4. I have the same experience when a window pops up saying that there is a newer version to install. I click on the link, download the .exe, Run, and get the "already running" message. Click out of that, close processes, find the .exe, blah, blah, blah.

Running Win 7 Pro on 2 other desktops and a laptop. Auto-update doesn't work on any of them.

Hmmm... what version was this happening with? The auto-update feature (when it works!) should silently download the update, install, and restart Sync without additional prompts

[tenjaa]

This is normal - but it does cause a great deal of confusion for users! It can often take several days/weeks before new builds are pushed out via auto-update. If you don't want to wait, you can always manually grab the latest build here: http://forum.bittorr...ync-build-1142/

Are you a dev?! Just a question cause youre posting so much here

But even if not I need to correct this: Auto-update didnt say there is no update, instead there was an update displayed but it failed downloading it. So it was more a network error at bittorrent.com. But 5 minutes ago it worked again as intended.

[GreatMarko]

Auto-update didnt say there is no update, instead there was an update displayed but it failed downloading it. So it was more a network error at bittorrent.com. But 5 minutes ago it worked again as intended.

Well, the second point that the previous poster made, was that "Auto-update doesn't seem to work for me." There was no reference made as to whether auto-update had announced that there was an update available, but that it subsequently failed to download/install. It was therefore assumed in my response that "auto-update doesn't seem to work" was a reference to the common message that users often see when they check for updates, with the knowledge that a newer version is available, only to be informed that their client version is already up to date!

With that in mind, my response to the previous poster's point was valid.

If, however, you've been experiencing a slightly different issue to the previous poster, that of a failed/incomplete download, it's quite possible that there has been a higher than usual demand on BitTorrent's servers/infrastructure over the past couple hours, given that Sync has just gone into "beta". As you say though, you have now been able to download, but this is a likely explanation as to why your download may have failed for you earlier, given potentially higher than usual levels of traffic.

[maartenvc]

What version are you updating from? What error are you seeing? You can also manually obtain the latest build here

it was latest version 1.1.33

There was a nice message update available.

Next error was: "There was a problem downloading BTSync. ..."

works ok now

[GreatMarko]

it was latest version 1.1.33

There was a nice message update available.

Next error was: "There was a problem downloading BTSync. ..."

works ok now

Great! Glad it's working for you now! I suspect your earlier issue was due to higher than usual traffic levels to BitTorrent's servers, given that Sync has literally just gone into "beta" in the last few hours!

[dearnold]

Great Marko - thanks for your reply. your response to my point 2 was entirely on point.

to my point 3 - now I understand why it is happening and I have been doing the manual download and update (I"m not a patient person). Do you know if this is going to be "fixed"?

point 4 - this happened just now on my laptop which had been running ver 1.1.30. This isn't the first time I've seen it, but I didn't note the versions or bother to mention it.

[GreatMarko]

to my point 3 - now I understand why it is happening and I have been doing the manual download and update (I"m not a patient person). Do you know if this is going to be "fixed"?

I hope so, as I agree, it's a little frustrating! That said, once the auto-update feature is fully working/implemented, and new builds are made available through that mechanism much sooner after they are released than at present, the need to manually download/install if you really can't wait to get your hands on the next build should be negated!

point 4 - this happened just now on my laptop which had been running ver 1.1.30. This isn't the first time I've seen it, but I didn't note the versions or bother to mention it.

Hmmm.. not sure on this one to be honest! Two thoughts spring to mind though;

Firstly, I wonder that maybe if the "silent" in-place update fails for some reason that it then reverts to the standard "full" installer, which is why you then see the various dialogs and "sync is already running" message?

The other thought would be that if your devices are "slow", and the updater attempts to automatically close a running Sync copy before proceeding with its silent update, if the Sync task hasn't exited/terminated in a timely fashion, the updater detects that Sync is still running, and you'll see a message accordingly.

[neumann]

When updating to the newest version 1.1.42, it seems there is a problem.When clicking the bittorrent sync icon I get this message:

It seems like BitTorrent Sync is allready running, but not responding. Please close all BitTorrent Sync processes and try Again.

I've tried to close all running instances of bittorrent sync, but without success.

The same happens on both on an Win XP and Win7 machines I've updated.

Any idea?

[vadimt]

Could you please specify your BTSync version you have before update?

Thanks!

[neumann]

I don't remember. But since i have upgrade everytime i've been informered of a new build, i have upgraded. So it's The latest version before 1.1.42.

And whenever I click the icon, I get the message. So I can't check the version.

[neumann]

The version was 1.0.134. I have tried to uninstall the program on 2 maschines and reinstall. But no luck. I saw that the automatic upgrade hadn't uninstalled the old version.

The problem is the same on 4 different machines I'm running with bittorrent sync. The fifth machine is a ubuntu server, which is my master. The upgrade on this will wait until the other problem is solved.

[shawnman]

I noticed that the Android APK version linked here is 1.1.21 but in the play store you get v1.1.23. Also noticed that in version 1.1.21 under the BACKUP tab, when you add a folder it shows you the RO key but when you click email, it will send out only the RW key. In version 1.1.23 it shows and only send the RO key. I can't seem to get the RW key at all in v1.1.23 from the BACKUP tab folders.

I know I could add the same folders under the SYNC tab and create my keys from the desktop.

Is there any intended difference from the SYNC & BACKUP tabs?

Guess I'm just mentioning all this as I'm curious what the thought process is from the developers, etc. going forward.

Thanks.

[tuxpoldo]

Using version 1.1.42 I have very heavy CPU load on Mac OSX 1.8.3

Any Idea?

[tomtom]

I still have the problem that after a while synchonisation stops. The device Tab ist empty. Changing the listening port helps. Any ideas? I use Build 1.1.42

[biggles621]

Update to 1.1.42 worked very well on WIn 72 32 & 64 bit.

But on 64bit version there is still a memory leak - starts at around 30K and gradually increases to beyond 100k.

On 32bit it stays around 30K

[joebush]

I noticed that the Android APK version linked here is 1.1.21 but in the play store you get v1.1.23. Also noticed that in version 1.1.21 under the BACKUP tab, when you add a folder it shows you the RO key but when you click email, it will send out only the RW key. In version 1.1.23 it shows and only send the RO key. I can't seem to get the RW key at all in v1.1.23 from the BACKUP tab folders.

I know I could add the same folders under the SYNC tab and create my keys from the desktop.

Is there any intended difference from the SYNC & BACKUP tabs?

That's strange. I installed 1.1.21 on my 3 devices, and none seemed to have a RW key.

Backup seems to be a default RO sync from the source. I have gotten the impression in other threads that the intention in the future could be to be able to recover. Until (if) that happens, Backup isn't anything more than a sync that is forced to be RO.

[fukawi2]

It seems there may be a memory leak on ARM as well. Since updating to 1.1.42 on my Raspberry Pi, the OOM killer keeps killing btsync off. This wasn't a problem prior to 1.1.42, and the Pi is dedicated to btsync (clean image of Raspbian + btsync)

[582005.827783] [ pid ]   uid  tgid total_vm      rss nr_ptes swapents oom_score_adj name
[582005.827821] [  154]     0   154      720        1       5      133         -1000 udevd
[582005.827839] [  260]     0   260      719        1       5      134         -1000 udevd
[582005.827857] [  279]     0   279      719        1       5      134         -1000 udevd
[582005.827877] [ 1540]     0  1540      436        5       5       16         -1000 ifplugd
[582005.827895] [ 1545]     0  1545      436        5       5       16         -1000 ifplugd
[582005.827911] [ 1605]     0  1605     1223        1       5      429             0 dhclient
[582005.827928] [ 1914]     0  1914     6992       54       7       54             0 rsyslogd
[582005.827945] [ 1978]     0  1978      948       10       5       31             0 cron
[582005.827961] [ 2015]   104  2015      794        1       5       68             0 dbus-daemon
[582005.827978] [ 2090]     0  2090     1552        1       6      105         -1000 sshd
[582005.827995] [ 2116] 65534  2116      503        4       4       26             0 thd
[582005.828013] [ 2127]     0  2127      935        1       6       31             0 getty
[582005.828029] [ 2128]     0  2128      935        1       5       31             0 getty
[582005.828045] [ 2129]     0  2129      935        1       6       31             0 getty
[582005.828062] [ 2130]     0  2130      935        1       4       31             0 getty
[582005.828078] [ 2131]     0  2131      935        1       6       31             0 getty
[582005.828094] [ 2132]     0  2132      935        1       5       31             0 getty
[582005.828110] [ 2133]     0  2133      515        1       5       30             0 getty
[582005.828127] [ 2209]   102  2209     1344       26       6       77             0 ntpd
[582005.828145] [ 2216]     0  2216     6886        1      10      276             0 console-kit-dae
[582005.828161] [ 2283]     0  2283     5571        1       8      119             0 polkitd
[582005.828178] [ 5034]     0  5034     2450        1       7      155             0 sshd
[582005.828195] [ 5039]  1000  5039     2450       90       7      126             0 sshd
[582005.828212] [ 5040]  1000  5040     1359        1       6      265             0 bash
[582005.828229] [ 5065]  1000  5065     1167       73       6       24             0 top
[582005.828248] [ 5492]  1000  5492   113091    72500     209    23371             0 btsync
[582005.828262] Out of memory: Kill process 5492 (btsync) score 640 or sacrifice child
[582005.828279] Killed process 5492 (btsync) total-vm:452364kB, anon-rss:289988kB, file-rss:12kB

[deadbrain]

It is a bit confusing that the android version is not aligned with the other desktop versions.

So now there is a 1.1.42 desktop version and 1.1.21 (or is the 1.1.23?) android version.

I wonder why...

[GreatMarko]

It is a bit confusing that the android version is not aligned with the other desktop versions.

So now there is a 1.1.42 desktop version and 1.1.21 (or is the 1.1.23?) android version.

I wonder why...

It's just different development cycles as the two versions of developed by different sub-teams. The difficulty is that if a bug is found in say the Android version, but doesn't affect the desktop version, obviously the android version would be "bumped" up, but the desktop version wouldn't (it would be more work to push new builds for every platform if say just the android build changed!). The alternative would be to wait and not release builds as quickly just in order to keep version numbers the same across platforms.

In an ideal world though, yes, all the version numbers would be the same!

(btw, latest Android version is 1.1.23)

[vadimt]

Using version 1.1.42 I have very heavy CPU load on Mac OSX 1.8.3

Any Idea?

Hi!

Could you please create dump file of BT sync process while it uses a lot of CPU and send it to us (syncapp@bittorrent.com)?

Please run Activity Monitor, select BitTorrent Sync process --> Sample Process --> Save. Then attach created file to email and send us.

Thanks!

[ismail]

With 1.1.48 getting a lot of these in the sync log:

[20130623 18:15:51.108] SyncDb: failed to execute query to save file info - 1

[sergey@bt]

With 1.1.48 getting a lot of these in the sync log:

[20130623 18:15:51.108] SyncDb: failed to execute query to save file info - 1

What is your operation system? Is it the only error you see?