warnings in log related to consensus problems
Yesterday I had this in my logs:
Aug 19 06:25:08.854 [notice] Tor 0.2.1.19 opening new log file. Aug 19 11:11:24.080 [warn] couldn't find start of hashed material "network-status-version" Aug 19 11:11:24.080 [warn] Unable to compute digest of network-status Aug 19 11:11:24.080 [warn] Unable to parse networkstatus consensus Aug 19 11:11:24.080 [warn] Unable to load consensus directory downloaded from server '80.190.246.100:80'. I'll try again soon. Aug 19 14:15:21.864 [warn] 1 unknown, 0 missing key, 3 good, 0 bad, 2 no signature, 4 required Aug 19 14:15:21.864 [warn] Not enough good signatures on networkstatus consensus Aug 19 14:15:21.866 [warn] Unable to load consensus directory downloaded from server '128.31.0.34:9031'. I'll try again soon. Aug 19 14:25:30.496 [warn] 1 unknown, 0 missing key, 3 good, 0 bad, 2 no signature, 4 required Aug 19 14:25:30.496 [warn] Not enough good signatures on networkstatus consensus Aug 19 14:25:30.498 [warn] Unable to load consensus directory downloaded from server '86.59.21.38:80'. I'll try again soon. Aug 19 14:56:01.852 [warn] 1 unknown, 0 missing key, 3 good, 0 bad, 2 no signature, 4 required Aug 19 14:56:01.852 [warn] Not enough good signatures on networkstatus consensus Aug 19 14:56:01.854 [warn] Unable to load consensus directory downloaded from server '216.224.124.114:9030'. I'll try again soon. Aug 20 06:25:09.481 [notice] Received reload signal (hup). Reloading config and resetting internal state.
No idea where these warnings would come from. Does anyone with an authority have any useful logs?
[Automatically added by flyspray2trac: Operating System: All]