tor 0.2.1.24 crashes on Sparc-Solaris10
Thomas.Hluchnik at netcologne.de
Thomas.Hluchnik at netcologne.de
Tue Mar 9 19:23:30 UTC 2010
Hello,
I always run a tor node on my Sparc engine which is connected to the net via DSL and always runs without problems. So the 0.2.1.22 did. Now I got the sources of 0.2.1.24 and installed them doing the same commands as I always do.
When starting tor it comes up but crashes within one minute. These are some of the infos:
root at tor# uname -a
SunOS tor 5.10 Generic_141444-09 sun4u sparc SUNW,Ultra-4
The configure options:
./configure --enable-threads --prefix=/usr --sysconfdir=/etc --with-ssl-dir=/usr/local/ssl
root at tor# ldd /usr/bin/tor
libz.so => /usr/lib/libz.so
libevent-1.4.so.2 => /usr/lib/libevent-1.4.so.2
libssl.so.0.9.8 => /usr/local/ssl/lib/libssl.so.0.9.8
libcrypto.so.0.9.8 => /usr/local/ssl/lib/libcrypto.so.0.9.8
libnsl.so.1 => /lib/libnsl.so.1
libsocket.so.1 => /lib/libsocket.so.1
libc.so.1 => /lib/libc.so.1
librt.so.1 => /lib/librt.so.1
libresolv.so.2 => /lib/libresolv.so.2
libdl.so.1 => /lib/libdl.so.1
libgcc_s.so.1 => /usr/local/lib/libgcc_s.so.1
libmp.so.2 => /lib/libmp.so.2
libmd.so.1 => /lib/libmd.so.1
libscf.so.1 => /lib/libscf.so.1
libaio.so.1 => /lib/libaio.so.1
libdoor.so.1 => /lib/libdoor.so.1
libuutil.so.1 => /lib/libuutil.so.1
libgen.so.1 => /lib/libgen.so.1
libm.so.2 => /lib/libm.so.2
/platform/SUNW,Ultra-4/lib/libc_psr.so.1
/platform/SUNW,Ultra-4/lib/libmd_psr.so.1
The crash causes no message in notices.log. It looks like:
Mar 09 20:07:27.087 [notice] Tor 0.2.1.24 opening log file.
Mar 09 20:07:27.092 [notice] Parsing GEOIP file.
Mar 09 20:07:28.997 [notice] OpenSSL OpenSSL 0.9.8l 5 Nov 2009 looks like version 0.9.8l; I will try SSL3_FLAGS to enable renegotation.
Mar 09 20:07:32.541 [notice] Your Tor server's identity key fingerprint is 'herecomesthesun E959DE5174DE719D712E181704DF20E7D47FD221'
Mar 09 20:08:03.318 [notice] We now have enough directory information to build circuits.
Mar 09 20:08:03.318 [notice] Bootstrapped 80%: Connecting to the Tor network.
Mar 09 20:08:04.474 [notice] Guessed our IP address as 89.0.140.247 (source: 194.109.206.212).
Mar 09 20:08:05.699 [notice] Bootstrapped 85%: Finishing handshake with first hop.
Mar 09 20:08:06.808 [notice] Bootstrapped 90%: Establishing a Tor circuit.
Mar 09 20:08:08.891 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Mar 09 20:08:08.895 [notice] Bootstrapped 100%: Done.
Mar 09 20:08:08.895 [notice] Now checking whether ORPort 89.0.140.247:9001 and DirPort 89.0.140.247:9030 are reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Mar 09 20:08:14.977 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Mar 09 20:08:15.846 [notice] Tor 0.2.1.24 opening log file.
Mar 09 20:08:15.851 [notice] Parsing GEOIP file.
At Mar 09 20:08:14.977 a new tor process started after the crash of the old process. This is because it starts vis SMF Service Manifest instead of initscript.
I did a truss -p <pid_of_tor> to see better whats going on. It looks like:
/1: write(14, " M a r 0 9 2 0 : 1 0".., 127) = 127
/1: time() = 1268161838
/1: port_associate(3, 4, 0x00000012, 0x00000001, 0x00000000) = 0
/1: port_getn(3, 0xFFBFFB20, 8, 1, 0xFFBFFB14) = 1 [0]
/1: clock_gettime(4, 0xFFBFFBA4) = 0
/1: write(14, " M a r 0 9 2 0 : 1 0".., 75) = 75
/1: write(14, " M a r 0 9 2 0 : 1 0".., 125) = 125
/1: read(18, "170301\0 ", 5) = 5
/1: read(18, " V -87 ~ jDA9BB8 P s90D7".., 32) = 32
/1: read(18, "17030102 ", 5) = 5
/1: read(18, "D0A7AB p80 4 - d yB4BF z".., 544) = 544
/1: write(14, " M a r 0 9 2 0 : 1 0".., 97) = 97
/1: write(14, " M a r 0 9 2 0 : 1 0".., 129) = 129
/1: time() = 1268161838
/1: time() = 1268161838
/1: time() = 1268161838
/1: port_associate(3, 4, 0x00000016, 0x00000005, 0x00000000) = 0
/1: write(14, " M a r 0 9 2 0 : 1 0".., 90) = 90
/1: write(14, " M a r 0 9 2 0 : 1 0".., 127) = 127
/1: time() = 1268161838
/1: port_associate(3, 4, 0x00000012, 0x00000001, 0x00000000) = 0
/1: port_getn(3, 0xFFBFFB20, 8, 1, 0xFFBFFB14) = 1 [0]
/1: clock_gettime(4, 0xFFBFFBA4) = 0
/1: write(14, " M a r 0 9 2 0 : 1 0".., 77) = 77
/1: send(22, "02\0\0\0\0\0\0\014 "\r '".., 197, 0) = 197
/1: time() = 1268161838
/1: port_associate(3, 4, 0x00000016, 0x00000001, 0x00000000) = 0
/2: recv(21, "02", 1, 0) = 1
/2: recv(21, "\0\0\0\0\0\0\014 "\r", 10, 0) = 10
/2: recv(21, " ' 210\0 T18B2 AFB040E .".., 186, 0) = 186
/2: time() = 1268161838
/2: getpid() = 11926 [2086]
/2: time() = 1268161838
/2: getpid() = 11926 [2086]
/1: port_getn(3, 0xFFBFFB20, 8, 1, 0xFFBFFB14) = 0 [62]
/1: clock_gettime(4, 0xFFBFFBA4) = 0
/1: time() = 1268161838
/1: write(14, " M a r 0 9 2 0 : 1 0".., 61) = 61
/1: write(14, " M a r 0 9 2 0 : 1 0".., 66) = 66
/1: write(14, " M a r 0 9 2 0 : 1 0".., 63) = 63
/1: time() = 1268161838
/1: time() = 1268161838
/1: time() = 1268161838
/1: time() = 1268161838
/1: time() = 1268161838
/1: time() = 1268161838
/1: time() = 1268161838
/1: time() = 1268161838
/1: time() = 1268161838
/1: time() = 1268161838
/2: write(14, " M a r 0 9 2 0 : 1 0".., 85) = 85
/2: send(21, "01\0\0\0\0\0\0\014 "\r8F".., 231, 0) = 231
/2: write(14, " M a r 0 9 2 0 : 1 0".., 73) = 73
/1: port_getn(3, 0xFFBFFB20, 8, 1, 0xFFBFFB14) = 1 [0]
/1: clock_gettime(4, 0xFFBFFBA4) = 0
/1: write(14, " M a r 0 9 2 0 : 1 0".., 75) = 75
/1: recv(22, "01\0\0\0\0\0\0\014 "\r8F".., 16384, 0) = 231
/1: write(14, " M a r 0 9 2 0 : 1 0".., 75) = 75
/1: Incurred fault #5, FLTACCESS %pc = 0x00029AD0
/1: siginfo: SIGBUS BUS_ADRALN addr=0xFFBFF9D6
/1: Received signal #10, SIGBUS [default]
/1: siginfo: SIGBUS BUS_ADRALN addr=0xFFBFF9D6
Any ideas, any help?
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.torproject.org/pipermail/tor-talk/attachments/20100309/7907f570/attachment.pgp>
More information about the tor-talk
mailing list