Hi Tom. Thankfully the sky isn't falling. Rather, Doctor's virt is
running into issues...
https://trac.torproject.org/projects/tor/ticket/12457
At first this manifested as OOM errors but now for some reason
descriptor requests are timing out. Honestly I'm not really sure
what's up. My guess is the OOM killer swept through and I need to
issue a reboot, but first I'm waiting for additional memory so this
doesn't reoccur.
Sorry about the confusion! -Damian
On Sun, Jul 6, 2014 at 6:37 PM, Tom Ritter t...@ritter.vg wrote:
On 6 July 2014 18:59, doctor role account
doc...@cappadocicum.torproject.org wrote:
ERROR: Unable to retrieve the consensus from maatuska
(http://171.25.193.9:443/tor/status-vote/current/consensus): timed out
ERROR: Unable to retrieve the consensus from tor26
(http://86.59.21.38:80/tor/status-vote/current/consensus): timed out
ERROR: Unable to retrieve the consensus from urras
(http://208.83.223.34:443/tor/status-vote/current/consensus): timed out
ERROR: Unable to retrieve the consensus from gabelmoo
(http://212.112.245.170:80/tor/status-vote/current/consensus): timed out
ERROR: Unable to retrieve the consensus from moria1
(http://128.31.0.39:9131/tor/status-vote/current/consensus): timed out
ERROR: Unable to retrieve the consensus from dannenberg
(http://193.23.244.244:80/tor/status-vote/current/consensus): timed out
ERROR: Unable to retrieve the consensus from Faravahar
(http://154.35.32.5:80/tor/status-vote/current/consensus): timed out
I've been keeping an eye on consensus health, it seems to be pretty
reliable, but this is an obvious outlier. I assume it was a doctor
error of some sort?
-tom
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
