You're currently not measured, per atlas it's been only 12 hours since this node has been online. It takes about three days to get a nominal measurement. I had a node on a 200mbps connection sit at 0bps for two days straight, then it finally had some movement in the evening of day three. I would wait at least another day and a half before worrying about this issue because it does take some time for the bandwidth measurements to complete. Please also review: https://blog.torproject.org/lifecycle-new-relay Regards, Conrad On Sunday, February 25, 2018 4:49:00 PM CST Gabe D. wrote: > https://metrics.torproject.org/rs.html#details/53CDD268FAD52B0236A4E7F478425 > 9A41C6E3414 > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > On 24 February 2018 5:59 PM, s7r <s7r@xxxxxxxxxx> wrote: > > Gabe D. wrote: > > > Feb 24 10:45:08.668 \[notice\] Tor 0.3.2.9 (git-64a719dd25a21acb) > > > running on Linux with Libevent 2.0.19-stable, OpenSSL 1.0.1t, Zlib > > > 1.2.7, Liblzma N/A, and Libzstd N/A. > > > > > > Feb 24 10:45:08.668 \[notice\] Tor can't help you if you use it wrong! > > > Learn how to be safe at https://www.torproject.org/downl > > > oad/download#warning > > > > > > Feb 24 10:45:08.668 \[notice\] Read configuration file "/etc/tor/torrc". > > > > > > Feb 24 10:45:08.671 \[notice\] Based on detected system memory, > > > MaxMemInQueues is set to 2891 MB. You can override this by sett ing > > > MaxMemInQueues by hand. > > > > > > Feb 24 10:45:08.671 \[notice\] Scheduler type KIST has been enabled. > > > > > > Feb 24 10:45:08.671 \[notice\] Opening Socks listener on 127.0.0.1:9050 > > > > > > Feb 24 10:45:08.671 \[notice\] Opening Control listener on > > > 127.0.0.1:9051 > > > > > > Feb 24 10:45:08.671 \[notice\] Opening OR listener on 0.0.0.0:9001 > > > > > > Feb 24 10:45:08.671 \[notice\] Opening Directory listener on 0.0.0.0:80 > > > > > > Feb 24 10:45:08.000 \[notice\] Not disabling debugger attaching for > > > unprivileged users. > > > > > > Feb 24 10:45:08.000 \[notice\] Parsing GEOIP IPv4 file > > > /usr/share/tor/geoip. > > > > > > Feb 24 10:45:08.000 \[notice\] Parsing GEOIP IPv6 file > > > /usr/share/tor/geoip6. > > > > > > Feb 24 10:45:08.000 \[notice\] Configured to measure statistics. Look > > > for the *-stats files that will first be written to the d ata directory > > > in 24 hours from now. > > > > > > Feb 24 10:45:08.000 \[warn\] You are running Tor as root. You don't need > > > to, and you probably shouldn't. > > > > > > Feb 24 10:45:08.000 \[notice\] Your Tor server's identity key > > > fingerprint is '123' > > > > > > Feb 24 10:45:08.000 \[notice\] Bootstrapped 0%: Starting > > > > > > Feb 24 10:45:09.000 \[notice\] Starting with guard context "default" > > > > > > Feb 24 10:45:09.000 \[notice\] Bootstrapped 80%: Connecting to the Tor > > > network > > > > > > Feb 24 10:45:10.000 \[notice\] Bootstrapped 85%: Finishing handshake > > > with first hop > > > > > > Feb 24 10:45:11.000 \[notice\] Bootstrapped 90%: Establishing a Tor > > > circuit > > > > > > Feb 24 10:45:12.000 \[notice\] Tor has successfully opened a circuit. > > > Looks like client functionality is working. > > > > > > Feb 24 10:45:12.000 \[notice\] Bootstrapped 100%: Done > > > > > > Feb 24 10:45:12.000 \[notice\] Now checking whether ORPort ***:9001 and > > > DirPort ***:80 are reachable... (th is may take up to 20 minutes -- > > > look for log messages indicating success) > > > > > > Feb 24 10:45:13.000 \[notice\] Self-testing indicates your DirPort is > > > reachable from the outside. Excellent. > > > > > > Feb 24 10:45:13.000 \[notice\] Self-testing indicates your ORPort is > > > reachable from the outside. Excellent. Publishing server d escriptor. > > > > > > Feb 24 10:45:14.000 \[notice\] Performing bandwidth self-test...done. > > > > You need to give us the IP address of the relay so that one can check if > > > > the ORPort is reachable. It should be, since that is indicated in the > > > > log messages but doesn't hurt to check. > > > > It takes some time until you can see it on atlas / relay search, it's > > > > not instant. Give it up to 24 hours. You will see it earlier here (but > > > > not instantly under any circumstances): > > > > https://consensus-health.torproject.org/consensus-health.html > > > > (careful, large page and can take some time to load) by searching for > > > > your nickname or fingerprint - see what the directory authorities have > > > > to say about your relay. > > > > The IP addresses of all relays in the network are public and not > > > > considered sensible information, but I can see a possibility where you > > > > don't want a certain IP address tied to the email you are posting here > > > > with, so it's up to you to decide but you can go to a port checking > > > > website (google it) and check the relay IP address ORPort if open or not. > > > > If yes, wait for 24 hours and check back on relay search. > > > > tor-relays mailing list > > > > tor-relays@xxxxxxxxxxxxxxxxxxxx > > > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > _______________________________________________ > tor-relays mailing list > tor-relays@xxxxxxxxxxxxxxxxxxxx > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays