[tor] noisetor status

[Andy Isaacson]

On Sat, Sep 22, 2012 at 05:47:56PM -0700, Andy Isaacson wrote:
> One of the tor daemons on noisetor started misbehaving in a very odd
> manner.  While debugging it, we noticed that the installed Tor was
> fairly out of date.  I upgraded to the current version and it turns out
> that something different in the startup process is preventing it from
> working with our custom multi-daemon-starting script.  And now I have to
> go offline for a few minutes.
> 
> I'll get back online in the next hour or so and hopefully finish fixing
> stuff.

I've fixed the configs to deal with the new tor setuid code, and
manually started the daemons.  We still need to fix the init script to
start them correctly on reboot, it's still doing things the old way
which doesn't work anymore.

I've dist-upgrade'd the box, so it needs a reboot.

One of the Tor daemons' IP addresses, 173.254.216.67, appears to be
blackholed by the DNS servers at the ISP.  We should probably open a
ticket to get that fixed.  This is what originally got me working on
this, I noticed that 1/4 daemons was no longer passing much traffic even
though it seemed to be running OK.

-andy