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

Re: upgrate to .13-alpha now no traffic? [FIXED]

To: or-talk@xxxxxxxxxxxxx
Subject: Re: upgrate to .13-alpha now no traffic? [FIXED]
From: Michael Holstein <michael.holstein@xxxxxxxxxxx>
Date: Tue, 28 Feb 2006 12:05:32 -0500
Delivered-to: archiver@seul.org
Delivered-to: or-talk-outgoing@seul.org
Delivered-to: or-talk@seul.org
Delivery-date: Tue, 28 Feb 2006 12:05:56 -0500
In-reply-to: <44046A07.5030703@csuohio.edu>
References: <44046199.10700@csuohio.edu> <44046A07.5030703@csuohio.edu>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.7.1 (X11/20040626)

Okay .. tried .14-alpha from source .. still getting a lot of these in debug :

Feb 28 10:18:52.349 [info] connection_read_to_buf(): tls error. breaking (nickname $2FD8FC5E53BEFA292E7FE69B4F454979765336AC, address 127.0.0.1).

Found the problem ... and this is a note to the FreeBSD ports maintainer .. .12 and .13 used different places for their data directories (both were installed from ports)

.12-alpha used /var/db/tor
.13-alpha used /var/run/tor

This caused new keys to get generated that weren't valid for my server, thus it'd never publish it's descriptor. Fixing the init script for TOR to reflect this new directory (it ignores what's in the config file) and replacing the keys with my backup copy immediately fixed the problem.

~Mike.

References:
- upgrate to .13-alpha now no traffic?
  - From: Michael Holstein
- Re: upgrate to .13-alpha now no traffic?
  - From: Michael Holstein

Prev by Author: Re: upgrate to .13-alpha now no traffic?
Next by Author: Circuits still shared?
Previous by thread: Re: upgrate to .13-alpha now no traffic?
Index(es):
- Author
- Thread