tor unable to connect/use/get network consensus
When I start tor (note this is the new alpha version of tor-client!) it gets stuck as it cannot get network consensus for some reason, thus I cannot use tor at all.
I get the following syslog (excerpts):
Sep 16 01:15:20 test1 Tor[2337]: Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now. Sep 16 01:15:21 test1 Tor[2337]: OpenSSL OpenSSL 1.0.0d-fips 8 Feb 2011 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation Sep 16 01:15:22 test1 Tor[2337]: Reloaded microdescriptor cache. Found 0 descriptors. Sep 16 01:15:22 test1 Tor[2337]: I learned some more directory information, but not enough to build a circuit: We have no usable consensus. Sep 16 01:15:23 test1 Tor[2337]: Bootstrapped 5%: Connecting to directory server. Sep 16 01:15:23 test1 Tor[2337]: Heartbeat: Tor's uptime is 0:00 hours, with 6 circuits open. I've sent 0 kB and received 0 kB. Sep 16 01:15:23 test1 Tor[2337]: Bootstrapped 10%: Finishing handshake with directory server. Sep 16 01:15:25 test1 Tor[2337]: Bootstrapped 15%: Establishing an encrypted directory connection. Sep 16 01:15:25 test1 Tor[2337]: Bootstrapped 20%: Asking for networkstatus consensus. Sep 16 01:15:25 test1 Tor[2337]: Bootstrapped 50%: Loading relay descriptors. Sep 16 01:15:25 test1 Tor[2337]: I learned some more directory information, but not enough to build a circuit: We have no usable consensus. [...]
It doesn't progress any further. Please note that I am using bridges (about 3 of them, fully functional), but even if I alter torrc and switch to "normal" mode (i.e. with UseBridges 0) I get the same result - tor cannot get its network consensus to make a proper connection.
Please also note that tor 2.2.33 has no problems connecting (using the same torrc) and connects almost instantly, so I am thinking that there is something not tight there.
Trac:
Username: mr-4