[tor] Exit 01 dropped out of consensus; appears down

[Cooper Quintin]

Thanks for taking care of this Patrick. Perhaps we should make getting
monitoring up a priority now.

On 07/29/2017 02:43 PM, Patrick O'Dohehrty wrote:
> Have fixed this, it was the age-old issue of our customized
> /etc/init.d/tor script being problematic and starting a default instance
> instead of our 4 instances upon restart. This will eventually be solved
> by us deprecating our old script and instead using whatever the
> ansible-relayor repository puts in place on the host.
> 
> p
> 
> On 07/28/2017 02:13 PM, Patrick O'Doherty wrote:
>> Hey folks,
>>
>> I noticed just now that Exit 01 has fallen out of consensus, and the tor
>> daemon doesn't appear to be running on the host. I don't have access to
>> the requisite credentials to investigate it thoroughly right now but
>> hope to do so later today, unless someone wants to beat me to it.
>>
>> I'm going to try get some basic uptime monitoring established so that
>> we're not left to discover these incidents by chance.
>>
>> cheers,
>>
>> p
>>
> 
> 
> 
> _______________________________________________
> tor mailing list
> tor at lists.noisebridge.net
> https://www.noisebridge.net/mailman/listinfo/tor
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://www.noisebridge.net/pipermail/tor/attachments/20170801/7c171101/attachment-0002.sig>