tuxpoldo

Members
  • Posts

    730
  • Joined

  • Last visited

  • Days Won

    27

Everything posted by tuxpoldo

  1. Updated all packages to 1.1.15 - All Debian builds are now online. Ubuntu builds are on the way and should be online in about 1-2 hours.
  2. Updated all packages to 1.1.15 - All Debian builds are now online. Ubuntu builds are on the way and should be online in about 1-2 hours. Changelog: btsync (1.1.15-1~sid) sid; urgency=low * New upstream release - Added possibility to reconfigure the device name - Added debconf support for disk_low_priority - Added debconf support for folder_rescan_interval - Added debconf support for lan_encrypt_data - Added debconf support for lan_use_tcp - Added debconf support for rate_limit_local_peers -- Leo Moll <leo.moll@yeasoft.com> Sat, 15 Jun 2013 14:52:14 +0200 All the new configuration options are not visible during initial setup (since it is only fine tuning). If you want to change these options, you have to do a sudo dpkg-reconfigure btsync
  3. Enable Debug Mode: sudo echo FFFF > /var/lib/btsync/debug.txt Disable Debug Mode: sudo rm /var/lib/btsync/debug.txt The Logile is /var/lib/btsync/sync.log Stop btsync: sudo service btsync stop Start btsync: sudo service btsync start What do you mean with "manually"? Installing without a default instance and creating the configuration file manually? Or using btsync directly from the binary archives without debian packaging?
  4. Hi Marcel, as a general rule, installations should only ask for questions vital for the functionality. It is no problem adding "device_name" as a low priority question to the install routine. But I'm wondering why you want to customize also the "storage_path". A general storage in /var/lib/<appname> is standard for nearby any application. I can also add it to the questions in the configuration stage, but can you tell me why you want this?
  5. These problems seems to be due to btsync itself and not to the packaging. Please post this errors as separate threads or directly as bug reports to syncapp@bittorrent.com because I have no possibility to diagnose and fix them.
  6. Version 1.1.12-1 is ready. All Debian builds are now online. Ubuntu builds are on the way and should be online in about 2 hours.
  7. Version 1.1.12-1 is ready. All Debian builds are now online. Ubuntu builds are on the way and should be online in about 2 hours.
  8. Debian and Ubuntu packages have been updated both for Server Version and for Desktop Version - as usual the Ubuntu Packages take a bit longer to be online, since the launchpad build queue is quite busy...
  9. The problem is, that you installed the server version, but from what you say, I think that you should better use the desktop version. The server version is intended for use on servers and offers also the possibility to run several instances with different user credentials. This can be achieved by creating manually the configuration files for each user and not by letting debconf create a default instance. Please use the desktop version of btsync by following the instructions in this post. This would certainly satisfy your requirements. Uninstall the server version with sudo apt-get --yes --purge remove btsync in order to delete anything related.
  10. Hey BitTorrent Guys! Since a lot of time has passed without any new release, I'm incredibly excited thinking about what may come in the upcoming version. Pleeeeeeaaaaaaasse! Let us know something! ;-)
  11. REPLY! Hi! I would like to test the iOS Applications. TNX!
  12. If hostname or hostname -f do not return the hostname you have configured on your machine, then there must be some process that changes the hostname on the fly. If the machine gets the address via DHCP, it is possible that also the hostname is set from the DHCP server. You can inhibit the renaming of your machine by DHCP editing the DHCP client configuration in /etc/dhcp/dhclient.conf
  13. I know ;-) If you have a debianoid system, you sould make sure the following preconditions are met in order to have a correct hostname: There must be a file called /etc/hostname containing only the hostname of your system. In the file /etc/hosts there should be line for the main IP address of your system with the short and the full qualified name of your system. Instead of the main IP (that could change since it may be provided by DHCP), the address can also be 127.0.1.1 (this intentionally differs from localhost 127.0.0.1): Example: 127.0.0.1 localhost 127.0.1.1 yeasoft-gate2.ffm.yeasoft.net yeasoft-gate2 # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts
  14. Currently there is no way. When the file is automatically created, the device name will be generated in this way: "device_name": "$(hostname) - Default Instance", It seems that the command hostname returns this strange name ipXXX-XXX-XXX-XXX. You have currently two possibilities: Make sure, that the computer has a name that you like. You can verify this by typing hostname in the shell, but if your computer gets his address via DHCP, the hostname may be overwritten by DHCP. If you want full freedom in tweaking your configuration file, configure btsync via dpkg-reconfigure not to create a default instance and make a configuration file as you like. I hope that this helps...
  15. Sorry! I'm so stupid ;-) There was still an issue in the build script that prevented the update of the binaries. It has now been fixed (I hope!). The next version is already online for Debian. Ubuntu builds are on the way...
  16. Released Version 1.0.134.1-1 only for i386 and amd64. Debian builds are available, Ubuntu builds are on the way. It was reported that the iNotify-Interface does not work with the binaries supplied in the previous versions. btsync (1.0.134.1-1~sid) sid; urgency=low - Fixed: Replaced binary version for i386 and amd64 with versions that support the current libc -- Leo Moll <leo.moll@yeasoft.com> Sun, 02 June 2013 00:51:12 +0200
  17. Released Version 1.0.134.1-1 only for i386 and amd64. Debian builds are available, Ubuntu builds are on the way. btsync (1.0.134.1-1~sid) sid; urgency=low - Fixed: Replaced binary version for i386 and amd64 with versions that support the current libc -- Leo Moll <leo.moll@yeasoft.com> Sun, 02 June 2013 00:51:12 +0200
  18. Hi! Yes. As I wrote in this post, when creating the packages I was in doubt, which version of btsync would be the right one and it seems that I took the wrong decision. My intention was to fix this upon the next release of btsync, but now I think that the guys from BitTorrent are working hard on making lots of changes and so it will probably take some more time until the next version will be released. Instead of waiting, I will try to create a new version today...
  19. I suppose that you run btsync for each user without a specific configuration file (in fact without a specific configuration file, btsync starts with an internal default configuration. You can specify different settings for each user by creating a configuration file for each user and there you can also specify credentials for the web interface. In addition you must make sure, that all instance specific stuff like pid file, data directory, device name and ports should be unique for each user. The Desktop Packages for Debian and Ubuntu make a lot of work for you (including the generation of a configuration file for each user) but at the moment they are not able to handle the situation where multiple users are logged on, since they should create for each user a different port for the web interface. But I will work on this issue and present a solution in one of the next releases of the packages.
  20. Are you sure? leo@bookpoldo ~ $ ssh root@10.65.19.4 dpkg -l | grep libc6 Debian GNU/Linux jessie/sid ii libc6:amd64 2.17-1 amd64 Embedded GNU C Library: Shared libraries ii libc6-dev:amd64 2.17-1 amd64 Embedded GNU C Library: Development Libraries and Header Files leo@bookpoldo ~ $ ssh root@10.65.6.1 dpkg -l | grep libc6 Debian GNU/Linux 7.0 ii libc6:i386 2.13-38 i386 Embedded GNU C Library: Shared libraries ii libc6-dev:i386 2.13-38 i386 Embedded GNU C Library: Development Libraries and Header Files leo@bookpoldo ~ $ ssh root@10.65.8.1 dpkg -l | grep libc6 Debian GNU/Linux 6.0 ii libc6 2.11.3-4 Embedded GNU C Library: Shared libraries leo@bookpoldo ~ $ ssh root@10.65.0.42 dpkg -l | grep libc6 Ubuntu 12.04.2 LTS ii libc6 2.15-0ubuntu10.4 Embedded GNU C Library: Shared libraries ii libc6-dev 2.15-0ubuntu10.4 Embedded GNU C Library: Development Libraries and Header Files leo@bookpoldo ~ $ ssh root@10.65.0.20 dpkg -l | grep libc6 Ubuntu 10.04.4 LTS ii libc6 2.11.1-0ubuntu7.12 Embedded GNU C Library: Shared libraries ii libc6-dev 2.11.1-0ubuntu7.12 Embedded GNU C Library: Development Librarie ii libc6-i686 2.11.1-0ubuntu7.12 GNU C Library: Shared libraries [i686 optimi PPS: Can I have a version that runs on a GNU/Hurd ? ;-)
  21. I have noticed similar problems on some small machines I'm operating (Alix 2D13 with Debian Wheezy). This is a system based on AMD Geode with only 256 MB RAM (a typical router board). I suppose that nowadays btsync still requires a lot of RAM but I hope that in the next version a lot of the RAM related issues will be solved. There are some posts talking about this issue...
  22. As soon as pbuilder is able to setup a jessie build environment (nowadays it does not work, since there is no updates-repository for jessie, but pbuilder create requires one...) I will also create jessie-builds. In the meantime it seems that sid-builds are OK
  23. It's a pity that there is no clear documentation about this. Since I did not knew which version was the right one, I decided to include the 23 version in my packages, since it seemed more secure, but I think this was a mistake. When BT releases the next version, I will include the standard versions of the packages, since none of the OS (Ubuntu >= lucid, Debian >= sid) uses old GLIBCs
  24. Yes - it has. The btsync instance is running as root, so this should not be a problem. In the meantime I have noticed another problem: on ape-gate (the debian wheezy machine) btsync stops working without leaving any trace in the log file. But now I can see a pattern: The machines with problems are tuxpoldo and ape-gate. Both machines are Alix 2D13 router boards running with only 256MB RAM and 512MB swap so I suppose that the problems are mainly due to the fact that there is too less RAM available...
  25. You see wonderful things like: [20130428 18:58:12] Got id message from peer yeasoft-gate2 - Server Sync (AA74DB661E5341829AFAB8865A9208AE78A3DB0F) 1.0.134 [20130428 18:58:12] Merge: processing root message, remote hash 141665E627775973D61E1C62812D802BC7FB91FA, timediff: 0 [20130428 18:58:12] Merge: requesting elements for root [20130428 18:58:12] Merge: processing elements message for [20130428 18:58:12] Merge: will request files for /alix-rescue-0804/* [20130428 18:58:12] Merge: will request files for /alix-rescue-1004/* [20130428 18:58:12] Merge: will request files for /alix-rescue-deb6/* [20130428 18:58:12] Merge: will request files for /alix-rescue-deb7/* [20130428 18:58:12] Merge: will request files for /bootutils/* [20130428 18:58:12] Merge: will request files for /centos-62/* [20130428 18:58:12] Merge: will request files for /clonezilla/* [20130428 18:58:12] Merge: will request files for /debian-etch/* [20130428 18:58:12] Merge: will request files for /debian-lenny/* [20130428 18:58:12] Merge: will request files for /debian-squeeze/* [20130428 18:58:12] Merge: will request files for /debian-wheezy/* [20130428 18:58:12] Merge: will request files for /esxi35u5/* [20130428 18:58:12] Merge: will request files for /esxi40u2/* [20130428 18:58:12] Merge: will request files for /esxi41u1/* [20130428 18:58:12] Merge: will request files for /isolinux.bin/* [20130428 18:58:12] Merge: will request files for /isolinux.cfg/* [20130428 18:58:12] Merge: will request files for /ldlinux.sys/* [20130428 18:58:12] Merge: will request files for /memtest86/* [20130428 18:58:12] Merge: will request files for /menu.cfg/* [20130428 18:58:12] Merge: will request files for /netpoldo-0804/* [20130428 18:58:12] Merge: will request files for /netpoldo-1004/* [20130428 18:58:12] Merge: will request files for /netpoldo-1204/* [20130428 18:58:12] Merge: will request files for /netpoldo-deb6/* [20130428 18:58:12] Merge: will request files for /netpoldo-deb7/* [20130428 18:58:12] Merge: will request files for /ontpre/* [20130428 18:58:12] Merge: will request files for /pmagic/* [20130428 18:58:12] Merge: will request files for /pxelinux.0/* [20130428 18:58:12] Merge: will request files for /pxelinux.cfg/* [20130428 18:58:12] Merge: will request files for /syslinux/* [20130428 18:58:12] Merge: will request files for /syslinux.cfg/* [20130428 18:58:12] Merge: will request files for /ubuntu-0804/* [20130428 18:58:12] Merge: will request files for /ubuntu-1004/* [20130428 18:58:12] Merge: will request files for /ubuntu-1110/* [20130428 18:58:12] Merge: will request files for /ubuntu-1204/* [20130428 18:58:12] Merge: will request files for /ubuntu-1304/* [20130428 18:58:12] Merge: sending get_files message [20130428 18:58:12] Got ping (broadcast: 0) from peer 10.65.2.142:22144 (AA74DB661E5341829AFAB8865A9208AE78A3DB0F) for share A2EF1BEB6B4AD2FE6CDA3DA0CEF528DCC9F0B59A [20130428 18:58:12] Found peer for folder /mnt/data/tftproot/yeaboot AA74DB661E5341829AFAB8865A9208AE78A3DB0F 10.65.2.142:22144 direct:1 [20130428 18:58:12] Got ping (broadcast: 0) from peer 10.65.2.142:22144 (AA74DB661E5341829AFAB8865A9208AE78A3DB0F) for share A2EF1BEB6B4AD2FE6CDA3DA0CEF528DCC9F0B59A [20130428 18:58:12] Found peer for folder /mnt/data/tftproot/yeaboot AA74DB661E5341829AFAB8865A9208AE78A3DB0F 10.65.2.142:22144 direct:1 [20130428 18:58:12] Sending broadcast ping for share A2EF1BEB6B4AD2FE6CDA3DA0CEF528DCC9F0B59A [20130428 18:58:12] Send ping to peer (BA74128C764764607A8127590EAF307BA0CF297C) for share A2EF1BEB6B4AD2FE6CDA3DA0CEF528DCC9F0B59A: [20130428 18:58:12] ping 10.65.2.129:22144 directly [20130428 18:58:12] Send ping to peer (AA74DB661E5341829AFAB8865A9208AE78A3DB0F) for share A2EF1BEB6B4AD2FE6CDA3DA0CEF528DCC9F0B59A: [20130428 18:58:12] ping 10.65.2.142:22144 directly [20130428 18:58:12] Send ping to peer () for share A2EF1BEB6B4AD2FE6CDA3DA0CEF528DCC9F0B59A: [20130428 18:58:12] ping 10.65.0.16:22144 directly [20130428 18:58:12] Send ping to peer () for share A2EF1BEB6B4AD2FE6CDA3DA0CEF528DCC9F0B59A: [20130428 18:58:12] ping 10.65.4.1:22144 directly [20130428 18:58:12] Send ping to peer () for share A2EF1BEB6B4AD2FE6CDA3DA0CEF528DCC9F0B59A: [20130428 18:58:12] ping 10.65.8.1:22144 directly [20130428 18:58:12] Send ping to peer () for share A2EF1BEB6B4AD2FE6CDA3DA0CEF528DCC9F0B59A: [20130428 18:58:12] ping 10.65.18.1:22144 directly [20130428 18:58:12] Got ping (broadcast: 0) from peer 10.65.2.129:22144 (BA74128C764764607A8127590EAF307BA0CF297C) for share A2EF1BEB6B4AD2FE6CDA3DA0CEF528DCC9F0B59A [20130428 18:58:12] Found peer for folder /mnt/data/tftproot/yeaboot BA74128C764764607A8127590EAF307BA0CF297C 10.65.2.129:22144 direct:1 [20130428 18:58:12] Got ping (broadcast: 0) from peer 10.65.2.129:22144 (BA74128C764764607A8127590EAF307BA0CF297C) for share A2EF1BEB6B4AD2FE6CDA3DA0CEF528DCC9F0B59A [20130428 18:58:12] Found peer for folder /mnt/data/tftproot/yeaboot BA74128C764764607A8127590EAF307BA0CF297C 10.65.2.129:22144 direct:1 [20130428 18:58:13] Got ping (broadcast: 0) from peer 10.65.2.142:22144 (AA74DB661E5341829AFAB8865A9208AE78A3DB0F) for share A2EF1BEB6B4AD2FE6CDA3DA0CEF528DCC9F0B59A [20130428 18:58:13] Found peer for folder /mnt/data/tftproot/yeaboot AA74DB661E5341829AFAB8865A9208AE78A3DB0F 10.65.2.142:22144 direct:1 [20130428 18:58:13] Got ping (broadcast: 0) from peer 10.65.2.142:22144 (AA74DB661E5341829AFAB8865A9208AE78A3DB0F) for share A2EF1BEB6B4AD2FE6CDA3DA0CEF528DCC9F0B59A [20130428 18:58:13] Found peer for folder /mnt/data/tftproot/yeaboot AA74DB661E5341829AFAB8865A9208AE78A3DB0F 10.65.2.142:22144 direct:1 [20130428 18:58:13] Sending broadcast ping for share A2EF1BEB6B4AD2FE6CDA3DA0CEF528DCC9F0B59A [20130428 18:58:13] Send ping to peer (BA74128C764764607A8127590EAF307BA0CF297C) for share A2EF1BEB6B4AD2FE6CDA3DA0CEF528DCC9F0B59A: [20130428 18:58:13] ping 10.65.2.129:22144 directly The problem is that nothing is replicated.... I must add some information: it seems to be a problem only on this machine (running on debian 6 squeeze i386). All the other machines in the grid are working fine: yeasoft-gate2(10.65.0.16): ubuntu 12.04 (precise) amd64 ape-gate(10.65.4.1): debian 7 (wheezy) i386 ccm-mgmt(10.65.18.1): ubuntu 10.03 (lucid) i386 All machines are running with the glib23 version....