Re: [tor-relays] New tor relay not showing up on Atlas

[Karsten Loesing <karsten@xxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/09/16 04:33, teor wrote:
> 
>> On 1 Sep 2016, at 12:07, Marina Brown <catskillmarina@xxxxxxxxx>
>> wrote:
>> 
>> Hi All:
>> 
>> I've set up a new relay and it is not showing up on Atlas. This
>> is the Log output.
>> 
>> Sep 01 03:52:27.000 [notice] Bootstrapped 90%: Establishing a Tor
>> circuit Sep 01 03:52:27.000 [notice] Tor has successfully opened
>> a circuit. Looks like client functionality is wor king. Sep 01
>> 03:52:27.000 [notice] Bootstrapped 100%: Done Sep 01 03:52:27.000
>> [notice] Now checking whether ORPort 78.47.167.67:9001 is
>> reachable... (this may take up to 20 minutes -- look for log
>> messages indicating success) Sep 01 03:52:27.000 [notice]
>> Self-testing indicates your ORPort is reachable from the outside.
>> Excellent. Publishing server descriptor. Sep 01 03:53:28.000
>> [notice] Performing bandwidth self-test…done.
> 
> It looks like you might have set up your relay in the last hour.
> 
> Your relay did make it into the consensus for this hour (large
> page): 
> https://consensus-health.torproject.org/consensus-health-2016-09-01-01-00.html#27376BCE3867E999330C53981FA0A226870F042F
>
>  It just takes Atlas a little while to update.
> 
> Here's what the process looks like: The Tor authorities vote every
> hour at 50-55 minutes past the hour. Then they produce a consensus
> on the hour. Then Onionoo updates. Then Atlas uses Onionoo for the
> relay data.
> 
> Wait half an hour, and check Atlas again.

Uh, sorry, this is caused by something else: I paused the Onionoo
updater last night, because I first need to check how it handles data
from two different bridge authorities.  I figured it's better to serve
slightly outdated data than invalid data.  Atlas should be back to
normal later today.

In theory, Atlas would be able to tell its users that its data is stale:

https://trac.torproject.org/projects/tor/ticket/15178

All the best,
Karsten

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJXx+M/AAoJEC3ESO/4X7XBqcwH/3OYjqmWDOe8Nc35u1Ae+SZZ
PFP5ul46pub0NF9iIKTwMX75M2WIBchHhYGf/kd1M2piFZq0mc9nZw696xHJQs4A
0VUXzHQC9YD/l6n4t53SK+Tee1MDKiNrYzGXPh2pMV9QD3t3IFtIrNhd/50p5Yr6
EYfx6HLP4izHEHFOZoKhDbWhH7qIWPQLu0C7PkKQ72S8LOkFJtcixmaf3bvfYR5C
yf89epeJXPn3eB183jlmC8BPbR62Nwqn3TNmRAdfG7+dKCCJ/led6jWqrc7w7+gH
hDzQV8zU5N0RqGvp1XeVukkVueQnSC/D8MUZ3gDkkjJ0i0YRRUdXsSfmvvaPeo0=
=1KCY
-----END PGP SIGNATURE-----
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays