Hello, thanks for your response. Couriously I find no corefile. But I did that nice command: root# strace -f -o tor.strace.02 /usr/bin/chroot /chroot/tor /bin/tor The tracefiles have between 7 an 10 mb, with gzip 500-850k. Are you interested in having a look at one? They end up with these lines: 15811 time(NULL) = 1320171090 15811 time(NULL) = 1320171090 15811 --- SIGSEGV (Segmentation fault) @ 0 (0) --- 15812 +++ killed by SIGSEGV +++ Another output shows the dependent shared libraries in my environment (+ some more stuff): root@h1896303:/root# lsof -p 25448 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME tor 25448 tor cwd DIR 9,1 4096 913933 /chroot/tor/var tor 25448 tor rtd DIR 9,1 4096 913922 /chroot/tor tor 25448 tor txt REG 9,1 3452331 913940 /chroot/tor/bin/tor tor 25448 tor mem REG 9,1 13340552 913962 /chroot/tor/var/cached-descriptors tor 25448 tor mem REG 9,1 54467 913982 /chroot/tor/lib/libnss_files.so.2 tor 25448 tor mem REG 9,1 49683 915042 /chroot/tor/lib/libnss_nis.so.2 tor 25448 tor mem REG 9,1 107282 915045 /chroot/tor/lib/libnsl.so.1 tor 25448 tor mem REG 9,1 40250 913976 /chroot/tor/lib/libnss_compat.so.2 tor 25448 tor mem REG 9,1 43341 913973 /chroot/tor/lib/librt.so.1 tor 25448 tor mem REG 9,1 1670857 913972 /chroot/tor/lib/libc.so.6 tor 25448 tor mem REG 9,1 17392 913971 /chroot/tor/lib/libdl.so.2 tor 25448 tor mem REG 9,1 125115 913970 /chroot/tor/lib/libpthread.so.0 tor 25448 tor mem REG 9,1 1685208 913969 /chroot/tor/lib/libcrypto.so.1.0.0 tor 25448 tor mem REG 9,1 351456 913967 /chroot/tor/lib/libssl.so.1.0.0 tor 25448 tor mem REG 9,1 834262 913966 /chroot/tor/lib/libevent-2.0.so.5 tor 25448 tor mem REG 9,1 191006 913965 /chroot/tor/lib/libm.so.6 tor 25448 tor mem REG 9,1 75416 913963 /chroot/tor/lib/libz.so.1 tor 25448 tor mem REG 9,1 143978 915046 /chroot/tor/lib/ld-linux.so.2 tor 25448 tor 0u CHR 1,3 0t0 913938 /chroot/tor/dev/null tor 25448 tor 1u CHR 1,3 0t0 913938 /chroot/tor/dev/null tor 25448 tor 2u CHR 1,3 0t0 913938 /chroot/tor/dev/null tor 25448 tor 3u 0000 0,9 0 1012 anon_inode tor 25448 tor 4u sock 0,6 0t0 21020578 can't identify protocol tor 25448 tor 5u unix 0xf34ea5c0 0t0 21020572 socket tor 25448 tor 6u unix 0xf34ea7c0 0t0 21020573 socket tor 25448 tor 7u 0000 0,9 0 1012 anon_inode tor 25448 tor 8u IPv4 21020574 0t0 TCP *:etlservicemgr (LISTEN) tor 25448 tor 9u IPv4 21020575 0t0 TCP *:9030 (LISTEN) tor 25448 tor 10w REG 9,1 7285 914703 /chroot/tor/log/notices.log tor 25448 tor 11w REG 9,1 12832838 914712 /chroot/tor/log/debug.log tor 25448 tor 12uW REG 9,1 0 913993 /chroot/tor/var/lock Regards Thomas Am Donnerstag, 3. November 2011 schrieb Nick Mathewson: > On Thu, Nov 3, 2011 at 1:37 PM, thomas.hluchnik@xxxxxxxxxxxxx > <thomas.hluchnik@xxxxxxxxxxxxx> wrote: > > Hello tories, > > > > after reading this mail I started to upgrade my two tor nodes which ran stable for years. I never have seen my tor process disappearing from the process list. Unfortunamtely, after upgrading to 2.2.34 on both nodes tor is crashing within a short time. > > > > I started tor in debug mode sending its debug log into a file. The crash always happens at the same point. > > > > root@h1896303:/chroot/tor/log# tail debug.log.2 > > Hi, Thomas! > > This looks like you're using a Unix box, which makes stuff easier. > The best way to debug a crash is by getting a stack trace -- either > getting a core dump, or by running Tor under gdb. That will tell us > exactly which part of the program is failing. > > Just let us know if you need help doing that and you can't find good > instructions online. > > cheers, >
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ tor-talk mailing list tor-talk@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk