Tor server crash in SSL_free with DH crypto error in logs
Just got a crash in r14173. Have a warn in the log right before:
Apr 12 12:30:19.323 [warn] crypto error while generating DH key: BN lib (in Diff ie-Hellman routines:GENERATE_KEY).
Here is the backtrace of the thread that caused the crash:
#0 0x4cef366c in EVP_CIPHER_CTX_cleanup () from /lib/libcrypto.so.6 #1 0x4cfc4f35 in ssl_clear_cipher_ctx () from /lib/libssl.so.6 legacy/trac#2 (closed) 0x4cfc6ab5 in SSL_free () from /lib/libssl.so.6 legacy/trac#3 (closed) 0x080f335c in tor_tls_free (tls=0x40df1ac0) at tortls.c:831 legacy/trac#4 (closed) 0x0806d2eb in _connection_free (conn=0x46229f00) at connection.c:328 legacy/trac#5 (closed) 0x080a363c in connection_unlink (conn=0x46229f00) at main.c:212 legacy/trac#6 (closed) 0x080a390e in close_closeable_connections () at main.c:603 legacy/trac#7 (closed) 0x4cfe4125 in event_base_loop () from /usr/lib/libevent-1.1a.so.1 legacy/trac#8 (closed) 0x4cfe4349 in event_loop () from /usr/lib/libevent-1.1a.so.1 legacy/trac#9 (closed) 0x080a5149 in do_main_loop () at main.c:1446 legacy/trac#10 (closed) 0x080a52fb in tor_main (argc=3, argv=0x59c9d5c4) at main.c:1986 legacy/trac#11 (closed) 0x080d9ee2 in main (argc=Cannot access memory at address 0x0
The cpuworker thread was in the process of spitting out another (or perhaps just finished the original?) warn:
#0 0x4cffe402 in __kernel_vsyscall () #1 0x4cdcbf7b in write () from /lib/libc.so.6 legacy/trac#2 (closed) 0x4cd6d884 in _IO_new_file_write () from /lib/libc.so.6 legacy/trac#3 (closed) 0x4cd6d545 in new_do_write () from /lib/libc.so.6 legacy/trac#4 (closed) 0x4cd6d82f in _IO_new_do_write () from /lib/libc.so.6 legacy/trac#5 (closed) 0x4cd6e006 in _IO_new_file_sync () from /lib/libc.so.6 legacy/trac#6 (closed) 0x4cd62c3c in fflush () from /lib/libc.so.6 legacy/trac#7 (closed) 0x080daaa7 in logv (severity=4, domain=2, funcname=0x0, format=0x8124004 "crypto error while %s: %s (in %s:%s)", ap=0x4aaa6eec "°<\022\baáõLÄßõL>ÀõLàV¾4\200") at log.c:295 legacy/trac#8 (closed) 0x080dad0e in _log (severity=4, domain=2, format=0x8124004 "crypto error while %s: %s (in %s:%s)") at log.c:314 legacy/trac#9 (closed) 0x080eb1a7 in crypto_log_errors (severity=4, doing=0x8123cb0 "generating DH key") at crypto.c:146 legacy/trac#10 (closed) 0x080ec104 in crypto_dh_generate_public (dh=0x34be56e0) at crypto.c:1467 legacy/trac#11 (closed) 0x080ec31b in crypto_dh_get_public (scrubbed) at crypto.c:1492 legacy/trac#12 (closed) 0x080a9e7e in onion_skin_server_handshake (scrubbed) at onion.c:267 legacy/trac#13 (closed) 0x08083a70 in cpuworker_main (data=0x4c2f2090) at cpuworker.c:284 legacy/trac#14 (closed) 0x080e11ed in tor_pthread_helper_fn (_data=0x4c2f20a0) at compat.c:1482 legacy/trac#15 (closed) 0x4ce5745b in start_thread () from /lib/libpthread.so.0 legacy/trac#16 (closed) 0x4cddb24e in clone () from /lib/libc.so.6
Unfortunately the logs were at notice. The node had just started, not much else was present. I'm rerunning it at info.
[Automatically added by flyspray2trac: Operating System: All]