After an epic battle getting this thing back online, it finally is.
This was one of those situations where everything that could go wrong, did.
Started with the initial physical hard drive problems, then when that was replaced the network cable somehow got unplugged.
After that got plugged back in, somewhere along the line the cable that provides video to our KVM became loose.
When the server finally was back online, there were all kinds of problems compiling our custom kernel (something to do with the kernel version the box came with, a few missing modules were to blame).
All is well now. I just did a test win connect with the widget and another test connect on my ubuntu laptop, both seem functional (and .onion/.i2p access works on them). Accessing the .bit TLD provided by DNSChain won't be available for another hour or two though. Starting that server requires running the namecoind server, which has to calculate a block count before it'll work (it's gotta reach the block count listed in
http://explorer.dot-bit.org/stats/block_count.txt ). As of this post, the status on that can be seen with this tiny one-liner I hacked up:
[namecoin@turing ~]$ t=`wget -qO-
http://explorer.dot-bit.org/stats/block ... `namecoind getinfo|grep blocks|awk '{print $NF}'|awk -F, '{print $1}'`;echo "$y blocks so far, $(expr $t - $y) to go til you reach $t"
99637 blocks so far, 124287 to go til you reach 223924
Also, we went ahead and converted all the daemons/servers running on Turing from the old/default services management through init scripts to the much better daemontools programs (
http://cr.yp.to/daemontools.html ). Eventually we'll convert all the other nodes from init to daemontools.