tuxpoldo
-
Posts
730 -
Joined
-
Last visited
-
Days Won
27
Everything posted by tuxpoldo
-
Released new packages 1.1.42-2 with a few bugfixes. All Debian builds are now online. As usual, Ubuntu builds will be probably available in a few hours. Changelog: btsync (1.1.42-2~sid) sid; urgency=low - Fixed: On slow systems the init scripts may fail under certain conditions (Reported by Christian Wantia) - Fixed: The init script did not reliably detect if a btsync instance is really started when more than one instance was defined -- Leo Moll <leo.moll@yeasoft.com> Tue, 18 Jul 2013 14:03:27 +0200 -
Update 3: Installed Debian 6 i386 on a virtual machine with desktop (i didn't want this!) and ssh server from netinstall image Removed all the not needed desktop stuff The attachment is the file with the list of installed packages: packages.txt Now: root@debian:~# gpg --keyserver pgp.mit.edu --recv-keys 6BF18B15 gpg: directory `/root/.gnupg' created gpg: new configuration file `/root/.gnupg/gpg.conf' created gpg: WARNING: options in `/root/.gnupg/gpg.conf' are not yet active during this run gpg: keyring `/root/.gnupg/secring.gpg' created gpg: keyring `/root/.gnupg/pubring.gpg' created gpg: requesting key 6BF18B15 from hkp server pgp.mit.edu gpg: /root/.gnupg/trustdb.gpg: trustdb created gpg: key 6BF18B15: public key "Leo Moll <leo.moll@yeasoft.com>" imported gpg: no ultimately trusted keys found gpg: Total number processed: 1 gpg: imported: 1 root@debian:~# gpg --armor --export 6BF18B15 | apt-key add - OK root@debian:~# echo deb http://debian.yeasoft.net/btsync $(lsb_release -cs) main contrib non-free >> /etc/apt/sources.list.d/btsync.list root@debian:~# echo deb-src http://debian.yeasoft.net/btsync $(lsb_release -cs) main contrib non-free >> /etc/apt/sources.list.d/btsync.list root@debian:~# apt-get update ... root@debian:~# apt-get install btsync Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: btsync 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 2,037 kB of archives. After this operation, 3,969 kB of additional disk space will be used. Get:1 http://debian.yeasoft.net/btsync/ squeeze/main btsync i386 1.1.42-1~squeeze [2,037 kB] Fetched 2,037 kB in 2s (858 kB/s) Preconfiguring packages ... Selecting previously deselected package btsync. (Reading database ... 21343 files and directories currently installed.) Unpacking btsync (from .../btsync_1.1.42-1~squeeze_i386.deb) ... Setting up btsync (1.1.42-1~squeeze) ... Starting P2P file synchronisation daemon(s)... root@debian:~# root@debian:~# useradd -m user1 root@debian:~# useradd -m user2 root@debian:~# useradd -m user3 root@debian:~# cd /etc/btsync/ Now copied the 3 configuration files from another machine: user1.conf.txtuser2.conf.txtuser3.conf.txt root@debian:/etc/btsync# lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 6.0.7 (squeeze) Release: 6.0.7 Codename: squeeze root@debian:/etc/btsync# uname -a Linux debian 2.6.32-5-686 #1 SMP Fri May 10 08:33:48 UTC 2013 i686 GNU/Linux root@debian:/etc/btsync# service btsync start Starting P2P file synchronisation daemon(s)...Autostarting btsync instance 'user1':. Autostarting btsync instance 'user2':. Autostarting btsync instance 'user3':. root@debian:/etc/btsync# ps ax PID TTY STAT TIME COMMAND 1 ? Ss 0:00 init [2] 2 ? S 0:00 [kthreadd] ... 947 ? Ss 0:00 sshd: root@pts/0 949 pts/0 Ss 0:00 -bash 1109 ? Sl 0:00 /usr/lib/btsync/btsync-daemon --nodaemon --config /etc/btsync/user1.conf 1153 ? Sl 0:00 /usr/lib/btsync/btsync-daemon --nodaemon --config /etc/btsync/user2.conf 1197 ? Sl 0:00 /usr/lib/btsync/btsync-daemon --nodaemon --config /etc/btsync/user3.conf 1210 pts/0 R+ 0:00 ps ax Everything is working properly. Any idea?
-
I will test this during the evening and try to find a solution. It seems that one of my last changes broke something... Update 1: On my first test I am not able to reproduce the error. I admit that the part you have removed is not really perfect, but currently is seems to work.... yeasoft-gate2 /etc/btsync # service btsync start * Starting P2P file synchronisation daemon(s)... * Autostarting btsync instance 'debconf-default' [ OK ] * Autostarting btsync instance 'serversync' [ OK ] yeasoft-gate2 /etc/btsync # ps axu ... 6698 ? Sl 0:01 /usr/lib/btsync/btsync-daemon --nodaemon --config /etc/btsync/debconf-default.conf 6739 ? Sl 0:32 /usr/lib/btsync/btsync-daemon --nodaemon --config /etc/btsync/serversync.conf yeasoft-gate2 /etc/btsync # But I'm still trying to reproduce the error... Update 2: I took your configuration file, copied it to user2.conf and user3.conf, changed names and ports, created the users, restarted the show... yeasoft-gate2 /etc/btsync # useradd -m user1 yeasoft-gate2 /etc/btsync # useradd -m user2 yeasoft-gate2 /etc/btsync # useradd -m user3 yeasoft-gate2 /etc/btsync # ls -la /home/ total 24 drwxr-xr-x 6 root root 4096 Jul 17 00:04 . drwxr-xr-x 22 root root 4096 Jul 7 18:07 .. drwxr-xr-x 4 leo leo 4096 Feb 25 15:01 leo drwxr-xr-x 2 user1 user1 4096 Jul 17 00:04 user1 drwxr-xr-x 2 user2 user2 4096 Jul 17 00:04 user2 drwxr-xr-x 2 user3 user3 4096 Jul 17 00:04 user3 yeasoft-gate2 /etc/btsync # service btsync restart * Stopping P2P file synchronisation daemon(s)... * Stopping btsync instance 'debconf-default' [ OK ] * Stopping btsync instance 'serversync' [ OK ] * Starting P2P file synchronisation daemon(s)... * Autostarting btsync instance 'debconf-default' [ OK ] * Autostarting btsync instance 'serversync' [ OK ] * Autostarting btsync instance 'user1' [ OK ] * Autostarting btsync instance 'user2' [ OK ] * Autostarting btsync instance 'user3' [ OK ] yeasoft-gate2 /etc/btsync # ps axu ... root 15278 1.2 0.1 463520 7404 ? Sl 00:06 0:01 /usr/lib/btsync/btsync-daemon --nodaemon --config /etc/btsync/debconf-default.conf root 15319 14.8 0.1 397252 5616 ? Sl 00:06 0:16 /usr/lib/btsync/btsync-daemon --nodaemon --config /etc/btsync/serversync.conf user1 15370 0.0 0.0 260848 2220 ? Sl 00:06 0:00 /usr/lib/btsync/btsync-daemon --nodaemon --config /etc/btsync/user1.conf user2 15420 0.0 0.0 260848 2228 ? Sl 00:06 0:00 /usr/lib/btsync/btsync-daemon --nodaemon --config /etc/btsync/user2.conf user3 15469 0.0 0.0 260848 2212 ? Sl 00:06 0:00 /usr/lib/btsync/btsync-daemon --nodaemon --config /etc/btsync/user3.conf yeasoft-gate2 /etc/btsync # Strange. Everything seems to work.... This machine is running Ubuntu 12.04 LTS amd64 with 4GB of RAM. Anybody here able to reproduce the behaviour reported by Christian Wantia?
-
Updated all packages to 1.1.42 - All Debian builds are now online. As usual, Ubuntu builds will be probably available in 1-2 hours. Changelog: btsync (1.1.42-1~sid) sid; urgency=low * New upstream release -- Leo Moll <leo.moll@yeasoft.com> Tue, 16 Jul 2013 17:45:08 +0200
-
Updated all packages to 1.1.42 - All Debian builds are now online. As usual, Ubuntu builds will be probably available in 1-2 hours. Changelog: btsync (1.1.42-1~sid) sid; urgency=low * New upstream release -- Leo Moll <leo.moll@yeasoft.com> Tue, 16 Jul 2013 17:45:08 +0200
-
I think, that the problem is caused by the combination of your settings. First of all, you must assure that btsync is able to read and write all files into the data directory. If the files were created by btsync before you set the credentials and the umask, you must change the ownership and permission of all files in the data directory accordingly. I'm also wondering about 0770 as UMASK. This means, that directories will be created with 007 and files with 006 mode. Is that really what you want? These options give the user a lot of power, but must be used wisely...
-
Updated all packages to 1.1.40 - All Debian builds are going online. As usual, Ubuntu builds will be probably available in 30-60 Minutes. Changelog: btsync (1.1.40-1~sid) sid; urgency=low * New upstream release -- Leo Moll <leo.moll@yeasoft.com> Mon, 15 Jul 2013 16:13:43 +0200
-
Updated all packages to 1.1.40 - All Debian builds are going online. As usual, Ubuntu builds will be probably available in 30-60 Minutes. Changelog: btsync (1.1.40-1~sid) sid; urgency=low * New upstream release -- Leo Moll <leo.moll@yeasoft.com> Mon, 15 Jul 2013 16:13:43 +0200
-
I think that the problem is that phyton3.3 upgrades also the libc6. The standard build process creates a library dependency in the package metainformation. I think that you can solve the problem, by installing the package for sid instead. You can achieve that, by editing the file /etc/apt/sources.list.d/btsync.list and changing the reference of wheezy to sid. Probably you have to uninstall btsync before (but you will not lose your settings). You should do things in the following order: uninstall btsync (apt-get remove btsync).. the references in the debconf database, the config files in /etc/btsync and the data files in /var/lib/btsync will not be removed (if you do not explicitely specify --purge) modify the file /etc/apt/sources.list.d/btsync.list apt-get update install your python stuff apt-get install btsync
-
In order to build the packages for jessie, I meed a jessie installation on my PI. I will try to do this in the next days.
-
Updated all packages to 1.1.33 - All Debian builds are now online. Unfortunately today again there is high load on launchpad and so Ubuntu builds will be probably available in about 8 hours (launchpad shows 4-8 hours for all builds). I'm sorry, but again I can't change this :-( Changelog: btsync (1.1.33-1~sid) sid; urgency=low * New upstream release -- Leo Moll <leo.moll@yeasoft.com> Thu, 11 Jul 2013 22:10:09 +0200
-
Updated all packages to 1.1.33 - All Debian builds are now online. Unfortunately today again there is high load on launchpad and so Ubuntu builds will be probably available in about 8 hours (launchpad shows 4-8 hours for all builds). I'm sorry, but again I can't change this :-( Changelog: btsync (1.1.33-1~sid) sid; urgency=low * New upstream release -- Leo Moll <leo.moll@yeasoft.com> Thu, 11 Jul 2013 22:10:09 +0200
-
Very tiny update 1.1.30-2. Unfortunately Ubuntu will take a while... and this time no ARM builds. Changelog: btsync (1.1.30-2~sid) sid; urgency=low - New: The init script now detects startup failures and shows an error message. - New: The init script now issues some syslog messages on failures - New: The init script now supports the "status" command -- Leo Moll <leo.moll@yeasoft.com> Thu, 11 Jul 2013 16:07:24 +0200 This release is inspired by:
-
Unfortunately this is another problem with btsync. If the configuration file contains errors, btsync will not start but also not return any error code, and for this reason it is not possible to detect a start failure in the daemon scripts. I am thinking about adding some additional tests after launching the daemon in order to verify that something is not working...
-
STOP! You are making two fundamental errors! First error: should never edit debconf-default.conf manually. As it says in the comment section at the beginning: // DO NOT EDIT THIS FILE MANUALLY // // use dpkg-reconfigure btsync to modify the // configuration What does this mean? It means: DO NOT EDIT THIS FILE MANUALLY ;-P You can/must reconfigure the default btsync instance by issuing the command: sudo dpkg-reconfigure btsync With this command you can set all operating parameters of btsync (including the umask) interactively. If you edit the file manually, all your changes are lost at the next update, since the parameters are stored into the debconf database and the configuration file will be regenerated at each update/install or reconfiguration. If you do not like this and you want to manage your configuration files manually, you should select at the very beginning of the installation (or dpkg-reconfigure) that you do not want a default instance. Second Error: as clearly described in the documentation, parameters like DAEMON_UID, DAEMON_GID and DAEMON_UMASK are not parsed by btsync itself, but by the daemon scripts and that they should be placed in the comments. So if you uncomment them, you are creating a broken configuration file and btsync will not start. This is the reason because nothing is working now! See the documentation included in the package, the documentation written in the initial post and what I wrote to another user in one of the previous postings: This shows why it is always a good idea to RTFM ;-)
-
Good news! Version 1.1.30 fixes the problem!
-
Updated all packages to 1.1.30 - All Debian builds are now online. Unfortunately todays there is high load on launchpad and so Ubuntu builds will be probably available in about 10 hours (launchpad shows 6-10 hours for all builds). I'm sorry, but I can't change this :-( Changelog: btsync (1.1.30-1~sid) sid; urgency=low * New upstream release -- Leo Moll <leo.moll@yeasoft.com> Wed, 10 Jul 2013 00:31:45 +0200
-
Updated all packages to 1.1.30 - All Debian builds are now online. Unfortunately todays there is high load on launchpad and so Ubuntu builds will be probably available in about 10 hours (launchpad shows 6-10 hours for all builds). I'm sorry, but I can't change this :-( Changelog: btsync (1.1.30-1~sid) sid; urgency=low * New upstream release -- Leo Moll <leo.moll@yeasoft.com> Wed, 10 Jul 2013 00:31:45 +0200
-
You can see which version was installed by the debian/ubuntu packaging by executing the commmand sudo dpkg -l btsync I suppose that you have more than one btsync running on your machine. One installed via the repository with apt-get install btsync the other installed by other means. This is the only explanation for what you are describing. One thing is clear. If the Web UI does not show the version of the currently installed btsync (that should be 1.1.27), then it comes from another btsysnc. p.S.: Are you sure to perform a regular sudo apt-get update in order to keep your package index file synchronised with their sources? If you did not, then your computer does never update anything! Keeping the machine up to date means to perform the following commands on a regular base: sudo apt-get update sudo apt-get upgrade
-
As you can read in this thread, all the packages for debian/ubuntu are always on the latest level. There is no explanation for what you are describing. If you initially have installed btsync using the PPA, you should always be up to date.
-
The file has a huge comment section at the beginning (lines staring with //) with a complete documentation on how to set the parameters. Since it is not btsync itself which understands DAEMON_UID, DAEMON_GID and DAEMON_UMASK, these parameters have to be set in the comments section. Simply specify before of the json part of the configuration file the DAMON_ parameters: // // DAEMON_UID=myuserid // The daemon script parses the parameters right out of the comment section.
-
Yes. Use the repositories for Debian sid instead. Since the question was asked several times, I updated the initial posting.
-
Hi! The BitTorrent Sync executable has his own daemonization capability. But since it offers no possibility neither to set the umask, the user credentials nor control some other important process characteristics, the daemon scripts use the standard tool start-stop-daemon that manages the whole thing. In such a case, the executable must be started as real program, and you achieve this by specifying --nodaemon on the command line. Take a look at the startup script /etc/init.d/btsync and to the manpage of start-stop-daemon if you want to learn more about this topic. Are you really sure? Try to run sudo ps ax | grep btsync-daemon and you will see, that only one instance is running. I tested it also on my datacenter server: yeasoft-gate2 ~ # pstree init-+-/usr/sbin/munin |-atd |-btsync-daemon---6*[{btsync-daemon}] |-corosync---9*[{corosync}] |-cron |-dbus-daemon |-dhcpd |-6*[getty] |-ha_logd---ha_logd |-in.tftpd |-named---6*[{named}] |-ntpd |-5*[openvpn] |-pacemakerd-+-attrd | |-cib | |-crmd | |-lrmd | |-pengine | `-stonithd |-rpc.idmapd |-rpc.mountd |-rpc.statd |-rpcbind |-rsync |-rsyslogd---3*[{rsyslogd}] |-sshd---sshd---bash---pstree |-udevd---2*[udevd] |-upstart-socket- |-upstart-udev-br `-zabbix_agentd---5*[zabbix_agentd] yeasoft-gate2 ~ # ps ax | grep btsync 2558 ? Sl 0:01 /usr/lib/btsync/btsync-daemon --nodaemon --config /etc/btsync/debconf-default.conf 16393 pts/1 S+ 0:00 grep --color=auto btsync As you see, also I have a 6* in the output of pstree but the output of ps ax shows only one instance running. If you look at the manpage of pstree, you will learn that the number represents the number of child threads (not processes). Each instance created by the btsync daemon scripts creates a btsync process.
-
All Debian builds are now online. Ubuntu builds are on the way and should be online in a few minutes. btsync (1.1.27-2~sid) sid; urgency=low - Fixed: AUTOSTART in /etc/default/btsync had no effect - Added support for custom configuration files in btsync-user -- Leo Moll <leo.moll@yeasoft.com> Sun, 07 Jul 2013 15:29:51 +0200
-
Some user requested the possibility to customise the configuration of the BitTorrent Sync instance. There are good news: the new Version 1.1.27-2 allows to create an optional user specific configuration file for each user. Please see the USAGE NOTES in the main posting for details. New Builds for Debian and Ubuntu are available: btsync (1.1.27-2~sid) sid; urgency=low- Fixed: AUTOSTART in /etc/default/btsync had no effect- Added support for custom configuration files in btsync-user-- Leo Moll <leo.moll@yeasoft.com> Sun, 07 Jul 2013 15:29:51 +0200
