networkstatus warning comes out of nowhere
... Feb 12 00:47:11.144 [Info] networkstatus_check_consensus_signature(): Looks like we need to download a new certificate from authority 'urras' at 208.83.223.34:443 (contact 1024D/9D0FACE4 Jacob Appelbaum jacob@appelbaum.net; identity 80550987E1D626E3EBA5E5E75A458DE0626D088C) Feb 12 00:47:11.145 [Info] networkstatus_check_consensus_signature(): Looks like we need to download a new certificate from authority 'moria1' at 128.31.0.34:9131 (contact 1024D/28988BF5 arma mit edu; identity D586D18309DED4CD6D57C18FDB97EFA96D330566) Feb 12 00:47:11.145 [Info] networkstatus_check_consensus_signature(): Looks like we need to download a new certificate from authority 'dizum' at tor.dizum.com:80 (contact 1024R/8D56913D Alex de Joode adejoode@sabotage.org; identity E8A9C45EDE6D711294FADF8E7951F4DE6CA56B58) Feb 12 00:47:11.145 [Info] networkstatus_check_consensus_signature(): Looks like we need to download a new certificate from authority 'gabelmoo' at 80.190.246.100:8180 (contact 1024D/F7C11265 Karsten Loesing ; identity ED03BB616EB2F60BEC80151114BB25CEF515B226) Feb 12 00:47:11.146 [Warning] 2 unknown, 7 missing key, 0 good, 0 bad, 2 no signature, 4 required Feb 12 00:47:11.146 [Info] networkstatus_set_current_consensus(): Not enough certificates to check networkstatus consensus Feb 12 00:47:11.146 [Notice] I learned some more directory information, but not enough to build a circuit: We have no network-status consensus. Feb 12 00:47:11.147 [Info] connection_dir_client_reached_eof(): Successfully loaded consensus ...
People running on log-level notice will just see that [warning] come out of nowhere. Looks like we got our severity screwed up there.
[Automatically added by flyspray2trac: Operating System: All]