[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-relays] How long before a new relay shows up in Relay Search?
On Fri, 17 Aug 2018 10:57:51 -0400
Matt Traudt <pastly@xxxxxxxxxxxxxx> wrote:
> On 8/17/18 10:53, hanzer@xxxxxxxxxx wrote:
> > Hello,
> >
> > I've recently set up a new relay: Tor 0.3.3.7
> > (git-035a35178c92da94) on a FreeBSD-11.2 machine. The Tor server's
> > identity key fingerprint is:
> >
> > 'Chiron420 9C7BB4BCB58AC876D83B67277A0CF3BC73F4FDF6'
> >
> > A search for this relay on the metrics site says "No Results found!"
> >
> > <https://metrics.torproject.org/rs.html#search/Chiron420%209C7BB4BCB58AC876D83B67277A0CF3BC73F4FDF6>
> >
> > Is this typical or might there be something awry in my setup?
> >
>
> About 2 hours.
>
> Check Tor's log for errors.
>
> https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Verifythatyourrelayworks
>
> If you configured an IPv6 ORPort in addition to the (required) IPv4
> one, it must be working or else your relay will be considered down.
>
> Matt
IPv6 isn't enabled on this system/network. The relay reports an uptime
of about 12 hours and I don't see any problems in the log.
Aug 16 20:40:33.000 [notice] Now checking whether ORPort
174.49.19.50:9001 and DirPort 174.49.19.50:9030 are reachable... (this
may take up to 20 minutes -- look for log messages indicating success)
Aug 16 20:40:34.000 [notice] Self-testing indicates your DirPort is
reachable from the outside. Excellent.
Aug 16 20:40:35.000 [notice] Self-testing indicates your ORPort is
reachable from the outside. Excellent.
Aug 16 20:40:41.000 [notice] Performing bandwidth self-test...done. Aug
17 02:40:30.000 [notice] Heartbeat: It seems like we are not in the
cached consensus.
Aug 17 02:40:30.000 [notice] Heartbeat: Tor's uptime is 5:59 hours,
with 0 circuits open. I've sent 908 kB and received 5 .97 MB.
Aug 17 02:40:30.000 [notice] Circuit handshake stats since last time:
0/0 TAP, 4/4 NTor. Aug 17 02:40:30.000 [notice] Since startup, we have
initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 6
v4 connections; and received 0 v1 connections, 0 v2 connections, 0 v3
connections, and 0 v4 connections. Aug 17 02:40:30.000 [notice] DoS
mitigation since startup: 0 circuits killed with too many cells. 0
circuits rejected, 0 marked addresses. 0 connections closed. 0 single
hop clients refused.
Aug 17 08:40:30.000 [notice] Heartbeat: It seems like we are not in the
cached consensus. Aug 17 08:40:30.000 [notice] Heartbeat: Tor's uptime
is 11:59 hours, with 0 circuits open. I've sent 1.42 MB and received
11.56 MB.
Aug 17 08:40:30.000 [notice] Circuit handshake stats since last time:
0/0 TAP, 0/0 NTor.
Aug 17 08:40:30.000 [notice] Since startup, we have initiated
0 v1 connections, 0 v2 connections, 0 v3 connections, and 1 7 v4
connections; and received 0 v1 connections, 0 v2 connections, 0 v3
connections, and 0 v4 connections.
Aug 17 08:40:30.000 [notice] DoS mitigation since startup: 0 circuits
killed with too many cells. 0 circuits rejected, 0 marked addresses. 0
connections closed. 0 single hop clients refused.
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays