Re: Client config help - TOR will not start - directory information "not enough to build a circuit"

[Pei Hanru <peihanru@xxxxxxxxx>]

On 2007-04-22 12:58 CST, Carlton B wrote:
> I installed v1.2.12-rc and find that TOR is unable to start (running as
> client).   The obvious message is that it can't connect to
> localhost:9051.  This is a first-time install, straight out of the box,
> no config changes made other than turning up the debug level.   Any
> takers to help me get the setup going?
> 
> I searched the wiki and web for the errors in the logs, got a couple of
> hits on the errors, but no responses.
> To my knowledge, none of my outbound ports are restricted.
> 
> Message log and debug log below:
> 
> Message log:
> Apr 22 00:34:46:390 [Notice] Tor v0.1.2.12-rc. This is experimental
> software. Do not rely on it for strong anonymity.
> Apr 22 00:34:46:406 [Notice] Initialized libevent version 1.3b using
> method win32. Good.
> Apr 22 00:34:46:406 [Notice] Opening Socks listener on 127.0.0.1:9050
> Apr 22 00:34:46:406 [Notice] Opening Control listener on 127.0.0.1:9051
> Apr 22 00:34:46:718 [Notice] I learned some more directory information,
> but not enough to build a circuit.
> 
> The debug log reads:
> Apr 22 00:08:41.531 [notice] Tor 0.1.1.26 opening new log file.
> Apr 22 00:08:41.531 [debug] parse_dir_server_line(): Trusted dirserver
> at 18.244.0.188:9031 (46DB)
> Apr 22 00:08:41.531 [debug] parse_dir_server_line(): Trusted dirserver
> at 18.244.0.114:80 (E45D)
> Apr 22 00:08:41.531 [debug] parse_dir_server_line(): Trusted dirserver
> at 86.59.21.38:80 (1F85)
> Apr 22 00:08:41.531 [debug] parse_dir_server_line(): Trusted dirserver
> at 140.247.60.64:80 (F5FC)
> Apr 22 00:08:41.531 [debug] parse_dir_server_line(): Trusted dirserver
> at 194.109.206.212:80 (EAD6)
> Apr 22 00:08:41.531 [info] or_state_load(): Loaded state from
> "C:\Documents and Settings\[scrubbed]\Application Data\tor/state"
> Apr 22 00:08:41.656 [info] read_file_to_str(): Could not stat
> "C:\Documents and Settings\[scrubbed]\Application Data\tor/cached-routers".
> Apr 22 00:08:41.656 [info] read_file_to_str(): Could not stat
> "C:\Documents and Settings\[scrubbed]\Application
> Data\tor/cached-routers.new".
> Apr 22 00:08:41.656 [info] update_router_have_minimum_dir_info(): We
> have 0 of 5 network statuses, and we want more than 2.
> Apr 22 00:08:41.656 [notice] I learned some more directory information,
> but not enough to build a circuit.
> Apr 22 00:08:41.656 [info] update_router_descriptor_client_downloads():
> Not enough networkstatus documents to launch requests.
> Apr 22 00:08:41.656 [info] update_router_descriptor_client_downloads():
> Not enough networkstatus documents to launch requests.
> Apr 22 00:08:41.656 [info] or_state_save(): Saved state to "C:\Documents
> and Settings\[scrubbed]\Application Data\tor/state"
> Apr 22 00:08:41.656 [info] update_networkstatus_client_downloads(): For
> 5/5 running directory servers, we have 0 live network-status documents.
> Downloading 5.
> Apr 22 00:08:41.656 [info] router_pick_directory_server(): No reachable
> router entries for dirservers. Trying them all again.
> Apr 22 00:08:41.656 [info] router_pick_directory_server(): Still no
> reachable router entries. Reloading and trying again.
> Apr 22 00:08:41.656 [info] read_file_to_str(): Could not stat
> "C:\Documents and Settings\[scrubbed]\Application Data\tor/cached-routers".
> Apr 22 00:08:41.656 [info] read_file_to_str(): Could not stat
> "C:\Documents and Settings\[scrubbed]\Application
> Data\tor/cached-routers.new".
> Apr 22 00:08:41.656 [info] directory_get_from_dirserver(): No router
> found for network status; falling back to dirserver list
> Apr 22 00:08:41.656 [debug] directory_initiate_command(): initiating
> network-status fetch
> Apr 22 00:08:41.656 [debug] connection_connect(): Connecting to
> [scrubbed]:80.
> Apr 22 00:08:41.656 [info] connection_connect(): connect() to
> [scrubbed]:80 failed: Connection refused [WSAECONNREFUSED ]
> Apr 22 00:08:41.656 [info] connection_dir_request_failed(): Giving up on
> directory server at '140.247.60.64'; retrying
> Apr 22 00:08:41.656 [info] update_router_have_minimum_dir_info(): We
> have 0 of 5 network statuses, and we want more than 2.

I think everything is OK judging from the log you gave. This is the
first time you start Tor, what Tor is doing here is:

1) it connects to one of the directory authority to get its
network-status document;
2) it connects to several directory mirrors to download other
authorities' network-status documents and enough router descriptors.

There's a threshold of how many network-status documents and router
descriptors Tor client should get before it begins to build circuit,
before then, Tor will tell you "...but not enough to build a circuit".

Since the Tor network is becoming larger and some servers are not very
fast, it's normal to take some time to build the first circuit.

So, what you should do is just calm down and wait for a while.

Hanru

(PS, these two entries are interesting:
Apr 22 00:34:46:390 [Notice] Tor v0.1.2.12-rc. This is experimental...
Apr 22 00:08:41.531 [notice] Tor 0.1.1.26 opening new log file.
Why the version numbers are different?)