Latest Desktop Build 2.3.1

GreatMarko · February 2, 2016

Dear community,

Sync 2.3.1 is now available. You can get it via direct links below, via official download page or via "Check now" button. Auto-update is not available yet.

Direct Download Links:

Installer for Windows: x86 installer x64 installer
Package for OS X: OS X package
Gzip archive for Linux: arm armhf i386 x64 glibc23_i386 glibc23_x64
Gzip archive for FreeBSD: i386 x64

A list of what's new, improved, changed, and fixed in this version is available in the change log.

Latest Android build is now also available via direct link: 2.3.2 APK
Latest Raspberry Pi package is available via direct link: 2.3.1 DEB

Known issues and peculiarities:
- Linux users please note: starting from 2.3.0, Sync now creates and uses storage folder (.sync folder) in current directory, not next to binary

Edited February 2, 2016 by RomanZ
Fixed Android link and added info about "Check now" update

Andy+ · February 3, 2016

20 hours ago, GreatMarko said:

.........starting from 2.3.0, Sync now creates and uses storage folder (.sync folder)..........

I don´t understand, because the folder ".sync" is not new. What is the news for this?

Andy+ · February 3, 2016

Your versioning is not clear for me. Hours ago you present here version 2.3.1 and for Synology since days I can load e.g. bittorrentsync_x86_2.3-1.spk with "2.3-1" in the name. So I´m confused and don´t know, if bittorrentsync_x86_2.3-1.spk now is BTsync version 2.3.1.

Helen · February 4, 2016

17 hours ago, Andy+ said:

I don´t understand, because the folder ".sync" is not new. What is the news for this?

It's not the news, it's warning about "known issue" - that storage on Linux is created in current directory.

16 hours ago, Andy+ said:

Your versioning is not clear for me. Hours ago you present here version 2.3.1 and for Synology since days I can load e.g. bittorrentsync_x86_2.3-1.spk with "2.3-1" in the name. So I´m confused and don´t know, if bittorrentsync_x86_2.3-1.spk now is BTsync version 2.3.1.

Updated packages for NASes, new ones are %2.3.1-1.spk for Synology.

a181855 · February 4, 2016

I'm on a Raspberry Pi.

I run using

/usr/local/bin/btsync --config /usr/local/etc/btsync.conf --log /var/log/btsync.log

After upgrade to 2.3.1 (259) I now get (I have a custom config file which I have disabled web UI):

**** ERROR ****
**** Unable to listen for HTTP traffic on port 0.  Exiting...

Edited February 4, 2016 by a181855

Moe · February 4, 2016

Well you got it right there...

can you post your configuration file so we can check it and point out what could be wrong here

a181855 · February 5, 2016

Moe, the config file has not changed between updates. But here it is:

{
  "device_name": "ADevice",
  "listening_port" : 6134, // 0 - randomize port

/* storage_path dir contains auxilliary app files if no storage_path field: .sync dir created in the directory
   where binary is located. otherwise user-defined directory will be used */
  "storage_path" : "/usr/local/var/btsync",

/* set location of pid file */
  "pid_file" : "/var/run/btsync.pid",

/* use UPnP for port mapping */
  "use_upnp" : false,

/* limits in kB/s. 0 - no limit */
  "download_limit" : 0,
  "upload_limit" : 0,

  "shared_folders" :
  [
    {
      "secret" : "ASecret********", // required field - use --generate-secret in command line to create new secret
      "dir" : "/mnt/EXTDRIVE/BTSync/BTBox", // * required field
      "use_relay_server" : false, //  use relay server when direct connection fails
      "use_tracker" : false,
      "use_dht" : false,
      "search_lan" : true,
      "use_sync_trash" : true, // enable SyncArchive to store files deleted on remote devices
      "overwrite_changes" : false, // restore modified files to original version, ONLY for Read-Only folders
      "known_hosts" : // specify hosts to attempt connection without additional search
      [
        //"192.168.2.13:44444"
      ]
    }

    ,{
      "secret" : "BSecret*********", // required field - use --generate-secret in command line to create new secret
      "dir" : "/mnt/EXTDRIVE/BTSync/SnowberryCamera", // * required field
      "use_relay_server" : false, //  use relay server when direct connection fails
      "use_tracker" : false,
      "use_dht" : false,
      "search_lan" : true,
      "use_sync_trash" : false, // enable SyncArchive to store files deleted on remote devices
      "overwrite_changes" : true // restore modified files to original version, ONLY for Read-Only folders
    }

    ,{
      "secret" : "BSecret2*********", // required field - use -$
      "dir" : "/mnt/EXTDRIVE/BTSync/Notebooks", // * required field
      "use_relay_server" : false, //  use relay server when direct connection f$
      "use_tracker" : false,
      "use_dht" : false,
      "search_lan" : true,
      "use_sync_trash" : false, // enable SyncArchive to store files deleted on $
      "overwrite_changes" : true // restore modified files to original version,$
    }

  ]


/* Advanced preferences can be added to config file. Info is available at "http://help.getsync.com/customer/portal/articles/1902048-sync-advanced-preferences--more-options"
For example see folder_rescan_interval below */
//, "folder_rescan_interval" : "86400"

}

Note: The Secrets are valid folder keys, I have hidden them for this post.

I also find that btsync keeps warning that the flag use_dht is deprecated, but the --dump-sample-config flag still produces a config with this flag in. But this warning has been around a while, it was not shutting down due to that.

Edited February 5, 2016 by a181855

Remirus · February 5, 2016

a181855, we checked why it happens. Looks like webui launched even if you didn't specify it in the config file, but in IPv6 instead of IPv4. Probably your device or OS doesn't support and shows the error. We're investigating why it happens.

Also thank you for reporting that sample config contains "use_dht" option, it will be removed in future versions.

a181855 · February 5, 2016

Thanks Remirus. I'm using a vanilla Raspberry Pi (1) B+ with Noobs OS + a Wifi Dongle, if that helps. Also what is the alternative to use_dht, if that is being removed

Edited February 5, 2016 by a181855

chmars2020 · February 7, 2016

I was still running 2.2.7 since I had not received an update notification. Is there anyway to reliably get informed about new Sync versions?

GreatMarko · February 7, 2016

3 hours ago, chmars2020 said:

Is there anyway to reliably get informed about new Sync versions?

Yes - by checking the latest pinned "Latest desktop build..." thread at top of this forum.

The latest version is currently 2.3.1, however - as mentioned in the topic starter - this isn't yet available via auto-update. The latest build available via auto-update is presently 2.2.7. The latest build available via manual update is 2.3.1. 2.3.1 will likely be pushed via auto-update in the coming days/weeks.

a181855 · February 8, 2016

Anyway I can I get hold of the 2.2.7 release please for ARM, since 2.3.1 has bricked my setup.

GreatMarko · February 8, 2016

56 minutes ago, a181855 said:

Anyway I can I get hold of the 2.2.7 release please for ARM, since 2.3.1 has bricked my setup.

Yes - please see earlier "Latest desktop build..." threads for links.

Remirus · February 8, 2016

a181855, I've created a ticket in our support system. Let's continue our discussion there.

steinbitglis · February 9, 2016

We're getting crashes after about 1 min. of operation with 2.3.1 (Linux, i386) on a 32-bit machine, so we had to roll back.

There's no relevant messages in the log, except there seems to be an access violation on the c-side (invalid pointer or array or something).

EDIT:

Quote

terminate called after throwing an instance of 'std::bad_alloc'

Edited February 9, 2016 by steinbitglis
Added error message quote.

RomanZ · February 9, 2016

@steinbitglis Any core dumps? They should be either in Sync storage folder, or next to binary or see "/proc/sys/kernel/core_pattern" file for its location.

steinbitglis · February 10, 2016

Here's what I found: BTSyncForum

RomanZ · February 12, 2016

@steinbitglis Thanks. Please approve my computer and I'll take a look at dumps.

steinbitglis · February 12, 2016

Done.

steinbitglis · February 12, 2016

I can reproduce the crash on demand if it helps.

RomanZ · February 15, 2016

@steinbitglis Thanks for dumps. We'll check if they are enough to find the root cause of the crash.

iranzo · February 26, 2016

Hi,

I get something similar while running btsync on a kernel without ipv6

once I do "modprobe ipv6", btsync starts as expected.

Regards,

Pablo

Sign In

Latest Desktop Build 2.3.1

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation