Re: Received http status code 503 ("Directory unavailable") from server

[Roger Dingledine <arma@xxxxxxx>]

On Wed, Jun 20, 2007 at 07:14:31PM -0700, Steve Southam wrote:
> Anyone seen this message before:
> 
> Jun 20 19:03:39.222 [info] connection_dir_request_failed(): Giving up on 
> directory server at '82.103.132.40:80'; retrying
> Jun 20 19:03:39.240 [info] connection_dir_client_reached_eof(): Received 
> http status code 503 ("Directory unavailable") from server 
> '82.103.132.40:80'. I'll try again soon.
> 
> Strange this is, this node shows up in the cached-status files as Exit 
> Fast Guard Stable Running Valid V2Dir with a pretty recent timestamp
> 
> Any ideas?

Look through src/or/connection.c for "Directory unavailable". This
happens when you try to ask for a v1-style directory object (either
a full directory or a running-routers list), and the directory mirror
doesn't have a suitable copy yet.

Most commonly this is because the server just started and hasn't found
a copy it likes yet.

With more and more Tor servers upgrading to 0.1.2.x and later, it will
become increasingly rare to find copies of the v1 directory objects (since
they will decline to serve them more often, sending a "503 Directory busy,
try again later").

I just checked the server you queried, and got a 503 as you say.

Then I queried it for /tor/server/authority and it told me it had an
uptime of 3 seconds (as of earlier today) and was named 'zealand'. The
IP and nickname aren't mentioned in any network-status documents I can
find.

Perhaps this is in your own private Tor network? Anything else you
aren't mentioning? :)

--Roger