I am a n00b relay (OnionTorte) operator, and, as such, know lamentably little of what I'm doing. (Yes, I'm one of *those* relay operators.) When I went to bed last night I had an HSDir flag, but it has since disappeared. And since this A.M. my consensus was halved. A bit of promiscuous pokings-about in relay metrics leads me to think that this happened in the wake of my having had to reboot my machine to unwedge it. Speed Test shows that even on the worst of BadHair Days my u/l speed doesn't sink below 15Mb/s (1900KB/s), and almost always cruises at
25Mb/s, so I don't think that it's so much a bandwidth issue as one of
perceived reliability. :(
I read https://blog.torproject.org/blog/lifecycle-of-a-new-relay
but wasn't able to take away as much as I would have liked. If somebody can explain to me, using small words and interpretive dance as befits a callow contributor, what happened I should certainly appreciate it.
Thanks,
P
On Feb 28, 2014, at 21:05 , Tor Relay wrote:
When I went to bed last night I had an HSDir flag, but it has since disappeared. And since this A.M. my consensus was halved. A bit of promiscuous pokings-about in relay metrics leads me to think that this happened in the wake of my having had to reboot my machine to unwedge it.
Yes, after rebooting it takes 25 hours to gain the HSDir flag. At time of writing, your uptime is just over 17 hours.
This is from the dir spec:
"HSDir" -- A router is a v2 hidden service directory if it stores and serves v2 hidden service descriptors, and the authority believes that it's been up for at least 25 hours (or the current value of MinUptimeHidServDirectoryV2).
Directory server administrators may label some relays or IPs as blacklisted, and elect not to include them in their network-status lists.
Full dir spec: https://gitweb.torproject.org/torspec.git/blob_plain/HEAD:/dir-spec.txt
-Job
tor-relays@lists.torproject.org