-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 01/09/16 04:33, teor wrote:
On 1 Sep 2016, at 12:07, Marina Brown catskillmarina@gmail.com 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.ht...
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