chrisvdb

Members
  • Content Count

    25
  • Joined

  • Last visited

  • Days Won

    1

About chrisvdb

  • Rank
    Member
  1. Here as well! No config changes were required... thanks a lot!
  2. Thanks for this! Is this a drop-in replacement that should work without changing any configuration files?
  3. Thanks for updating us. Unfortunately, it's still not working for me... with all the tinkering it could be that I messed up the init file myself, though. Can someone else give it a try?
  4. Same here... I'll take a look over the weekend. If I feel really ambitious I might make a new .deb.
  5. So, tried running btsync directly and didn't get an error message at all... so the problem seems to be with the startup script. I'll do a bit of digging over the weekend.
  6. Would it be possible to create an official .deb package of bittorrent sync? The unofficial (outdated) package can be used as a template and hence the amount of work involved should be minimal.
  7. Hey guys, Did anyone try the binary replacement trick with version 2.2? For me it fails without error message. Thanks, Chris.
  8. As the unofficial Debian/Ubuntu PPA seems to be abandoned I have using the latest 2.x (server) btsync package and upgrade by simply replacing the /usr/lib/btsync-core/btsync-core binary with newer version. This has been working fine before version 2.2. With version 2.2 it just does not start up anymore... no log entry at all. Before I start debugging, did anyone encounter the same issue? If so, did you find a solution? Would Bittorrent consider creating an official deb package?
  9. Indeed rather large, but apparently also fairly compressable... I have uploaded the logs and core dump through the webform.
  10. Ok, so, btsync ran for a few hours without issues and then crashed again. Unlike the previous crashes removing the faulty file does not seem to fix the issue... when I restart btsync it crashes again a few seconds later on a different file. I have coredumps and logs in case you still want them.
  11. Hi Helen, I have restarted btsync on Timbuktu (Linux timbuktu 3.19.0-20-generic #20-Ubuntu SMP Fri May 29 10:10:47 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux) with 'ulimit -c unlimited'. I will post the log + coredump on the next failure. Faraday is a QNAP TS-253 NAS running the same version of btsync. I use the standard (outdated) QNAP btsync package but replaced the binary with the newer version (32-bit glib 2.3). Btsync on Faraday hasn't crashed a single time yet. Do you know how to enable debug logging on btsync for QNAP? I tried putting debug.txt in the directory of the binary but that didn't seem to have worked. The files are mostly normal JPGs and some AVIs. I do not know what files are the culprits due to the encryption... I can only see the encrypted filename on Timbuktu. Cheers, Chris.
  12. No, I run sync in configuration mode with the webgui disabled. Configuration: { "device_name": "Timbuktu", "listening_port" : 65432, "storage_path" : "/var/lib/btsync", "check_for_updates" : false, "use_upnp" : false, "download_limit" : 0, "upload_limit" : 0, "webui" : { //"listen" : "0.0.0.0:8888", //"login" : "admin", //"password" : "password" } , "shared_folders" : [ {// Pictures (encrypted read-only) "secret" : "<snip>", "dir" : "/var/btsync/chrisvdb/Pictures", "use_relay_server" : false, "use_tracker" : true, "use_dht" : false, "search_lan" : false, "use_sync_trash" : true, "known_hosts" : [ "<snip>:65432" ] }] , "disk_low_priority" : false, "lan_encrypt_data" : true, "lan_use_tcp" : true, "folder_rescan_interval" : 3600, "rate_limit_local_peers" : false, "sync_trash_ttl" : 30, "log_size" : 100}After the error btsync crashes. I need to delete the affected file and restart btsync for it to continue (until the next time).
  13. Hi, I haven't disabled this in the configuration. Wouldn't the assert mean that the file is altered although it is not supposed to be altered in ro mode? I have checked and there is no other process accessing the files. I just happened again... I have uploaded the logs again: https://www.dropbox.com/s/y6arxoub5b8bcyk/sync.log.tar.bz2?dl=0 . Removing the file again (temporarily) solved the issue. Chris.