Perhaps this is a bug in the consensus system. Pulling the consensus archive and grepping, exactly the one single consensus is showing DirPort as zero:
12-13-09-cons:r kitten1 <fp> vG0ZWLi31UXoqz4H2H/hweSvxqo 04:44:19 62.210.124.124 9001 9030 12-13-10-cons:r kitten1 <fp> vG0ZWLi31UXoqz4H2H/hweSvxqo 04:44:19 62.210.124.124 9001 9030 12-13-11-cons:r kitten1 <fp> yUnPgGOwhq5QfUEe1Eg0zKCU+w0 10:48:46 62.210.124.124 9001 0 12-13-12-cons:r kitten1 <fp> JrZF6+VnnYZuQHRllufg53dbjH8 10:49:48 62.210.124.124 9001 9030 12-13-13-cons:r kitten1 <fp> JrZF6+VnnYZuQHRllufg53dbjH8 10:49:48 62.210.124.124 9001 9030 Are you *absoultely* certain that the config was not fiddled with at the time of this event? As can be seen, the descriptor hash changed twice which could indicate two config changes in rapid succession--could also indicate a BW or similar change. At 17:54 1/12/2016 +0100, Aeris wrote: >> DEBUG:root:86E78DD3720C78DA8673182EF96C54B162CD660C not a >candidate: changed >> address/port recently (2015-12-13 11:00:00) > >Hum Donât know how is it possible, this relay has the samee >IP/port since it >creation 1 year ago. > >From CollecTor, seems there is only a single network glitch, and >only on the >DirPort (OR port stable). > >$ wget >https://collector.torproject.org/archive/relay-descriptors/micro >descs/ >microdescs-2015-12.tar.xz >$ tar xf microdescs-2015-12.tar.xz >$ cd microdescs-2015-12/consensus-microdesc >$ rgrep kitten1 | awk '{print $2,$3,$6,$7,$8}' | sort | uniq -c > 1 kitten1 hueN03IMeNqGcxgu+WxUsWLNZgw 62.210.124.124 9001 0 > 735 kitten1 hueN03IMeNqGcxgu+WxUsWLNZgw 62.210.124.124 9001 >9030 >$ rgrep kitten1 | grep "9001 0" >13/2015-12-13-11-00-00-consensus-microdesc:r kitten1 >hueN03IMeNqGcxgu >+WxUsWLNZgw 2015-12-13 10:48:46 62.210.124.124 9001 0 > >:'( > >-- >Aeris _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
