WebAsh

Members
  • Posts

    17
  • Joined

  • Last visited

Posts posted by WebAsh

  1. 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!

     

    Mate! You're a legend. What's the best way to move from tuxpoldo's repository to yours on a system already using his? Do I just remove his sources.list.d entry and put yours in?

  2. So, I did a crazy hack to make this work (and it seemed to, but I can't really verify 4.85 gigs of files).  Here are my steps if anyone wants to try.

     

    This is all because clicking "ok" on syncing a non-empty folder won't work.  For this we'll assume Computer 1 and Computer 2 have a folder with identical data.  We'll call it folder1.

     

    1. Remove any references to folder1 in BTSync.

    2. Add folder1 to BTSync on Computer 1.

    3. Copy the share link.

    4. Shutdown BTSync on Computer 1 (so it doesn't start syncing until you're ready).

    5. Rename folder1 to folder2 on Computer 2.

    6. Add folder1 (which is now empty) to BTSync on Computer2 (via the share link).

    7. Shutdown BTSync on Computer 2.

    8. Copy the .sync folder from folder1 to folder2.

    9. Either delete or rename folder1, so you can rename folder2 back to folder1.

    10. Now that you have your computers set up how they should be (with BTSync references AND all of your data) you can restart BTSync on both computers.

     

    The indexing time will depend on how much data you have, but it should be substantially less than actually transferring the data.

     

    Great little 'hack'. This worked perfectly.

  3. Good news, everyone. We finally got good debug information from ppl and fixed it. But sorry, no ETA on when it'll be released yet. 

     

    Is there a workaround for now? Some sort of permissions assignment that can be given?

     

    One of my BitTorrent Sync copies is 18,000km away and the other end is a slow connection - re-seeding the data will take weeks.

     

    EDIT: 

    Actually, bicman11 over in this thread has a pretty sweet workaround. Just used it and works a-OK!

    http://forum.bittorrent.com/topic/38865-two-problems-destination-folder-is-not-empty-loop-and-junctions/#entry107122

  4. I couldn't get this to work for read-only sync, either. Connecting to the folder using 2.0 version sync in a two-way mode works fine (clicking 'Connect), but for some reason when trying to connect to an existing folder using 1.0 version sync or using a read-only sharing link, I get the permissions error. Pretty annoying, as I'd prefer my backup device NOT to be able to sync changes back to the source device(s).

  5. @WebAsh

    Forever loading is most likely a firewall issue. Especially if non SSL is working and SSL isn't. Maybe port 443 is blocked or something like that. 

     

    Anyway adding your raspberry (temporary) to DMZ would at least point out if it's a firewall configuration issue or something else.

     

    No, this isn't the case. It does it for me even when I am on the same network as the Raspberry Pi. Additionally, the custom port of 8888 is remaining, so HTTPS/SSL is operating via this port - nothing to do with Port 443.

     

    I've now seen this issue on three completely different Raspberry Pi units - two running RaspBMC/OSMC and the third running Raspbian.

  6. Hi, I followed the guide:

    http://www.yeasoft.com/site/projects:btsync-deb:btsync-server

     

    And installed rasbian, used SSH to install btsync successfully on a Raspberry Pi. When I go to the webui: raspberrypi:port, I first receive a Firefox warning about the certificate, thats OK, but after adding an exception, it is loading and waiting forever. Nothing really loads. I do see the url changed to ipaddress:portnumber/gui but nothing else.

     

    SSH works fine, but when I use Cyberduck to SFTP into my raspberry it also just loads forever. It seems something is not configured yet but I don't know what.

    I logged into my router, assigned an IP address to the raspberry and even opened the port for the webui in my router. I rebooted the RPi after doing this and I can still SSH into the RPI using the new IP address.

     

    No idea in what direction to look for the issue now.

     

    Hi tuxpoldo! Been a while since I've been here... have been loving your btsync package.

     

    Having the same issue as the user above... when SSL is enabled for the WebUI, the connection never seems to complete (after accepting the self-signed cert). Just keeps 'loading'. Turning off SSL using dpkg-reconfigure gets it working again, but ultimately I'd like to use SSL.

     

    I'm (also) using a raspberry pi, running raspbmc (or soon to be known as OSMC).

  7. Thanks GreatMarko. Will give that a go now.

     

    As an aside, as the Raspberry Pi's CPU is quite abysmal (even with encryption over LAN disabled) for BTSync transfers, would copying the files onto the drive first using another machine, and then adding the folder be a better way to initially replicate the folder, with the indexing/hashing ensuring that only new changes after that would be sync'd?

  8. Thanks for your reply GreatMarko.

     

    Yes, you've caught me out. I didn't mention it as I wasn't sure what version I came from. I hoped it might not be necessary, despite knowing better ;)

     

    It wasn't that old, however. Possibly only a week or two at most.

     

    I did try removing the Pictures folder and adding again with the same secret, but it just seems to have got back to the same state and does not continue syncing.

     

    It seems to always be saying "indexing", it does disappear sometimes, but then returns not long after.

     

    If I was to power the system down, unplug the hard drive, plug it in to the machine where the files are, copy them across then hook it back up to my Pi, do you think it would bring it back to life?

  9. A pictures folder that was transferring (hadn't finished first sync) when I upgraded to 1.2.73 has now stuck saying there are no more updates, and doesn't want to transfer. The other machine which has the folder says this one (my Raspberry Pi) is connected, but there are no transfers in progress. I added another folder since the upgrade, and this one is syncing without issue.

     

    The folder just keeps saying Indexing, and that there is 14GB to upload to the other machine, which isn't right, as this is the machine that should be pulling - but it just never transfers anything.

     

    I'm not a Linux pro, so I'm not sure where to look for logs like I would be on Windows.

     

     

    post-36934-0-68256700-1384863450_thumb.p

  10. The command creates a symbolic link in the directory /lib pointing to a file located elsewhere. That means: instead of accessing the library by calling it /lib/arm-linux-gnueabihf/ld-linux.so.3, the application can also find it calling /lib/ld-linux.so.3.

    On my Raspberry PI running under Raspian, the following symbolic Links exist by default:

    pi@raspberrypi ~ $ ls -la /lib/ld-linux*lrwxrwxrwx 1 root root 30 Feb 23  2013 /lib/ld-linux-armhf.so.3 -> arm-linux-gnueabihf/ld-2.13.solrwxrwxrwx 1 root root 24 Dec 15  2012 /lib/ld-linux.so.3 -> /lib/ld-linux-armhf.so.3
    The effect is that if you access /lib/ld-linux.so.3 or /lib/ld-linux-armhf.so.3 you will always redirected to /lib/arm-linux-gnueabihf/ld-2.13.so

    As you can see, this is slightly different as the workaround specified by schlegel11, but the effect is the same: there will be a library named ld-linux.so.3 in /lib

    Basically you should find out where the library really is located and what is it's name on your system. Then you will create the symbolic link.

    Running that command given by the other user to create the symbolic link has indeed fixed the issue! Excellent! Now I have a working btsync instance on my media machine. Excellent! Thank you so much!

    Is there anything I can do to give back to you for the work you have done here?

  11. What exactly does that command do? I'm not a massive Linux user, but I'm wary of running random commands without knowing what affect it will have / do.

    Also, if it helps, I'm running a fresh install of raspbmc installed from the NOOBS SD card that comes with some RPi. It had auto updated to the latest version. So it should be completely updated - and I've since done an apt-get update and apt-get upgrade.

    There was an issue with nfs-common I had to resolve first - let me know if you also encounter it and I'll flick through the command I had to run. (i have a full log of all I've tried)

  12. Hi tuxpoldo,

     

    First, I want to say thank you very much for giving your time to provide such a great service. The package management system in Linux is great, so to be able to consume btsync via it - awesome!

     

    However, I'm having an issue with the btsync-common library on my installation of raspBMC. Whilst I appreciate that raspbmc is not listed explicitly as an OS you support, raspbmc is simply a slightly slimmer version of raspbian - customised to run the XBMC interface more natively. So, in theory, what runs on raspbian should run on raspbmc. If you don't wish to help me, that's more than OK, as you are already taking on a lot here!

     

    If you want to take a shot, here is the output I'm receiving from both aptitude and apt-get.

    Selecting previously unselected package btsync-common.(Reading database ... 43398 files and directories currently installed.)Unpacking btsync-common (from .../btsync-common_1.2.71-1_armhf.deb) ...Selecting previously unselected package btsync.Unpacking btsync (from .../btsync_1.1.82.1-3_armhf.deb) ...Setting up btsync-common (1.2.71-1) .../var/lib/dpkg/info/btsync-common.postinst: 31: /var/lib/dpkg/info/btsync-common.postinst: /usr/lib/btsync-common/btsync-core: not founddpkg: error processing btsync-common (--configure): subprocess installed post-installation script returned error exit status 127dpkg: dependency problems prevent configuration of btsync: btsync depends on btsync-common; however:  Package btsync-common is not configured yet.dpkg: error processing btsync (--configure): dependency problems - leaving unconfiguredErrors were encountered while processing: btsync-common btsyncE: Sub-process /usr/bin/dpkg returned an error code (1)A package failed to install.  Trying to recover:Setting up btsync-common (1.2.71-1) .../var/lib/dpkg/info/btsync-common.postinst: 31: /var/lib/dpkg/info/btsync-common.postinst: /usr/lib/btsync-common/btsync-core: not founddpkg: error processing btsync-common (--configure): subprocess installed post-installation script returned error exit status 127dpkg: dependency problems prevent configuration of btsync: btsync depends on btsync-common; however:  Package btsync-common is not configured yet.dpkg: error processing btsync (--configure): dependency problems - leaving unconfiguredErrors were encountered while processing: btsync-common btsync

    As you can see by "selecting previously unselected package" - I've tried this a few times, all to no avail. I'm tried purging in between and everything. But no matter what btsync-core seems to remain missing, causing btsync-common to fail.

     

    Thanks in advance for any assistance - greatly appreciated.