[tor-bugs] #10461 [Tor]: tor seems to ignore "DirServer" option

Tor Bug Tracker & Wiki blackhole at torproject.org
Sun Dec 22 11:50:18 UTC 2013


#10461: tor seems to ignore "DirServer" option
------------------------+------------------------------
     Reporter:  mr-4    |      Owner:
         Type:  defect  |     Status:  new
     Priority:  normal  |  Milestone:
    Component:  Tor     |    Version:  Tor: 0.2.4.18-rc
   Resolution:          |   Keywords:
Actual Points:          |  Parent ID:
       Points:          |
------------------------+------------------------------

Comment (by mr-4):

 Well, something isn't right! This is what I have at the top of my debug
 file log:

 [debug] {DIR} parse_dir_authority_line(): Trusted 100 dirserver at
 128.31.0.39:9131 (9695)
 [debug] {DIR} parse_dir_authority_line(): Trusted 111 dirserver at
 86.59.21.38:80 (847B)
 [debug] {DIR} parse_dir_authority_line(): Trusted 102 dirserver at
 194.109.206.212:80 (7EA6)
 [debug] {DIR} parse_dir_authority_line(): Trusted 16 dirserver at
 82.94.251.203:80 (4A0C)
 [debug] {DIR} parse_dir_authority_line(): Trusted 100 dirserver at
 76.73.17.194:9030 (F397)
 [debug] {DIR} parse_dir_authority_line(): Trusted 100 dirserver at
 212.112.245.170:80 (F204)
 [debug] {DIR} parse_dir_authority_line(): Trusted 100 dirserver at
 193.23.244.244:80 (7BE6)
 [debug] {DIR} parse_dir_authority_line(): Trusted 100 dirserver at
 208.83.223.34:443 (0AD3)
 [debug] {DIR} parse_dir_authority_line(): Trusted 100 dirserver at
 171.25.193.9:443 (BD6A)
 [debug] {DIR} parse_dir_authority_line(): Trusted 100 dirserver at
 154.35.32.5:80 (CF6D)


 Off these, at least 3 should be working: dannenberg, tor26 and maatuska (I
 have {US} in my ExcludedNodes list), but they don't! Even with explicitly
 adding the following to my torrc file:

 DirAuthority 95.223.60.130:9030 23155386E3B4B93B0294DB3A6263A8FAFE273255
 DirAuthority tor26 86.59.21.38:80 847B1F850344D7876491A54892F904934E4EB85D
 DirAuthority maatuska 171.25.193.9:443
 BD6A829255CB08E66FBE7D3748363586E46B3810
 DirAuthority 95.223.60.130:443 23155386E3B4B93B0294DB3A6263A8FAFE273255
 DirAuthority 89.245.227.226:9001 6CB447C4CBCC4F5BDB4BA096902C2956CB534999
 DirAuthority 89.245.227.226:9030 6CB447C4CBCC4F5BDB4BA096902C2956CB534999
 DirAuthority 109.228.139.83:9001 9DD97868543CB3CF432B96C082DFAC1FD16F6768

 I still get the following in my log:

 [info] {DIR} microdesc_cache_reload(): Reloaded microdescriptor cache.
 Found 0 descriptors.
 [info] {FS} tor_mmap_file(): Could not open "/var/lib/tor/cached-
 descriptors" for mmap(): No such file or directory
 [info] {FS} tor_mmap_file(): Could not open "/var/lib/tor/cached-
 extrainfo" for mmap(): No such file or directory
 [info] {DIR} I learned some more directory information, but not enough to
 build a circuit: We have no usable consensus.
 [info] {DIR} update_consensus_networkstatus_downloads(): Launching
 microdesc networkstatus consensus download.
 [info] {CIRC} entry_guards_set_from_config(): Adding configured EntryNodes
 '{EU},{AT},{HR},{CH},{CZ},{DK},{FI},{FR},{DE},{HU},{IT},{LU},{MT},{NL},{NO},{SK},{SI},{ES},{SE},{BE},{IS}'.
 [notice] {GENERAL} 0 entries in guards
 [info] {CIRC} compute_weighted_bandwidths(): Empty routerlist passed in to
 consensus weight node selection for rule weight as guard
 [info] {CIRC} smartlist_choose_node_by_bandwidth(): Empty routerlist
 passed in to old node selection for rule weight as guard
 [info] {DIR} directory_pick_generic_dirserver(): No router found for
 consensus network-status fetch; falling back to dirserver list.
 [info] {DIR} router_pick_dirserver_generic(): No dirservers are reachable.
 Trying them all again.
 [notice] {DIR} While fetching directory info, no running dirservers known.
 Will try again later. (purpose 14)
 [info] {GENERAL} or_state_save(): Saved state to "/var/lib/tor/state"

 Please note that at least 2 of the "default" directory authorities are NOT
 in any of my exclude list (which, to be fair, is quite extensive) - I
 checked and double-checked this yesterday.

 Even if any of them are in that list and tor cannot connect to them for
 this very reason, I would expect tor to tell me that (something like
 "trying to connect to XXX directory authority, but it is in your
 ExcludeNodes list" - the same way as it does with ordinary ExitNodes).

 The fact is that it doesn't!

 The above message shown "No dirservers are reachable. Trying them all
 again." is not helpful at all.

 Why are no dirservers available? Why is tor not able to connect to any of
 them? Why is tor not listing what directory servers is trying to connect
 to?

 These are answers I expect to get when I have the reporting level set that
 low (=debug). It is not acceptable for me to be scratching my head having
 to guess what tor is doing and what appears to be wrong, particularly when
 I asked tor to be reporting everything.

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


More information about the tor-bugs mailing list