After about 77% of the bootstrapping process, I consistently get an error/bug report in my tor.log, and my tor doesn't startup...
[err] channel_closed(): Bug: src/or/channel.c:1315: channel_closed: Assertion chan->state == CHANNEL_STATE_CLOSING || chan->state == CHANNEL_STATE_CLOSED || chan->state == CHANNEL_STATE_ERROR failed; aborting.
I compiled it with "bufferevents" and "threads" only.
Upgrading my dev-libs/libevent (from 2.0.14) to 2.0.20 makes my tor bootstrapping freeze consistently at 45%, consuming all of my cpu. No error messages get outputted to tor.log, just a cpu-hang.
It seems to work without bufferevents compiled in. (export USE=-bufferevents)
Thanks for the report. This is definitely an upstream issue (and one of the reasons I put the alphas in the tree, so we can help them debug).
If its not too much of a pain, can you post an strace of tor up to when it hangs.
strace -f -o tor.log /usr/bin/tor -f /etc/tor/torrc
Also, can you post your torrc. Just scrub anything that is private.
The only obvious problem I can see from the strace is 8400+ calls to "time(NULL)", within 3 seconds. The last messages in tor.log vary: "Bootstrapped 90%: Establishing a Tor circuit" "Bootstrapped 85%: Finishing handshake with first hop". I am forced to pkill -9 it.
I believe this may be the upstream bug report: https://trac.torproject.org/projects/tor/ticket/4588
(In reply to candrews from comment #5)
> I believe this may be the upstream bug report:
Its fixed in the latest 0.2.4 which have now gone stable upstream.