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

2007-06-21 Thread Steve Southam
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

Received http status code 503 (Directory unavailable) from server

2007-06-20 Thread Steve Southam
Hi 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

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

2007-06-20 Thread Roger Dingledine
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