[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: Directory server errors: can't connect

To: or-talk@xxxxxxxxxxxxx
Subject: Re: Directory server errors: can't connect
From: David MacDonald <dbmacdon@xxxxxxxxx>
Date: Tue, 4 Sep 2007 12:46:34 +0300
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Tue, 04 Sep 2007 05:46:53 -0400
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-YMail-OSG:Mime-Version:In-Reply-To:References:Content-Type:Message-Id:Content-Transfer-Encoding:From:Subject:Date:To:X-Mailer; b=S6iIoKVGCKeQVbqom7NZwXqfW08Rl5cpsZcezxf6uKqOlJdvOQu5M9EiyIAAw7H7iq06rk0C4s++UYVPOAdTqr4sDU+EaUOLd8JNQ4KwGpHshidgLDGykNaLYGgGNQpOI1OdgqrRon3qLz5DrXbI2sBZZpdUcFM/UBbtDUCwWMM= ;
In-reply-to: <4A9362B1-C18B-496C-88F6-AC3C97513AC6@xxxxxxxxx>
References: <4A9362B1-C18B-496C-88F6-AC3C97513AC6@xxxxxxxxx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx

I've been using tor successfully in Saudi Arabia for over 2 years (OSX). Suddenly I can no longer connect due to 'server errors':

Sep 02 07:41:23.407 [Notice] Tor v0.1.2.17. This is experimentalsoftware. Do not rely on it for strong anonymity.Sep 02 07:41:23.410 [Notice] Enabling experimental OS X kqueuesupport with libevent 1.3d. If this turns out to not work, set theenvironment variable EVENT_NOKQUEUE, and tell the Tor developers.Sep 02 07:41:23.412 [Notice] Initialized libevent version 1.3d usingmethod kqueue. Good.

Sep 02 07:41:23.415 [Notice] Opening Socks listener on 127.0.0.1:9050
Sep 02 07:41:23.417 [Notice] Opening Control listener on 127.0.0.1:9051

Sep 02 07:42:25.098 [Warning] Received http status code 500 ("ServerError") from server '140.247.60.64:80' while fetching "/tor/status/fp/38D4F5FCF7B1023228B895EA56EDE7D5CCDCAF32+719BE45DE224B607C53707D0E2143E2D423E74CF+7EA6EAD6FD83083C538F44038BBFA077587DD755+847B1F850344D7876491A54892F904934E4EB85D+FFCB46DB1339DA84674C70D7CB586434C4370441.z". I'll try again soon.Sep 02 07:43:35.673 [Notice] Tried for 120 seconds to get aconnection to [scrubbed]:80. Giving up. (waiting for circuit)Sep 02 07:47:30.766 [Warning] Received http status code 500 ("ServerError") from server '86.59.21.38:80' while fetching "/tor/status/fp/38D4F5FCF7B1023228B895EA56EDE7D5CCDCAF32+719BE45DE224B607C53707D0E2143E2D423E74CF+7EA6EAD6FD83083C538F44038BBFA077587DD755+847B1F850344D7876491A54892F904934E4EB85D+FFCB46DB1339DA84674C70D7CB586434C4370441.z". I'll try again soon.Sep 02 07:49:31.912 [Warning] Received http status code 500 ("ServerError") from server '194.109.206.212:80' while fetching "/tor/status/fp/38D4F5FCF7B1023228B895EA56EDE7D5CCDCAF32+719BE45DE224B607C53707D0E2143E2D423E74CF+7EA6EAD6FD83083C538F44038BBFA077587DD755+847B1F850344D7876491A54892F904934E4EB85D+FFCB46DB1339DA84674C70D7CB586434C4370441.z". I'll try again soon.....

Repeated efforts to connect to the same three servers continueindefinitely without success. The problem first appeared immediatelyafter upgrading to v0.1.2.17, but also affects v0.1.2.16 that hadpreviously been working fine.


Could someone kindly help me resolve this problem?

Regards to all

References:
- Directory server errors: can't connect
  - From: David MacDonald

Prev by Author: Directory server errors: can't connect
Next by Author: Re: Directory server errors: can't connect
Previous by thread: Re: Directory server errors: can't connect
Next by thread: Re: Directory server errors: can't connect
Index(es):
- Author
- Thread