Just sent a request to the contact of three affected relays asking they post daemon log entries if they have them. Hopefully someone can retrieve the information and it will shed some light on what's happening.
At 10:33 1/13/2016 +1100, Tim Wilson-Brown - teor wrote: >>At 19:20 1/12/2016 +0100, Aeris wrote: >>>>Are you *absoultely* certain that the config >>>>was not fiddled with at the time of this event? >>> >>>After grepping some logs, seems 13/12 was the day of a Tor >>>upgrade : >>> >>>2015-12-13 10:47:31 upgrade tor:amd64 0.2.7.5-1~d80.jessie+1 >>>0.2.7.6-1~d80.jessie+1 >>>2015-12-13 10:48:39 configure tor:amd64 0.2.7.6-1~d80.jessie+1 >>> >>>Timing is good compare to the 10:48:46 of the consensus ! >>> >>>But I donât remember a config change after that, >>>perhaps only on /usr/share/tor/tor-service-defaults-torrc >>>or on a default config param change ? >>> >>>And perhaps the Tor reboot cause the DirPort to >>>be temporarily disabled (seems not human, only >>>2s duration) ? > >I wonder if the DirPort self-test finished ~62 seconds after the ORPort >self-test? >(Or, strictly, after the first descriptor was submitted?) > >That would explain the behaviour we're seeing here. >(And it shouldn't be grounds for exclusion as a fallback directory, let me see >what I can do.) >Logged in trac as #18050. ><https://trac.torproject.org/projects/tor/ticket/18050>https://trac.torproject.org/projects/tor/ticket/18050 > >Tim _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays