Debian And Ubuntu Server Unofficial Packages For Bittorrent Sync


Recommended Posts

Try this:

 

dpkg -L btsyncsudo ls -la /etc/init.d/b*
btsync:~$ dpkg -L btsync/./etc/etc/init.d/etc/init.d/btsync/etc/btsync/etc/btsync/samples/etc/btsync/samples/user.conf/etc/btsync/samples/simple.conf/etc/default/etc/default/btsync/var/var/lib/var/lib/btsync/usr/usr/share/usr/share/icons/usr/share/icons/hicolor/usr/share/icons/hicolor/96x96/usr/share/icons/hicolor/96x96/apps/usr/share/icons/hicolor/96x96/apps/btsync.png/usr/share/icons/hicolor/48x48/usr/share/icons/hicolor/48x48/apps/usr/share/icons/hicolor/48x48/apps/btsync.png/usr/share/icons/hicolor/32x32/usr/share/icons/hicolor/32x32/apps/usr/share/icons/hicolor/32x32/apps/btsync.png/usr/share/icons/hicolor/16x16/usr/share/icons/hicolor/16x16/apps/usr/share/icons/hicolor/16x16/apps/btsync.png/usr/share/btsync/usr/share/doc/usr/share/doc/btsync/usr/share/doc/btsync/README.Debian/usr/share/doc/btsync/CREDITS.md/usr/share/doc/btsync/README.md.gz/usr/share/doc/btsync/copyright/usr/share/doc/btsync/changelog.Debian.gz/usr/lib/usr/lib/btsync/etc/btsync/samples/complex.conf/usr/lib/btsync/btsync-daemon@btsync:~$ sudo ls -la /etc/init.d/b*-rwxr-xr-x 1 root root 1276 Oct 15  2012 /etc/init.d/bootlogs-rwxr-xr-x 1 root root 1281 Jul 14  2013 /etc/init.d/bootmisc.sh@btsync:~$
Link to post
Share on other sites
  • Replies 802
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

BTSYNC PACKAGES FOR DEBIAN, UBUNTU AND OTHER DERIVED DISTRIBUTIONS BitTorrent® Inc. delivers for Linux users only a raw binary file without any deployment concept or setup system. It's up to the user

Released new packages 1.1.82-1 with some bugfixes and many additions. Beside of the upstream update to 1.1.82, this release adds the powerpc architecture both for btsync and btsync-user packages. Furt

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 package

Posted Images

btsync:~$ dpkg -L btsync/./etc/etc/init.d/etc/init.d/btsync...

OK - your installation archive is OK

 

...@btsync:~$ sudo ls -la /etc/init.d/b*-rwxr-xr-x 1 root root 1276 Oct 15  2012 /etc/init.d/bootlogs-rwxr-xr-x 1 root root 1281 Jul 14  2013 /etc/init.d/bootmisc.sh@btsync:~$

But nothing has been installed. I really have no idea what's the problem on your machine. So I have now only two possible suggestions for you:

1. You can try a real hard uninstall and reinstall. But this will kill all your internal status data of btsync (in case there was a previous version installed). If this is OK for you:

 

sudo apt-get --yes --purge remove btsync btsync-commonsudo apt-get --yes --purge autoremovesudo apt-get --yes install btsync
2. If this does not help, or you cannot effort to lose the internal configuration data of btsync, I can offer to analyse the problem together with you by a screen sharing (TeamViewer) or SSH session. You should contact me by E-Mail (leo.moll@yeasoft.com) for details.
Link to post
Share on other sites

Thanks, tuxpoldo. Your last suggestion helped. After purging install completed successfully.

 

One little thing I noticed: you have to re-run dpkg-reconfigure btsync manually after initial configuration to set umask & listening port because.

 

That's correct. Setting the UMASK is considered as an advanced setting. During initial installation, only the most important settings are asked.

Link to post
Share on other sites

Hello,

 

I'm using Linux Mint 13 (= Ubuntu 12.04), and I face the following issue when I update from the PPA or install:

desktop ~ # apt-get --yes install btsyncLecture des listes de paquets... FaitConstruction de l'arbre des dépendances       Lecture des informations d'état... FaitLes paquets supplémentaires suivants seront installés :   btsync-commonPaquets suggérés :  bind-shimLes NOUVEAUX paquets suivants seront installés :  btsync btsync-common0 mis à jour, 2 nouvellement installés, 0 à enlever et 4 non mis à jour.Il est nécessaire de prendre 0 o/5.661 ko dans les archives.Après cette opération, 8.570 ko d'espace disque supplémentaires seront utilisés.Préconfiguration des paquets...Sélection du paquet btsync-common précédemment désélectionné.(Lecture de la base de données... 371701 fichiers et répertoires déjà installés.)Dépaquetage de btsync-common (à partir de .../btsync-common_1.4.72-1_amd64.deb) ...Sélection du paquet btsync précédemment désélectionné.Dépaquetage de btsync (à partir de .../btsync_1.4.0-1_all.deb) ...Traitement des actions différées (« triggers ») pour « hicolor-icon-theme »...Traitement des actions différées (« triggers ») pour « ureadahead »...Paramétrage de btsync-common (1.4.72-1) ...Paramétrage de btsync (1.4.0-1) ...dpkg : erreur de traitement de btsync (--configure) : le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1Des erreurs ont été rencontrées pendant l'exécution : btsyncE: Sub-process /usr/bin/dpkg returned an error code (1)

Sorry, it is in French, but it just says that dpkg returned and error while treating btsync. I tried to purge everything and reinstall from scratch, same issue.

 

dpkg log is not more verbose (/var/log/dpkg.log):

2014-09-02 19:48:45 configure btsync-common 1.4.72-1 <aucun>2014-09-02 19:48:45 status unpacked btsync-common 1.4.72-12014-09-02 19:48:45 status half-configured btsync-common 1.4.72-12014-09-02 19:48:45 status installed btsync-common 1.4.72-12014-09-02 19:48:45 configure btsync 1.4.0-1 <aucun>2014-09-02 19:48:45 status unpacked btsync 1.4.0-12014-09-02 19:48:45 status unpacked btsync 1.4.0-12014-09-02 19:48:45 status unpacked btsync 1.4.0-12014-09-02 19:48:45 status unpacked btsync 1.4.0-12014-09-02 19:48:45 status unpacked btsync 1.4.0-12014-09-02 19:48:45 status half-configured btsync 1.4.0-1

dpkg-reconfigure does not work:

desktop ~ # dpkg-reconfigure btsync/usr/sbin/dpkg-reconfigure: btsync est cassé ou partiellement installé

It says that btsync is broken or partially installed.

 

 

However, btsync works fine, it is accessible without any issue, the synchronization works perfectly.

Edited by Rizzo96
Link to post
Share on other sites

Hello,

 

I'm using Linux Mint 13 (= Ubuntu 12.04), and I face the following issue when I update from the PPA or install:

...

dpkg-reconfigure does not work:

desktop ~ # dpkg-reconfigure btsync/usr/sbin/dpkg-reconfigure: btsync est cassé ou partiellement installé
It says that btsync is broken or partially installed.

 

 

However, btsync works fine, it is accessible without any issue, the synchronization works perfectly.

This error has already been reported and fixed. See this forum post.

 

Unfortunately the PPA builds are still not available, since Launchpad seems to be really busy and it will probably take a lot of time before the updates are available.

 

PLEASE DO NOT USE THE PPA IF POSSIBLE. IT HAPPENS MORE AND MORE OFTEN THAT IT TAKES HOURS/DAYS FOR UPDATES TO BE PUBLISHED THERE.

 

PLEASE USE THE YEASOFT REPOSITORY SINCE THIS IS THE MAIN REPOSITORY AND UPDATES ARE AVAILABLE IMMEDIATELY AFTER RELEASE. SEE THE INITIAL POSTING FOR DETAILS.

Link to post
Share on other sites

This error has already been reported and fixed. See this forum post.

 

Unfortunately the PPA builds are still not available, since Launchpad seems to be really busy and it will probably take a lot of time before the updates are available.

 

PLEASE DO NOT USE THE PPA IF POSSIBLE. IT HAPPENS MORE AND MORE OFTEN THAT IT TAKES HOURS/DAYS FOR UPDATES TO BE PUBLISHED THERE.

 

PLEASE USE THE YEASOFT REPOSITORY SINCE THIS IS THE MAIN REPOSITORY AND UPDATES ARE AVAILABLE IMMEDIATELY AFTER RELEASE. SEE THE INITIAL POSTING FOR DETAILS.

 

Indeed, I thought the PPA was already up-to-date. Anyway, a complete purge was necessary to get the installation working; an apt-get update was failing with the same error.

Link to post
Share on other sites

Anyone else getting this error message on upgrading to 1.4.72-1?:

 

          symbol lookup error: ./btsync-core: undefined symbol: _ZNSs4_Rep20_S_empty_rep_storageE
 
Also:
 
          Autostarting btsync instance 'debconf-default':Failed to start btsync instance debconf-default - please check the configuration file /etc/btsync/debconf-default.conf failed!
 
I have two AMD64 servers in sync, one of them is a Wheezy which upgraded fine. The other is a Lenny that's got the above problems.
 
Am using these sources:
 
 
Anyone else got similar problems? Anyone found a solution?
 
I've purged the software multiple times but still not getting anywhere.
 
I did see someone mentioning something similar here: http://forum.bittorrent.com/topic/31437-btsync-1475-i386-crash-on-readynas-pro/ - but they don't seem to have been answered.
 
Thanks,
 
Alex
Link to post
Share on other sites

I'm afraid that the toolchain of Debian "lenny" is too old (See http://gcc.gnu.org/ml/gcc/2013-02/msg00239.html) and does not provide the required function. Sorry - no chance.

 

Since there is a lot of people really angry about 1.4, I'm seriously thinking about providing a repository with the latest 1.3 based packages (there is an info, that 1.3.109 is fully compatible with the 1.4 protocol...) .....

Link to post
Share on other sites

hi tuxpoldo!

 

thank you for this wonderfully easy to use package! I've installed it on two vservers running debian wheezy and a raspbian system. the raspberry shows the updated web-ui whereas the two vservers show the old one. oddly enough all three systems gave me the new options to configure advanced settings after install.. do you have any idea why this is happening? 

 

Okay, I fixed it by removing btsync and btsync-common, a reboot and reinstalling it again. Thanks anyway! :)

Edited by s1ckb0y
Link to post
Share on other sites

hi tuxpoldo!

 

thank you for this wonderfully easy to use package! I've installed it on two vservers running debian wheezy and a raspbian system. the raspberry shows the updated web-ui whereas the two vservers show the old one. oddly enough all three systems gave me the new options to configure advanced settings after install.. do you have any idea why this is happening? 

 

I noticed that under certain circumstances the daemon does not really stop (on update/reconfiguration). Can you please restart/reboot the affected machines? As an alternative you can try to kill the daemon(s) manually and then restart them:

sudo pkill btsync-daemonsudo service btsync restart

I'm investigating the issue... See Issue #149

Edited by tuxpoldo
Link to post
Share on other sites

Yeah, this seems to be the problem..

 

Maybe this has been asked and answered before – SSL for web UI doesn't seem to work. The web pages doesn't load. Any ideas? Thank you!

 

Edit: It does work with chrome.. only safari seems to malfunction. (OS X)

 

I am too fast... Never mind!

Edited by s1ckb0y
Link to post
Share on other sites

Yeah, this seems to be the problem..

 

Maybe this has been asked and answered before – SSL for web UI doesn't seem to work. The web pages doesn't load. Any ideas? Thank you!

 

I tested it here on different platforms (btsync 1.4.72 installed with my btsync package) on several platforms (amd64,i386 both Ubuntu 12.04, 14.04 and Debian 7) and different browsers (Google Chrome on Mac OSX, Google Chrome on Debian) and it worked for me with the automatically created self signed certificate... Perhaps your browser is blocking it?

Link to post
Share on other sites

I tested it here on different platforms (btsync 1.4.72 installed with my btsync package) on several platforms (amd64,i386 both Ubuntu 12.04, 14.04 and Debian 7) and different browsers (Google Chrome on Mac OSX, Google Chrome on Debian) and it worked for me with the automatically created self signed certificate... Perhaps your browser is blocking it?

 

Yes, could be the case. I've disabled adblock and Ghostery and it seems to work alright. 

Link to post
Share on other sites

Ghostery is also installed on my browser, but it does not block it. I suppose that adblock is the problem... Maybe you can put the Web UI on the whitelist (in case adblock supports whitelists)?

 

It does and I whitelisted those sites. Now everything works beautifully and I even don't have endless syncs because of the resource forks of os x. Thank you very much for your kind support. I am really happy right now :)

Link to post
Share on other sites

I'm afraid that the toolchain of Debian "lenny" is too old (See http://gcc.gnu.org/ml/gcc/2013-02/msg00239.html) and does not provide the required function. Sorry - no chance.

 

Since there is a lot of people really angry about 1.4, I'm seriously thinking about providing a repository with the latest 1.3 based packages (there is an info, that 1.3.109 is fully compatible with the 1.4 protocol...) .....

 

Yes please Tuxpolodo, a 1.3 repository would be great.

 

I installed BTSync via these repositories on Saturday so I've had 4 days of falling head-over-heels in love with how simple it makes keeping a bunch of servers in sync.

 

:)

Link to post
Share on other sites

I'm having a problem on two Ubuntu 14.04 boxes after the latest btsync update:

 

hostname$ btsync start
hostname$ BitTorrent Sync forked to background. pid = 8506. default port = 8888
WARNING:root:Communication Error caught, displaying error message
WARNING:root:Communication Error caught, displaying error message
 
I also have an exclamation mark in the btsync icon and and error message: Communication Error 400.
 
Is this a known issue?

I was able to fix it by removing btsync* and reinstalling it from the yeasoft PPA.
Link to post
Share on other sites

Yes please Tuxpolodo, a 1.3 repository would be great.

 

I installed BTSync via these repositories on Saturday so I've had 4 days of falling head-over-heels in love with how simple it makes keeping a bunch of servers in sync.

 

:)

 

OK - Here it comes. Execute the following commands:

`which sudo` apt-key adv --keyserver keys.gnupg.net --recv-keys 6BF18B15echo deb http://debian.yeasoft.net/btsync13 experimental main > ~/btsync.listecho deb-src http://debian.yeasoft.net/btsync13 experimental main >> ~/btsync.list`which sudo` mv ~/btsync.list /etc/apt/sources.list.d/btsync.list`which sudo` chown root:root /etc/apt/sources.list.d/btsync.list`which sudo` apt-get update

Please keep in mind, that the internal database of 1.4 is not compatible with 1.3. If you want to revert, you have to start from scratch. uninstall 1.4, remove all internal databases (like the one in /var/lib/btsync) and reinstall everything with the new repository.

Link to post
Share on other sites

 

I discovered the build yesterday. But there are still some unclear facts like the reappearance of the GEODE build and some rumours in the forum that the Linux version of 1.4.75 crashes frequently. I will at least try to test it a few days before releasing.

Link to post
Share on other sites

Oh i didn't saw these issues on the forum.

 

What do you think about the idea of a testing-repo, then I (and others too) could test it too.

I doesn't care if it crashes, because I don't got important things there, but if something happens, I could tell you.

 

Whats a GEODE build?

Link to post
Share on other sites

Oh i didn't saw these issues on the forum.

 

What do you think about the idea of a testing-repo, then I (and others too) could test it too.

I doesn't care if it crashes, because I don't got important things there, but if something happens, I could tell you.

 

Whats a GEODE build?

 

There is already such a testing repo. You can edit the file /etc/apt/sources.list.d/yeasoft.list and change the contents to:

deb http://debian.yeasoft.net/btsync experimental maindeb-src http://debian.yeasoft.net/btsync experimental main

Generally I will publish my testing versions here before publishing them in the regular repositories.

 

The AMD GEODE is a low power, Pentium compatible CPU used in embedded Boards like the PCengines Alix Boards. The architecture is i386 and you can generally install any i386 Linux flavour (only the kernel or drivers should not rely on things like the i686 instruction set, PAE or other modern stuff). All Linux i386 versions of btsync up to 1.3.109 did crash on GEODE processors since they were explicitly compiled for i686 CPUs. That's the reason the developers provided also a GEODE version.

 

With 1.4.72 there was no GEODE version, but I noticed that the i386 version is now running also on GEODE. But after the publication of versioned links for 1.4.75, I discovered also a GEODE version. This makes things complicated.

Link to post
Share on other sites
Guest
This topic is now closed to further replies.