[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #18351 [Tor]: Relay directory failures and logging are too aggressive
#18351: Relay directory failures and logging are too aggressive
------------------------------------------------+--------------------------
Reporter: sysrqb | Owner:
Type: defect | Status: closed
Priority: High | Milestone: Tor:
Component: Tor | 0.2.8.x-final
Severity: Normal | Version: Tor:
Keywords: regression, must-fix-before-028-rc | 0.2.8.1-alpha
Parent ID: | Resolution: fixed
Reviewer: | Actual Points:
| Points:
| Sponsor: None
------------------------------------------------+--------------------------
Comment (by Christian):
The latest ```git-d5f50cb052a535b5``` compiles, starts, but then crashed
after 4 minutes with:
{{{
Mar 24 14:49:51.000 [notice] Bootstrapped 80%: Connecting to the Tor
network
Mar 24 14:49:51.000 [notice] New control connection opened from 127.0.0.1.
Mar 24 14:50:07.000 [err] tor_assertion_failed_(): Bug:
src/or/circuituse.c:119: circuit_is_acceptable: Assertion
conn->chosen_exit_name failed; aborting. (on Tor 0.2.8.1-alpha-dev
d5f50cb052a535b5)
Mar 24 14:50:07.000 [err] Bug: Assertion conn->chosen_exit_name failed in
circuit_is_acceptable at src/or/circuituse.c:119. Stack trace: (on Tor
0.2.8.1-alpha-dev d5f50cb052a535b5)
Mar 24 14:50:07.000 [err] Bug: /opt/tor/bin/tor(log_backtrace+0x74)
[0x202349c4] (on Tor 0.2.8.1-alpha-dev d5f50cb052a535b5)
Mar 24 14:50:07.000 [err] Bug:
/opt/tor/bin/tor(tor_assertion_failed_+0xb4) [0x20247034] (on Tor 0.2.8.1
-alpha-dev d5f50cb052a535b5)
Mar 24 14:50:07.000 [err] Bug: /opt/tor/bin/tor(+0xe4968) [0x201bc968]
(on Tor 0.2.8.1-alpha-dev d5f50cb052a535b5)
Mar 24 14:50:07.000 [err] Bug: /opt/tor/bin/tor(+0xe8558) [0x201c0558]
(on Tor 0.2.8.1-alpha-dev d5f50cb052a535b5)
Mar 24 14:50:07.000 [err] Bug:
/opt/tor/bin/tor(connection_ap_handshake_attach_circuit+0xdc) [0x201c0d5c]
(on Tor 0.2.8.1-alpha-dev d5f50cb052a535b5)
Mar 24 14:50:07.000 [err] Bug:
/opt/tor/bin/tor(connection_ap_attach_pending+0x1c8) [0x201e2e58] (on Tor
0.2.8.1-alpha-dev d5f50cb052a535b5)
Mar 24 14:50:07.000 [err] Bug: /opt/tor/bin/tor(do_main_loop+0x21c)
[0x20123f6c] (on Tor 0.2.8.1-alpha-dev d5f50cb052a535b5)
Mar 24 14:50:07.000 [err] Bug: /opt/tor/bin/tor(tor_main+0x1804)
[0x20127224] (on Tor 0.2.8.1-alpha-dev d5f50cb052a535b5)
Mar 24 14:50:07.000 [err] Bug: /opt/tor/bin/tor(main+0x30)
[0x2011ebd0] (on Tor 0.2.8.1-alpha-dev d5f50cb052a535b5)
Mar 24 14:50:07.000 [err] Bug: /lib/powerpc-linux-
gnu/libc.so.6(+0x23294) [0x1fb0a294] (on Tor 0.2.8.1-alpha-dev
d5f50cb052a535b5)
Mar 24 14:50:07.000 [err] Bug: /lib/powerpc-linux-
gnu/libc.so.6(+0x23454) [0x1fb0a454] (on Tor 0.2.8.1-alpha-dev
d5f50cb052a535b5)
}}}
But that may be a different bug altogether - sorry for spamming this bug
entry. I shall return to a stable Tor release to get my node up & running
again.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18351#comment:14>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs