Ah, that explains it. Thanks a lot. First period ends in two days, and I'm not even close to the max yet, so hopefully I should get the flag soon.
Lucas On 13.12.2015 23:47, Tim Wilson-Brown - teor wrote: > >> On 14 Dec 2015, at 09:45, Random Tor Node Operator <c...@fu110.de <mailto:c...@fu110.de>> wrote: >> >> Hi, >> >> you didn't get the V2Dir flag with AccountingMax set on... I had to have the same experience with that. > > You will only get the V2Dir flag with AccountingMax on if your relay is sure it will never hit its bandwidth cap. > This will only happen after the first full period, if at all. > > Tim > >> >> ------------------------ >> Random Tor Node Operator >> >> hi >> Am 13.12.2015 um 23:32 schrieb Lucas Werkmeister: > Hi all! > > For some reason, my relay[1] isn't getting the HSDir and V2Dir flags. > This is the full config, sans comments (sed '/^#\|^$/d' /etc/tor/torrc): > > SocksPort 0 > DataDirectory /var/lib/tor > ORPort 9001 > Address 78.46.139.153 > Nickname BotIfMuvasfo > AccountingMax 7900 GB > AccountingStart month 15 00:00 > ContactInfo Lucas Werkmeister "6B89 5B8B 11A4 75B1 EC93 1698 FC46 2872 > 72AE 323F" <m...@lucaswerkmeister.de <mailto:m...@lucaswerkmeister.de>> > DirPort 9030 # what port to advertise for directory connections > ExitPolicy reject *:* # no exits allowed > > I reloaded the config several times since I uncommented the DirPort > line, and even restarted the relay earlier today just in case enabling > DirPort wasn't supported without restart. No luck - both Globe[1] and > Atlas[2] don't show the HSDir or V2Dir flags. > > A few months ago, I had the relay running on a different server. I had > enabled the DirPort there for a while, but eventually was forced to > disable it since the server couldn't handle the load. But back then, the > relay got the flags without any problem. Since I moved to a new server > (copying over the torrc and data directories), this doesn't seem to be > working anymore. (I am now on Debian 8, tor version 0.2.5.12; the old > server was on Debian 7, tor version 0.2.4.27.) > > Any ideas on what the problem here could be? > > Thanks a lot, > Lucas > > [1]: > https://globe.torproject.org/#/relay/C527AD7D47E9DEC163537A444F4F790433CD67F7 > [2]: > https://atlas.torproject.org/#details/C527AD7D47E9DEC163537A444F4F790433CD67F7 >>> >>> >>> _______________________________________________ >>> tor-relays mailing list >>> tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org> >>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >> >> >> _______________________________________________ >> tor-relays mailing list >> tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org> >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > Tim Wilson-Brown (teor) > > teor2345 at gmail dot com > PGP 968F094B > > teor at blah dot im > OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F > > > > _______________________________________________ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays