[tor-relays] Relay Node not acquiring Guard Flag.

Beagle Bone beaglebone3xbt at gmail.com
Mon Feb 23 17:28:17 UTC 2015


Hey folks. 3xBT here, admin of the node of the same name. I was wondering
why my node has yet to pick up the Guard flag:

Fingerprint: D937161730610A5D66BDED6CF4D5C9692566D9FE

Feb 23 06:25:05.000 [notice] Tor 0.2.4.24 (git-e3c61213fb2dc49a) opening
new log file.
Feb 23 06:25:05.000 [notice] Configured to measure directory request
statistics, but no GeoIP database found. Please specify a GeoIP database
using the GeoIPFile option.
Feb 23 06:27:22.000 [notice] Your DNS provider gave an answer for
"lya67fieutqf6", which is not supposed to exist. Apparently they are
hijacking DNS failures. Trying to correct for this. We've noticed 1
possibly bad addre$
Feb 23 09:57:31.000 [notice] Heartbeat: Tor's uptime is 59 days 6:02 hours,
with 153 circuits open. I've sent 414.64 GB and received 394.25 GB.
Feb 23 09:57:31.000 [notice] Average packaged cell fullness: 97.080%
Feb 23 09:57:31.000 [notice] TLS write overhead: 3%
Feb 23 09:57:31.000 [notice] Circuit handshake stats since last time:
4059/4059 TAP, 3977/3977 NTor.
Feb 23 15:02:49.000 [notice] New control connection opened.
Feb 23 15:57:31.000 [notice] Heartbeat: Tor's uptime is 59 days 12:02
hours, with 158 circuits open. I've sent 416.55 GB and received 396.07 GB.
Feb 23 15:57:31.000 [notice] Average packaged cell fullness: 97.087%
Feb 23 15:57:31.000 [notice] TLS write overhead: 3%
Feb 23 15:57:31.000 [notice] Circuit handshake stats since last time:
6032/6033 TAP, 4055/4055 NTor.
Feb 23 17:23:54.000 [notice] New control connection opened.


Additional info: When traffic is 4Mbit/sec, CPU and memory load is at ~50%.

I'm also wondering why the log is only being written when I'm looking at
it, and if there was anything I could do to increase usage of allotted
bandwidth.

-3xBT
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20150223/bfc22512/attachment.html>


More information about the tor-relays mailing list