Camaban

Members
  • Posts

    96
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by Camaban

  1. I'd had this happen as well. Insisted on asking for a new user/password (using a config file that had this defined) and then showing nothing.

     

    Empty folder list. Attempts to add a new one simply showed a blank. Attempts to add a URL received a message saying invalid URL.

     

    debug logs showed nothing.

     

    Occurred with a previous install of CentOS 6.5, a fresh Centos 7 install and a fresh Ubuntu 14.04 install. All x64.

     

    Was resolved by wiping, wiping the sync directory, installing 1.3.109, running, quitting then updating to 1.4.75

     

    The sync.log file with debugging turned on is as below.

     

    tail -f sync.log 
    version: 1.4.75
    platform: Linux 2.6.32-042stab090.5 #1 SMP Sat Jun 21 00:15:09 MSK 2014 x86_64
    [20140910 14:40:12.040] total physical memory 536870912 max disk cache 2097152
    [20140910 14:41:27.067] total physical memory 536870912 max disk cache 2097152
    [20140910 14:41:27.070] test sha1: AE5BD8EFEA5322C4D9986D06680A781392F9A642
    [20140910 14:41:27.070] test sha2: 630DCD2966C4336691125448BBB25B4FF412A49C732DB2C8ABC1B8581BD710DD
    [20140910 14:41:27.070] test aes: 0A940BB5416EF045F1C39458C653EA5A07FEEF74E1D5036E900EEE118E949293
    [20140910 14:41:27.070] My PeerID: 10536BB73F07CF503C99E80FB80CF7C1FF0F9ECA
    [20140910 14:41:27.166] setup socket 10 for local peer discovery for 127.0.0.1:0: success
    [20140910 14:41:27.576] setup socket 11 for local peer discovery for 127.0.0.2:0: success
  2. You're sure that no programs are attempting to access any of those files?

     

    If lsof (or whatever, if any, the OS/X equivalent is) and looking for that filename should show you.

     

    If they're in use, they won't be synced. I see similar behaviour when I attempt to sync two Calibre servers.

     

    On re-reading it, I can see you've mentioned that you've closed iTunes, so you can probably disregard that.

     

    However, it's also worth checking the logs on the receiving device. I've (rarely) had an issue that required deleting the problem file on the recipient device (including the !sync file for partial syncs)

     

    When I think about it, it's been a long time since I saw that happen, however I don't have any OS/X devices.

  3. dump actual config would be the contents of your current config file, so it would be pointless.

     

    All that needs to be said here if you want to keep your settings is that you might like to experiment with diff or meld (probably more meld http://meldmerge.org/) to make sure you don't miss anything when transferring from your old settings.

     

    As for your currently configuration in particular, make sure that the new config still points to your old .sync directory (located under "storage_path" on your current config file)

     

    That contains all of your file, folder and share information.

  4. I ended up just using DropBox. Mainly because it nicely renames the pictures and videos into YYYY-MM-DD HH:MM:SS.EXT format. Then have a Python script sort these into a photos folder (Camera/YYYY-MM-DD/) and use BTSync to keep this folder synced with my backup servers.

     

    Because the photos are only in the DB folder for about a minute (assuming my PC is turned on) the free version is easily sufficient.

  5. Basically, I've got about nine devices running Debian, Ubuntu and CentOS running on i386, x86_64 and ARM devices.

     

    I've also got a properly configured ~/.ssh/config file.

     

    I wrote the Python script included in the attached text file to automate the updates.

     

    This requires a file called BTSync-list.txt located where the SERVERLIST variable is pointing that contains a list of servers to be managed.

     

    It starts off by asking what the target version is (IE: 1.3.87)

    Then checks whether this is a valid version by checking whether http://syncapp.bittorrent.com/1.3.87/ exists.

     

    Then proceeds through SERVERLIST

    First it checks the installed version of btsync to see if it matches the target version

     

    If it doesn't, it checks for a processor type defined under PROCESSORLIST using the output of uname -a

     

    Then it uses SCP to transfer the correct version that has already been placed in INSTALLERDIR/PROCESSOR/btsync

    IE:  /home/pi/BTSync-Installers/x86_64/btsync to the target home directory on the target system.

     

    Then checks that the correct version has been copied.

     

    Then executes the correct version using: nice ~/btsync --config ~/sync.conf

    nice was used because one of these devices is a Raspbian server. I couldn't be bothered having it not nice on other systems.

     

    My Python is fairly primitive, so any suggestions or improvements are welcome. At the very least though, this appears to be functional. About the only thing I can think of (at 4am) that I've gotten lazy on was checking to confirm that the relevant btsync files exist under INSTALLERDIR.

     

    Obviously rename the attached file to .py - for some weird reason this forum wouldn't allow me to post executable scripts as executable scripts ;-)

    CheckBTSync.txt

  6. I'd been noticing it for a while. Then I noticed lines like:

    Blocked downloading file com.adobe.reader-20130722-010139.tar.gz due Connection closed

     

    In the sync.log file the other day.

     

    When I went through and removed those files (on RO nodes :-) ) it went fine.

     

    While doing this, I also set these RO nodes to always restore modified files to the original version.

     

    I'd also done this after the latest update, so it may have been a remainder of a bug from an earlier version.

  7. Do NOT use these expensive alternatives

    You can get a dedicated server for $5 per month with a 500 GB drive. If you need over 500 GB then choose a higher one.

    Just get a cheap dedicated server:

    www.ovh.co.uk

    I can't see those on the page... Would love a UK-based server.

    Edit: Found it.

    http://www.hotukdeal...a-month-1615371

    Now to cry tears of pain that I didn't know about this while they were available. Also further tears that I can't quite justify the 1TB one.

    Further edit:

    Apparently they're selling more at the end of September. Apparently they also take an age to provision (But really, who cares?)

  8. I'm currently using backupsy from backupsy.com

    There was (is?) a deal for $7 465GB VMs. I've got two of these setup (one CentOS, one Ubuntu) and running BTSync. The VMs only have 512MB of RAM, but now that we're past the early BTSync builds, this is plenty.

    Two aren't strictly necessary, but when I made a mistake and lost everything on one, well.... Uploading 300GB sucks. Uploading 600GB sucks hard.

    Uploading a further 100GB after that (when I'd done a rather dramatic change to my photo collection) is downright cruel.

    I'd originally also setup Owncloud to make up for my lack of DB-style web interface, but it just isn't ready for the prime time yet. I'm keeping an eye on it to see if it eventually becomes less dodgy.

    Either way, where I was paying $10 a month fo 100GB of highly difficult to customise DB storage, I'm now paying $14 a month for 465GB of easily customisable BTSync/Backupsy storage.

    I do still use DB, but that's because of the phone app which renames my photos and videos into YYYY-MM-DD format. I've made a Python script that scans that folder every minute and copies it to a dated folder in my Camera share. If BTSync ever does that photo rename and when it gets the option to start when the phone starts, I'll ditch that remaining DB link with a smile on my face and a song in my heart :-)

  9. This application is built around one single premise, sharing your key. Your advocating that the most important aspect of this application is not the burden of the application and protocol developers?

    Basically.

    There are plenty of secure means of transmission out there, just use those to transfer passwords.

    The actual app security is just fine. What you're asking for falls outside the scope of the app security.

    Edit: If you really wanted to, you could save the secret key to a text file, compress and encrypt it, email the encrypted file and SMS the recipient the key to decrypt the text file.

    Or just use single-use keys.

  10. assuming the keys are shared via unencrypted email, skype, facebook, aol, yahoo, etc etc .... then our keys are no longer really "Secret" to say the least. This doesn't even begin to cover malware, keyloggers, etc.

    In other news, accessing hotmail in a Chinese internet cafe is also a bad idea. As is giving your banking details to a Nigerian prince.

  11. Are your other devices syncing between themselves as well?

    They should be, but if they haven't started to do that for whatever weird reason, it might explain it..

    Nevermind, misunderstood how you phrased that.

    So the Windows boxes have a full sync, but the Pi is outstanding?