• Content Count

  • Joined

  • Last visited


  • Rank
  1. I have no access to the server ATM, but I will check it as soon as I have it up and running again (SSH remote reboot did not succeed...) I use a Debian Jessie Distro (Debian 8.0). And I did already do a dpkg-reconfigure btsync which did start the daemon for a couple of minutes, and then died at some point. This is the same behaviour as if I do a service btsync start.
  2. @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
  3. Okay... I have found the error. But it's rather strange. My system tells me that I have a x64 architecture: uname -m x86_64 So I always downloaded the 64bit binaries. it never worked. Out of curiosity I tried the i386 binaries: it worked! So I don't know who is to blame here: my uname or the repository at BitTorrent...
  4. It seems that the instance 'debconf-default' could not be loaded. btsync as a daemon seems to run with version 2.1.3, but not the instance of it. Why could that be? root@something:/etc/btsync# /etc/init.d/btsync status‚óŹ btsync.service - LSB: btsync Service Loaded: loaded (/etc/init.d/btsync) Active: active (exited) since Sun 2015-08-23 11:20:14 CEST; 7s ago Process: 22078 ExecStart=/etc/init.d/btsync start (code=exited, status=0/SUCCESS)Aug 23 11:20:14 something btsync[22078]: Autostarting btsync instance 'debconf-default':Failed to start btsync instance debconf-default - ... failed!Hint:
  5. Completely agree with this... I know that Bittorrent has partnerships with NAS-manufactures, and that there are actually supported btsync-builds, but we don't want to buy a NAS-system in order to create our own cloud. Therefore an offical btsync-daemon for Linux would be a great thing from BitTorrent. @noiime.. yeah it might be an ownership issue... I will try it once again. Thanks a lot for your input and help.
  6. @knireis: any idea why it fails for me? Just a hint would be great. I saw that @tuxpoldo did update his git-hub-repo with upstream notes to version 2.0.125 in June. So he seems to be doing something there, but it's true, we can not rely on him alone.
  7. @tuxpoldo: any chance that you update the PPA with the latest version from btsync? I tried manually to overwrite the btsync-core with the latest version on my Debian box, but it didn't work (I get a configuration file error...). We really need to have btsync up and running, and I don't want to switch to a NAS. This is the error: root@neo:/tmp/btsync_daemon# service btsync start[....] Autostarting btsync instance 'debconf-default':[....] Failed to start btsync instance debconf-def[FAIL- please check the configuration file /etc/btsync/debconf-default.conf ... failed!What do you think? Bernha
  8. Same issue here. We are pro users with multiple licences in our company: files get deleted on one machine, and on the other we have found the .bts leftover files... renaming those .bts files resolves the issue, but a few days later other files are missing... We are seriously considering dumping BTSync as this is too much of a show stopper for us. Regard Bernhard Sturm
  9. Ok... I could solve it: the problem was that I didn't tick the 'Install Desktop Icon' checkbox. I could start it with simply clicking on the btsync.exe in %AppData%\BitTorrent Sync\ folder Bernhard
  10. we cannot install the windows version here. The upgrade function gives an error, that there was a problem with downloading the new version and we should check for the latest version. We did, and we downloaded the version there. But after having run the installation wizard, nothing happens, and the version had not been installed. uninstalling the old version and installing a new version did not help either. rebooting all the machines did not help either. Now we are stuck. Any help on this? thanks Bernhard
  11. Hi, I have the same issue here: a large folder (>40GB) will always end ub with a "110foldererror". It used to be a 1.4 version folder, then I disconnected it, and set it up as a v2.0 folder. The error came up when it was a 1.4-folder (of course only wiht btsync 2.0), and after several disconnect and removal actions it still shows the 110foldererror.... This is somehow annyoing, as it synced ok with btsync 1.4 any chance to solve this issue?
  12. Sorry... found it myself. You can do it by simply using the Web-UI using the Cog-Wheel and upgrading to the Pro-Version...
  13. I have the server package under debian, but I can't seem to upgrade it to the pro-license... How can this be achieved?