- tor-consensus-health - lists.torproject.org

Consensus issues
by atagar＠torproject.org 04 Jan '17

04 Jan '17

ERROR: Unable to retrieve the consensus from longclaw (http://199.254.238.52:80/tor/status-vote/current/consensus.z) <urlopen error [Errno 111] Connection refused> ERROR: Unable to retrieve the consensus from dannenberg (http://193.23.244.244:80/tor/status-vote/current/consensus.z) <urlopen error [Errno 111] Connection refused> ERROR: Unable to retrieve the vote from longclaw (http://199.254.238.52:80/tor/status-vote/current/authority.z) <urlopen error [Errno 111] Connection refused> ERROR: Unable to retrieve the vote from dannenberg (http://193.23.244.244:80/tor/status-vote/current/authority.z) <urlopen error [Errno 111] Connection refused> WARNING: The certificate of the following directory authority expires within the next week: maatuska (2017-01-06 20-08-14) NOTICE: Consensus fetched from maatuska was missing the following authority signatures: dannenberg NOTICE: Consensus fetched from tor26 was missing the following authority signatures: dannenberg NOTICE: Consensus fetched from dizum was missing the following authority signatures: dannenberg NOTICE: Consensus fetched from gabelmoo was missing the following authority signatures: dannenberg NOTICE: Consensus fetched from moria1 was missing the following authority signatures: dannenberg NOTICE: Consensus fetched from Faravahar was missing the following authority signatures: dannenberg WARNING: The following directory authorities are not reporting bandwidth scanner results: maatuska WARNING: The following authorities are missing from the consensus: dannenberg WARNING: Unable to reach the ORPort of longclaw (2620:13:4000:8000:60:f3ff:fea1:7cff, port 443): [Errno 111] Connection refused

1 0

Consensus issues
by atagar＠torproject.org 03 Jan '17

03 Jan '17

ERROR: Unable to retrieve the consensus from dannenberg (http://193.23.244.244:80/tor/status-vote/current/consensus.z) <urlopen error [Errno 111] Connection refused> ERROR: Unable to retrieve the vote from dannenberg (http://193.23.244.244:80/tor/status-vote/current/authority.z) <urlopen error [Errno 111] Connection refused> WARNING: The certificate of the following directory authority expires within the next week: maatuska (2017-01-06 20-08-14) NOTICE: Consensus fetched from maatuska was missing the following authority signatures: dannenberg NOTICE: Consensus fetched from tor26 was missing the following authority signatures: dannenberg NOTICE: Consensus fetched from longclaw was missing the following authority signatures: dannenberg NOTICE: Consensus fetched from dizum was missing the following authority signatures: dannenberg NOTICE: Consensus fetched from gabelmoo was missing the following authority signatures: dannenberg NOTICE: Consensus fetched from moria1 was missing the following authority signatures: dannenberg NOTICE: Consensus fetched from Faravahar was missing the following authority signatures: dannenberg WARNING: The following directory authorities are not reporting bandwidth scanner results: maatuska WARNING: The following authorities are missing from the consensus: dannenberg

1 0

Consensus issues
by atagar＠torproject.org 03 Jan '17

03 Jan '17

ERROR: Unable to retrieve the consensus from dannenberg (http://193.23.244.244:80/tor/status-vote/current/consensus.z) <urlopen error [Errno 111] Connection refused> ERROR: Unable to retrieve the vote from dannenberg (http://193.23.244.244:80/tor/status-vote/current/authority.z) <urlopen error [Errno 111] Connection refused> WARNING: The following directory authorities do not support the consensus method that the consensus uses: Faravahar WARNING: The certificate of the following directory authority expires within the next week: maatuska (2017-01-06 20-08-14) NOTICE: Consensus fetched from maatuska was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from tor26 was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from longclaw was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from dizum was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from gabelmoo was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from moria1 was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from Faravahar was missing the following authority signatures: dannenberg, Faravahar WARNING: The following directory authorities are not reporting bandwidth scanner results: maatuska WARNING: The following authorities are missing from the consensus: dannenberg

1 0

Consensus issues
by atagar＠torproject.org 03 Jan '17

03 Jan '17

ERROR: Unable to retrieve the consensus from dannenberg (http://193.23.244.244:80/tor/status-vote/current/consensus.z) <urlopen error [Errno 111] Connection refused> ERROR: Unable to retrieve the vote from maatuska (http://171.25.193.9:443/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from tor26 (http://86.59.21.38:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from longclaw (http://199.254.238.52:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from dizum (http://194.109.206.212:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from gabelmoo (http://131.188.40.189:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from moria1 (http://128.31.0.39:9131/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from dannenberg (http://193.23.244.244:80/tor/status-vote/current/authority.z) <urlopen error [Errno 111] Connection refused> WARNING: The following directory authorities do not support the consensus method that the consensus uses: Faravahar NOTICE: Consensus fetched from maatuska was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from tor26 was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from longclaw was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from dizum was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from gabelmoo was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from moria1 was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from Faravahar was missing the following authority signatures: dannenberg, Faravahar WARNING: The following authorities are missing from the consensus: dannenberg

1 0

Consensus issues
by atagar＠torproject.org 03 Jan '17

03 Jan '17

ERROR: Unable to retrieve the consensus from dannenberg (http://193.23.244.244:80/tor/status-vote/current/consensus.z) <urlopen error [Errno 111] Connection refused> ERROR: Unable to retrieve the vote from maatuska (http://171.25.193.9:443/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from tor26 (http://86.59.21.38:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from longclaw (http://199.254.238.52:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from dizum (http://194.109.206.212:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from gabelmoo (http://131.188.40.189:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from moria1 (http://128.31.0.39:9131/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from dannenberg (http://193.23.244.244:80/tor/status-vote/current/authority.z) <urlopen error [Errno 111] Connection refused> WARNING: The following directory authorities do not support the consensus method that the consensus uses: Faravahar NOTICE: Consensus fetched from maatuska was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from tor26 was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from longclaw was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from dizum was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from gabelmoo was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from moria1 was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from Faravahar was missing the following authority signatures: dannenberg, Faravahar WARNING: The following authorities are missing from the consensus: dannenberg

1 0

Consensus issues
by atagar＠torproject.org 03 Jan '17

03 Jan '17

ERROR: Unable to retrieve the consensus from dannenberg (http://193.23.244.244:80/tor/status-vote/current/consensus.z) <urlopen error [Errno 111] Connection refused> ERROR: Unable to retrieve the vote from maatuska (http://171.25.193.9:443/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from tor26 (http://86.59.21.38:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from longclaw (http://199.254.238.52:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from dizum (http://194.109.206.212:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from gabelmoo (http://131.188.40.189:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from moria1 (http://128.31.0.39:9131/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from dannenberg (http://193.23.244.244:80/tor/status-vote/current/authority.z) <urlopen error [Errno 111] Connection refused> WARNING: The following directory authorities do not support the consensus method that the consensus uses: Faravahar NOTICE: Consensus fetched from maatuska was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from tor26 was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from longclaw was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from dizum was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from gabelmoo was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from moria1 was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from Faravahar was missing the following authority signatures: dannenberg, Faravahar WARNING: The following authorities are missing from the consensus: dannenberg

1 0

Consensus issues
by atagar＠torproject.org 02 Jan '17

02 Jan '17

ERROR: Unable to retrieve the consensus from dannenberg (http://193.23.244.244:80/tor/status-vote/current/consensus.z) <urlopen error [Errno 111] Connection refused> ERROR: Unable to retrieve the vote from maatuska (http://171.25.193.9:443/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from tor26 (http://86.59.21.38:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from longclaw (http://199.254.238.52:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from dizum (http://194.109.206.212:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from gabelmoo (http://131.188.40.189:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from moria1 (http://128.31.0.39:9131/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from dannenberg (http://193.23.244.244:80/tor/status-vote/current/authority.z) <urlopen error [Errno 111] Connection refused> WARNING: The following directory authorities do not support the consensus method that the consensus uses: Faravahar NOTICE: Consensus fetched from maatuska was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from tor26 was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from longclaw was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from dizum was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from gabelmoo was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from moria1 was missing the following authority signatures: dannenberg, Faravahar NOTICE: Consensus fetched from Faravahar was missing the following authority signatures: dannenberg, Faravahar WARNING: The following authorities are missing from the consensus: dannenberg

1 0

Consensus issues
by atagar＠torproject.org 02 Jan '17

02 Jan '17

ERROR: Unable to retrieve the consensus from dannenberg (http://193.23.244.244:80/tor/status-vote/current/consensus.z) <urlopen error [Errno 111] Connection refused> ERROR: Unable to retrieve the vote from maatuska (http://171.25.193.9:443/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from tor26 (http://86.59.21.38:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from longclaw (http://199.254.238.52:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from dizum (http://194.109.206.212:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from gabelmoo (http://131.188.40.189:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from moria1 (http://128.31.0.39:9131/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from dannenberg (http://193.23.244.244:80/tor/status-vote/current/authority.z) <urlopen error [Errno 111] Connection refused> WARNING: The following directory authorities do not support the consensus method that the consensus uses: Faravahar NOTICE: Consensus fetched from maatuska was missing the following authority signatures: Faravahar NOTICE: Consensus fetched from tor26 was missing the following authority signatures: Faravahar NOTICE: Consensus fetched from longclaw was missing the following authority signatures: Faravahar NOTICE: Consensus fetched from dizum was missing the following authority signatures: Faravahar NOTICE: Consensus fetched from gabelmoo was missing the following authority signatures: Faravahar NOTICE: Consensus fetched from moria1 was missing the following authority signatures: Faravahar NOTICE: Consensus fetched from Faravahar was missing the following authority signatures: Faravahar

1 0

Consensus issues
by atagar＠torproject.org 02 Jan '17

02 Jan '17

ERROR: Unable to retrieve the vote from maatuska (http://171.25.193.9:443/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from tor26 (http://86.59.21.38:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from longclaw (http://199.254.238.52:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from dizum (http://194.109.206.212:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from gabelmoo (http://131.188.40.189:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from moria1 (http://128.31.0.39:9131/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from dannenberg (http://193.23.244.244:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' WARNING: The following directory authorities do not support the consensus method that the consensus uses: Faravahar NOTICE: Consensus fetched from maatuska was missing the following authority signatures: Faravahar NOTICE: Consensus fetched from tor26 was missing the following authority signatures: Faravahar NOTICE: Consensus fetched from longclaw was missing the following authority signatures: Faravahar NOTICE: Consensus fetched from dizum was missing the following authority signatures: Faravahar NOTICE: Consensus fetched from gabelmoo was missing the following authority signatures: Faravahar NOTICE: Consensus fetched from moria1 was missing the following authority signatures: Faravahar NOTICE: Consensus fetched from dannenberg was missing the following authority signatures: Faravahar NOTICE: Consensus fetched from Faravahar was missing the following authority signatures: Faravahar

1 0

Consensus issues
by atagar＠torproject.org 02 Jan '17

02 Jan '17

ERROR: Unable to retrieve the vote from maatuska (http://171.25.193.9:443/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from tor26 (http://86.59.21.38:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from longclaw (http://199.254.238.52:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from dizum (http://194.109.206.212:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from gabelmoo (http://131.188.40.189:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from moria1 (http://128.31.0.39:9131/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, client-versions, server-versions, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' ERROR: Unable to retrieve the vote from dannenberg (http://193.23.244.244:80/tor/status-vote/current/authority.z) The fields in a section of the document are misordered. It should be 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, known-flags, flag-thresholds, recommended-client-protocols, recommended-relay-protocols, required-client-protocols, required-relay-protocols, params' but was 'network-status-version, vote-status, consensus-methods, published, valid-after, fresh-until, valid-until, voting-delay, recommended-relay-protocols, recommended-client-protocols, required-relay-protocols, required-client-protocols, known-flags, flag-thresholds, params' WARNING: The following directory authorities do not support the consensus method that the consensus uses: Faravahar NOTICE: Consensus fetched from maatuska was missing the following authority signatures: Faravahar NOTICE: Consensus fetched from tor26 was missing the following authority signatures: Faravahar NOTICE: Consensus fetched from longclaw was missing the following authority signatures: Faravahar NOTICE: Consensus fetched from dizum was missing the following authority signatures: Faravahar NOTICE: Consensus fetched from gabelmoo was missing the following authority signatures: Faravahar NOTICE: Consensus fetched from moria1 was missing the following authority signatures: Faravahar NOTICE: Consensus fetched from dannenberg was missing the following authority signatures: Faravahar NOTICE: Consensus fetched from Faravahar was missing the following authority signatures: Faravahar WARNING: The following authorities are missing from the consensus: maatuska

1 0