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

Re: Directory issues

To: or-talk@xxxxxxxxxxxxx
Subject: Re: Directory issues
From: "Josh McFarlane" <josh.mcfarlane@xxxxxxxxx>
Date: Mon, 13 Aug 2007 10:44:28 -0500
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Mon, 13 Aug 2007 11:44:45 -0400
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=W/ESATEiwfEJFvY5Lz2TfklfuayCiVk3P1MeeKzpjpQQ/J/XdiWS5ynjJX8kw7QOjDgwUU934FEPUhGsZs1R60MGLaJ5OVRXlK3D5krR8N9mpghfBAHPf8k3qn4/xQmch3styP2z2FdWWZmCghQOAztc5R/xwhFcjq84My/Z/Lo=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=AuYv3G/x/rN78rOr25CNsnjmUcjKjE3/rTIs7cM3JZJIEmdgB9HAjHoBxj8Ly/iWvMiKEg43ctRoy85k4xoCTds5n3NRRgORMUV7UvzpVWO/p7oYdhVPbPu1tI1LJampb47Tmzaz/JZ5rUT8Nr7pzpUSJ8II1Rp7NXhpjQjANBw=
In-reply-to: <20070813115152.GA13497@xxxxxxxxx>
References: <540d634a0708122136q745706f0tf25d633c52e9736d@xxxxxxxxxxxxxx> <4ef5fec60708122252q79364207y9a5a224207b97d9c@xxxxxxxxxxxxxx> <46C00EB9.2010900@xxxxxxxxx> <4ef5fec60708130110l19e68d5ci48d6e55d0634692a@xxxxxxxxxxxxxx> <20070813115152.GA13497@xxxxxxxxx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx

On 8/13/07, Mike Cardwell <tor@xxxxxxxxxxxxxxxxxx> wrote:
> 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.

Well, that solved my circuit issue, but I'm still not sure whether or
not it's properly pushing to the directory servers. Looking on
http://torstatus.kgprog.com/ still lists my server as .14, and has not
restarted my uptime even though I had to bring the service down and
restart. Anyone have any idea why?

-- 
Josh McFarlane

Follow-Ups:
- Re: Directory issues
  - From: Chris

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

Prev by Author: Directory issues
Next by Author: Re: Privoxy usage?
Previous by thread: Re: Directory issues
Next by thread: Re: Directory issues
Index(es):
- Author
- Thread