Debian And Ubuntu Server Unofficial Packages For Bittorrent Sync

[RomanZ]

@knireis

I understand that. Sorry - still can't promise anything about official packages for now. Making a minor fix in the client is the fastest thing we can do now.

 

@chrisvdb

Few params were removed from the client, while it looks like Leo's package is using all of them.

[noiime]

@Borph thanks a lot, apparently removing the "--log sync.log" did the trick and there's no need to bypass the btsync-daemon.

 

I didn't notice it because when you execute it manually with the "--log sync.log" option, it actually start so, I never thought removing that option from the init file would make it worked... weird!!?

 

So finally the workaround can be resumed in 2 steps

 

1- Edit the config file /etc/btsync/debconf-default.conf and remove  "folder_defaults.use_dht" : false,

2- Edit the init file /etc/init.d/btsync and in the "Start btsync" section, remove the --log sync.log

2- Edit the init file /etc/init.d/btsync and in the "Start btsync" section, add the complete path to the log file

 

EDIT: In fact you don't need to remove "--log sync.log" you just need to add the complete path

ie: "--log /var/lib/btsync/sync.log"

 

If you remove it btsync will no longer log anything.

I thought it would create a "sync.log" automatically somewhere but apparently it doesn't.

[Moe]

In fact it is actually the default value of BitTorrent Sync not to use DHT.

If you take a look at this article here http://help.getsync.com/customer/portal/articles/1902048-sync-advanced-preferences--more-options

I wonder why tuxpoldo is not updating it anymore..

[RomanZ]

@noiime

To ensure that folder_defaults.dht does not appear again, edit "btsync.postinst"

 

file and remove the line

"folder_defaults.use_dht" : ${FOLDER_DEFAULTS_USE_DHT},

you can also call dpkg-reconfigure btsync once so script will clean up the default config automatically.

 

So, to make 2.2.0 run as part of @tuxpoldo's btsync package, do:

1. Stop the service

2. Edit /var/lib/dpkg/info/btsync.postinst, remove line containing "folder_defaults.use_dht"

3. Edit /etc/init.d/btsync, remove --log sync.log (or replace sync.log with full path)

4. Run "dpkg-reconfigure btsync" so the script will update default config

5. Start service again

 

It worked in my lab.

[noiime]

@RomanZ

I confirm, it's working on my side too.

Thanks to you, the workaround is now completed.

Keep up your good work!!

[noiime]

Most of my peers are Debian Wheezy and I didn't have to do anything after modifying the init file.

But, apparently, on Debian Jessie it's important to do a "systemctl daemon-reload" for btsync to start after the modification to the init file.

[GreatMarko]

@knireis

I understand that. Sorry - still can't promise anything about official packages for now. Making a minor fix in the client is the fastest thing we can do now.

 

@chrisvdb

Few params were removed from the client, while it looks like Leo's package is using all of them.

 

@all, today's 2.2.1 release contains a fix for "Deprecated settings prevent Linux package built by community from starting"

[chrisvdb]

 

@all, today's 2.2.1 release contains a fix for "Deprecated settings prevent Linux package built by community from starting"

 

Thanks for updating us. Unfortunately, it's still not working for me... with all the tinkering it could be that I messed up the init file myself, though. Can someone else give it a try?

[Lazurixx]

Just curious anyone here get 2.2 running on OpenMediaVault?  Thanks

[Silvenga]

I used Btsync some time ago, but stopped when it began a subscription model. With the creation of the one-payment option I thought I would try Btsync again. Seeing that the official-unofficial packages have become a bit stale, I attempted to build my own based on the work of @tuxpoldo - upgrading along the way. 

 

So, until Mr. Moll upgrades his packages, I'm maintaining a personal fork of his repository here: https://github.com/Silvenga/btsync-deb. I'll use it for my own deployments, but anyone is free to check them out. The binaries are published to Canonical's repositories on the PPA's: https://launchpad.net/~silvenga/+archive/ubuntu/btsync

 

I've only tested btsync 2.2.1 under Ubuntu Trusty 64-bit in headless mode, but I don't anticipate any issues on other Debian based operating systems. I can add other Ubuntu distributions or CPU architectures if there's a want. 

 

Cheers!

[knireis]

I used Btsync some time ago, but stopped when it began a subscription model. With the creation of the one-payment option I thought I would try Btsync again. Seeing that the official-unofficial packages have become a bit stale, I attempted to build my own based on the work of @tuxpoldo - upgrading along the way. 

 

So, until Mr. Moll upgrades his packages, I'm maintaining a personal fork of his repository here: https://github.com/Silvenga/btsync-deb. I'll use it for my own deployments, but anyone is free to check them out. The binaries are published to Canonical's repositories on the PPA's: https://launchpad.net/~silvenga/+archive/ubuntu/btsync

 

I've only tested btsync 2.2.1 under Ubuntu Trusty 64-bit in headless mode, but I don't anticipate any issues on other Debian based operating systems. I can add other Ubuntu distributions or CPU architectures if there's a want. 

 

Cheers!

 

Thanks! Saves me a lot of time each update. 

Thanks! Saves me a lot of time each update. 

 

Forgot to ask can you add for arm cpu?   

Failed to fetch http://ppa.launchpad.net/silvenga/btsync/ubuntu/dists/trusty/Release  Unable to find expected entry 'main/binary-armel/Packages' in Release file (Wrong sources.list entry or malformed file)

[Silvenga]

Thanks! Saves me a lot of time each update. 

 

Forgot to ask can you add for arm cpu?   

Failed to fetch http://ppa.launchpad.net/silvenga/btsync/ubuntu/dists/trusty/Release  Unable to find expected entry 'main/binary-armel/Packages' in Release file (Wrong sources.list entry or malformed file)

 

I'll make a request to Launchpad to enable arm builds for this repository when I get home. However, Launchpad can only build armhf arm packages as armel is being deprecated.

 

I'll need to look into how @tuxpoldo made packages for the Pi. 

[chrisvdb]

So, until Mr. Moll upgrades his packages, I'm maintaining a personal fork of his repository here: https://github.com/Silvenga/btsync-deb. I'll use it for my own deployments, but anyone is free to check them out. The binaries are published to Canonical's repositories on the PPA's: https://launchpad.net/~silvenga/+archive/ubuntu/btsync

 

I've only tested btsync 2.2.1 under Ubuntu Trusty 64-bit in headless mode, but I don't anticipate any issues on other Debian based operating systems. I can add other Ubuntu distributions or CPU architectures if there's a want.

 

Thanks for this! Is this a drop-in replacement that should work without changing any configuration files?

[Silvenga]

Forgot to ask can you add for arm cpu?   

 

I gave up on using Launchpad. I've uploaded the packages (including ARM) to my private repository -  http://deb.silvenga.com. 

# Add my signing keyapt-key adv --keyserver keyserver.ubuntu.com --recv-keys 992A3C9A3C3DE741# Add the btsync repositoryadd-apt-repository "deb http://deb.silvenga.com/btsync any main"

Please check them out.

 

Is this a drop-in replacement that should work without changing any configuration files?

 

It should work without modifications. Btsync 2.2.1 fixes the configuration issues reported earlier (which is included in the above packages). 

Edited September 19, 2015 by Silvenga

[knireis]

I gave up on using Launchpad. I've uploaded the packages (including ARM) to my private repository -  http://deb.silvenga.com. 

# Add my signing keyapt-key adv --keyserver keyserver.ubuntu.com --recv-keys 992A3C9A3C3DE741# Add the btsync repositoryadd-apt-repository "deb http://deb.silvenga.com/btsync any main"

Please check them out.

 

 

It should work without modifications. Btsync 2.2.1 fixes the configuration issues reported earlier (which is included in the above packages). 

 

Great, thanks, works perfectly

