atte

You'll find links to full core dump in this thread. I also send you a PM with links to two sync.log files created with debug turned on.

Ok, btsync is not running well at all on that box. The i386 version exits after about 10 seconds with this dump: https://dl.dropboxusercontent.com/u/4343030/4380f07d-14dc-c68e-47b5b7b7-70802820.dmp https://dl.dropboxusercontent.com/u/4343030/core The glibc 2.3 version (although it shouldn't fit my system), runs up a bit longer, about 2 minutes, syncing seems to be working, then it exits just like that, no dump, no nothing. I have no idea where to go from here :-( A bit about my system (debian wheezy on a fit-pc): atte@vodskov:~$ ulimit -c unlimited atte@vodskov:~$ uname -a Linux vodskov 3.2.0-4-486 #1 Debian 3.2.41-2+deb7u2 i586 GNU/Linux atte@vodskov:~$ ll /lib/i386-linux-gnu/libc.so.6 lrwxrwxrwx 1 root root 12 May 26 15:33 /lib/i386-linux-gnu/libc.so.6 -> libc-2.13.so atte@vodskov:~$ /lib/i386-linux-gnu/libc.so.6 GNU C Library (Debian EGLIBC 2.13-38) stable release version 2.13, by Roland McGrath et al. Copyright (C) 2011 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Compiled by GNU CC version 4.4.7. Compiled on a Linux 3.2.35 system on 2012-12-30. Available extensions: crypt add-on version 2.1 by Michael Glad and others GNU Libidn by Simon Josefsson Native POSIX Threads Library by Ulrich Drepper et al BIND-8.2.3-T5B libc ABIs: UNIQUE IFUNC For bug reporting instructions, please see: <http://www.debian.org/Bugs/>. Btsync is running just fine on my laptop running crunchbang linux. Needles to say, I'd really appreciate any pointers, and would be more than happy to supply any info that could help track this down.

Thanks for the info! Would you (devs) like to get a fresh dump, or is it irrelevant now?

Or even better: /mnt/usb/atte/all_my_data (secret 1) /mnt/usb/atte/all_my_data/photos/latest (secret 2) /mnt/usb/atte/all_my_data/mp3/currently_listening_to (secret 3) Everything is on home server, backup at a friends house through secret 1. Laptop 1 is sharing a subset (secret 2 + 3), laptop 2 is sharing an even smaller subset (secret 3).

Hi Is nested sharing possible/recommended/evil? Example: /home/atte/photos is synced through secret 1 /home/atte/photos/summer_2013 is synced through secret 2 Reasons for doing this: 1) selective syncing a subset of files (only secret 2) to a smaller laptop, while keeping everything (secret 1) in sync on a backup box 2) sharing a single folder(secret 2) within a larger structure (secret 1) to friends, possibly using a one-time secret

Hi Well, that's the dump I got. It seems the glibc 2.3 version is working just fine on the debian box, although I don't get why (as far as I can tell glibc is version 2.13): atte@vodskov:~$ /lib/i386-linux-gnu/libc.so.6 GNU C Library (Debian EGLIBC 2.13-38) stable release version 2.13, by Roland McGrath et al. Copyright (C) 2011 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Compiled by GNU CC version 4.4.7. Compiled on a Linux 3.2.35 system on 2012-12-30. Available extensions: crypt add-on version 2.1 by Michael Glad and others GNU Libidn by Simon Josefsson Native POSIX Threads Library by Ulrich Drepper et al BIND-8.2.3-T5B libc ABIs: UNIQUE IFUNC For bug reporting instructions, please see: <http://www.debian.org/Bugs/>.

Hi I'm getting started with btsync, but having some trouble. Things work as expected on my laptop (running crunchbang linux which is based on debian wheezy). However, when I ssh into my home server (running standard debian wheezy on a fit-pc), btsync coredumps with this dmp: https://dl.dropboxus...c4-09233513.dmp As far as I can tell the two environments should be quite identical, but obviously I missed something. Any suggestions or hints would be appreciated :-)