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

Re: Directory issues

To: or-talk@xxxxxxxxxxxxx
Subject: Re: Directory issues
From: Mike Cardwell <tor@xxxxxxxxxxxxxxxxxx>
Date: Mon, 13 Aug 2007 12:51:52 +0100
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Mon, 13 Aug 2007 07:52:02 -0400
In-reply-to: <4ef5fec60708130110l19e68d5ci48d6e55d0634692a@xxxxxxxxxxxxxx>
References: <540d634a0708122136q745706f0tf25d633c52e9736d@xxxxxxxxxxxxxx> <4ef5fec60708122252q79364207y9a5a224207b97d9c@xxxxxxxxxxxxxx> <46C00EB9.2010900@xxxxxxxxx> <4ef5fec60708130110l19e68d5ci48d6e55d0634692a@xxxxxxxxxxxxxx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)

* on the Mon, Aug 13, 2007 at 01:10:01AM -0700, coderman wrote:

> On 8/13/07, vikingserver@xxxxxxxxx <vikingserver@xxxxxxxxx> wrote:
>>
>>  I have the same problem. 3 days of "not enough to build a circuit".
>>  Server: Viking, WinXp Vidalia 0.0.13 Tor 0.2.0.4
>>
>>  But right now Tor seems to work again...
> 
> your descriptors are published regularly as well.
> 
> is it possible both of you are experiencing clock skew / incorrect system times?

I had the same issue after upgrading. Restarting tor didn't seem to
help. I did:

rm -rf /var/lib/tor/cached-* /var/lib/tor/bw_accounting

followed by restarting tor, and it started working again. I wasn't sure if
that was just a fluke at the time so never brought it up.

Mike

Follow-Ups:
- Re: Directory issues
  - From: Josh McFarlane

References:
- Directory issues
  - From: Josh McFarlane
- Re: Directory issues
  - From: coderman
- Re: Directory issues
  - From: vikingserver@xxxxxxxxx
- Re: Directory issues
  - From: coderman

Prev by Author: ModSecurity v2 Apache rules for directory servers
Next by Author: Re: ModSecurity v2 Apache rules for directory servers
Previous by thread: Re: Directory issues
Next by thread: Re: Directory issues
Index(es):
- Author
- Thread