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

Re: descriptor published, but router missing from consensus

To: tor-relays@xxxxxxxxxxxxxx
Subject: Re: descriptor published, but router missing from consensus
From: Sebastian Hahn <mail@xxxxxxxxxxxxxxxxx>
Date: Fri, 9 Apr 2010 15:38:21 +0200
Delivered-to: archiver@xxxxxxxx
Delivered-to: tor-relays-outgoing@xxxxxxxx
Delivered-to: tor-relays@xxxxxxxxxxxxxx
Delivery-date: Fri, 09 Apr 2010 09:38:32 -0400
In-reply-to: <201004091225.o39CPs0d017091@xxxxxxxxxxxxx>
References: <201004091225.o39CPs0d017091@xxxxxxxxxxxxx>
Reply-to: tor-relays@xxxxxxxxxxxxxx
Sender: owner-tor-relays@xxxxxxxxxxxxxx


On Apr 9, 2010, at 2:25 PM, Scott Bennett wrote:

I started tor in relay mode early this a.m. It finisheduploading itsstartup descriptor (MYCROFTsOtherChild) at Apr 09 02:37:10.166 (CDT)andits speed update descriptor at Apr 09 02:57:30.830 (also CDT).However, it
is now after 7 a.m. CDT, and my relay has still not been listed in the
consensus documents. This is the first time I can remember such athing
happening to my node.


Does https://bugs.torproject.org/flyspray/index.php?do=details&id=1346
look like it might explain things?

Sebastian

References:
- descriptor published, but router missing from consensus
  - From: Scott Bennett

Prev by Author: RE: Google cache blocking non-exit relays?
Next by Author: Re: descriptor published, but router missing from consensus
Previous by thread: descriptor published, but router missing from consensus
Next by thread: Re: descriptor published, but router missing from consensus
Index(es):
- Author
- Thread