[tor-bugs] #19939 [Core Tor/Tor]: tor 0.2.2.35-1 Stuck at 25%: Loading networkstatus consensus

Thu Aug 18 20:04:35 UTC 2016

#19939: tor 0.2.2.35-1 Stuck at 25%: Loading networkstatus consensus
------------------------------+------------------------------------------
     Reporter:  maumue        |      Owner:
         Type:  defect        |     Status:  new
     Priority:  Medium        |  Milestone:
    Component:  Core Tor/Tor  |    Version:  Tor: 0.2.2.35
     Severity:  Normal        |   Keywords:  Consensus stuck bootstrapped
Actual Points:                |  Parent ID:
       Points:                |   Reviewer:
      Sponsor:                |
------------------------------+------------------------------------------
 Hello,

 since a few days, my tor 0.2.2.35-1 cannot build up a working circuit.
 Within tor's log file, I found:

 ...
 Aug 18 21:18:35.628 [notice] Bootstrapped 20%: Asking for networkstatus
 consensus.
 Aug 18 21:18:35.748 [notice] Bootstrapped 25%: Loading networkstatus
 consensus.
 Aug 18 21:18:36.020 [warn] Received http status code 404 ("Consensus not
 signed by sufficient number of requested authorities") from server
 '128.31.0.39:9101' while fetching consensus directory.
 Aug 18 21:20:09.018 [warn] Got a certificate for dannenberg, but we
 already have it. Maybe they haven't updated it. Waiting for a while.
 Aug 18 21:20:09.018 [notice] I learned some more directory information,
 but not enough to build a circuit: We have no network-status consensus.
 Aug 18 21:25:12.330 [warn] Got a certificate for dannenberg, but we
 already have it. Maybe they haven't updated it. Waiting for a while.
 Aug 18 21:25:12.330 [notice] I learned some more directory information,
 but not enough to build a circuit: We have no network-status consensus.
 Aug 18 21:47:03.404 [notice] Application request when we haven't used
 client functionality lately. Optimistically trying directory fetches
 again.
 Aug 18 21:47:04.145 [warn] Received http status code 404 ("Consensus not
 signed by sufficient number of requested authorities") from server
 '86.59.21.38:443' while fetching consensus directory.
 Aug 18 21:47:04.204 [notice] Application request when we haven't used
 client functionality lately. Optimistically trying directory fetches
 again.
 Aug 18 21:47:35.160 [warn] Received http status code 404 ("Consensus not
 signed by sufficient number of requested authorities") from server
 '193.23.244.244:443' while fetching consensus directory.
 Aug 18 21:47:36.411 [notice] Application request when we haven't used
 client functionality lately. Optimistically trying directory fetches
 again.
 Aug 18 21:47:36.552 [warn] Received http status code 404 ("Consensus not
 signed by sufficient number of requested authorities") from server
 '193.23.244.244:443' while fetching consensus directory.
 Aug 18 21:47:36.661 [notice] Application request when we haven't used
 client functionality lately. Optimistically trying directory fetches
 again.
 Aug 18 21:47:42.725 [warn] Received http status code 404 ("Consensus not
 signed by sufficient number of requested authorities") from server
 '208.83.223.34:80' while fetching consensus directory.
 Aug 18 21:47:44.810 [notice] Application request when we haven't used
 client functionality lately. Optimistically trying directory fetches
 again.
 Aug 18 21:48:07.294 [warn] Problem bootstrapping. Stuck at 25%: Loading
 networkstatus consensus. (Connection timed out; TIMEOUT; count 10;
 recommendation warn)
 Aug 18 21:48:08.667 [warn] Received http status code 404 ("Consensus not
 signed by sufficient number of requested authorities") from server
 '128.31.0.39:9101' while fetching consensus directory.
 Aug 18 21:48:09.410 [notice] Application request when we haven't used
 client functionality lately. Optimistically trying directory fetches
 again.
 Aug 18 21:48:39.917 [warn] Received http status code 404 ("Consensus not
 signed by sufficient number of requested authorities") from server
 '86.59.21.38:443' while fetching consensus directory.
 Aug 18 21:48:42.399 [notice] Application request when we haven't used
 client functionality lately. Optimistically trying directory fetches
 again.
 Aug 18 21:49:12.574 [warn] Problem bootstrapping. Stuck at 25%: Loading
 networkstatus consensus. (Connection timed out; TIMEOUT; count 11;
 recommendation warn)
 ...

 Things I've tried:
 - restart tor service
 - restart the machine
 - completly remove and reinstall package

 Installing tor-browser from ppa on this machine works without problems.
 But tor-browser is not my preferred solution (as a workaround - okay).
 On another machine within the same local network and newer linux-
 distribution tor 0.2.4.27-1build0.14.04 still works.
 So, it's unlikely to me a problem with a personal firewall (anyway none
 active) or router or ISP (I'm from DE).

 I found some old posts, where the resoultion was a to high clock skew. But
 mine is okay, e.g. from tor's debug.log
 Aug 18 18:20:50.217 [debug] connection_dir_client_reached_eof(): Time on
 received directory is within tolerance; we are -146 seconds skewed.
 (That's okay.)

 On another post it was advised to use a tor bridge, but I don't think this
 can be a solution as my second computer *can* build up a circuit.

 My system is Linux Mint Maya 13 (derived from Ubuntu 12.04 LTS) 64-Bit.
 There's no newer tor service package available for this distribution.

 Can anyone reproduce this with tor 0.2.2.35-1 ?

 Thanks, maumue

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19939>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online