[chrisvdb]

Great, thanks, works perfectly

 

Here as well! No config changes were required... thanks a lot!

[jbishop129]

I'm running the 1.4 Server unofficial package on 3 servers, and have ran in to a strange issue:
Server A: all R/W syncs

Server B: all R/O syncs

Server C: all R/O syncs

 

Server B and C are my read-only off-site backups. Recently I had a storage failure on Server C, and had to re-sync all of my Sync folders. the OS and therefore BTSync config was unaffected, only the mass-storage containing all the sync data. I fixed the storage, and since it was mapped to a new location, all the syncs on that node showed "Storage unavailable" (or 'path unavailable'? something like that). So I just removed the syncs from that node, then added them back in with the R/O keys from Server A. 

 

Back on Server A, the Peers list doesnt show the connection re-added from Server C (waited several hours). I thought maybe because it's the same server, and server A thinks it already has fully synced it, it's ignoring it for some reason. 

 

I went to Server A and did 'dpkg-reconfigure btsync' so I could run thru the settings, and I set the 'time to expire offline peers' to 0 days, so I would expire that failed Server C, then be able to just re-add, right? 

Things then went worse: Server A now shows no peers, even though Server B never went offline. I dpkg-reconfigure'ed again and set it back to 7 days, and peers are still all gone.

 

On Server C, i do see it re-syncing from Server B, and it shows '2 of 2' peers, with both Server A and B listed. 

 

I can't figure out how to get Server A to see the peers again... not quite sure where I went wrong (although likely my setting the peer expiration to zero was bad).

[Silvenga]

Great, thanks, works perfectly

 

Here as well! No config changes were required... thanks a lot!

 

Awesome! Feel free to email me (address on deb.silvenga.com) if I'm slow to update.

[boldstripe]

Awesome! Feel free to email me (address on deb.silvenga.com) if I'm slow to update.

 

Thanks for your effort. Will this likely work on Debian with the same signing and repository instructions?

[knireis]

Thanks for your effort. Will this likely work on Debian with the same signing and repository instructions?

 

yes, i can confirm it does

[Silvenga]

Thanks for your effort. Will this likely work on Debian with the same signing and repository instructions?

 

If anything, some minimal Debian/Ubuntu builds need the software-properties-common package to be installed for the add-apt-repository command to work. add-apt-repository is just a wrapper to automatically add sources to the /etc/apt/sources.list file and is sometimes considered superfluous, thus removed.

 

I'm not used to BBCode forums, I can figure out how to do single tics like on a Markdown style forum... So bold it is!

 

I can't figure out how to get Server A to see the peers again... not quite sure where I went wrong (although likely my setting the peer expiration to zero was bad).

 

It might be a temporary issue. You can add the servers manually using the "Predefined hosts" option on the folder. 

[Silvenga]

Added packages for Btsync 2.2.2. 

[Ted]

With some debugging I found out that the option "--log sync.log" or so caused the process to die (access rights?). At least removing helped.

 

Thanks - after changing that, the binary upgrade is working for me 

[STUBR.BS]

@Silvenga: thanks a lot for the new repository. Installing worked like a charm, I had to restore the original init.d script in order to let it run.

 

But I have the problem, that the process dies after a few minutes.... I have no idea why? I tried removing --log sync.log, but this did not resolve the issue...

 

It seems that the daemon dies, and the process is handled by the Kernel as I get active(exited) after a 

 

service btsync status

 

But the web administration doesn't work either. So I think I missed something here?

 

Any ideas?

Thanks

Bernhard

[Silvenga]

@Silvenga: thanks a lot for the new repository. Installing worked like a charm, I had to restore the original init.d script in order to let it run.

 

But I have the problem, that the process dies after a few minutes.... I have no idea why? I tried removing --log sync.log, but this did not resolve the issue...

 

Np, could you check `/tmp/sync.log`? What distro are you running and are you running it with systemd?

You could also try to dpkg-reconfigure btsync again.