[tor-consensus-health] Consensus issues

micah micah at riseup.net
Sat Mar 31 14:50:44 UTC 2018


atagar at torproject.org writes:

> ERROR: Unable to retrieve the consensus from longclaw (http://199.58.81.140:80/tor/status-vote/current/consensus.z): <urlopen error [Errno 111] Connection refused>
> ERROR: Unable to retrieve the vote from longclaw (http://199.58.81.140:80/tor/status-vote/current/authority.z): <urlopen error [Errno 111] Connection refused>

Mar 30 20:00:06.000 [notice] It looks like I need to generate and sign a new medium-term signing key, because the one I have is expired. To do that, I need to load the permanent master identity key. If the master identity key was not moved or encrypted with a passphrase, this will be done automatically and no further action is required. Otherwise, provide the necessary data using 'tor --keygen' to do it manually.
Mar 30 20:00:06.000 [warn] We wanted to load a secret key from /var/lib/tor/keys/ed25519_master_id_secret_key, but you're keeping it offline. (OfflineMasterKey is set.)
Mar 30 20:00:06.000 [warn] Can't load master identity key; OfflineMasterKey is set.

Regenerated new set.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 962 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-consensus-health/attachments/20180331/ba85c701/attachment.sig>


More information about the tor-consensus-health mailing list