I erased the former writeup because UNIXY.net is taking steps to resolve the issues I had and refunding my money.
I think the lesson, in the end, is that if you want unmanaged hosting, don’t go with a managed hosting provider. You and the hosts will step on each other’s toes and it will not end well.
Just built this for my servers/KVM guests, from git on 2012-05-31. Download here. Install like:
dpkg -i ./mosh_1.2.1-1_amd64.deb
... complaints about missing packages etc...
apt-get -f install -y
As I mentioned the other day, before shutting down and deleting my Linode, I made a complete copy of the system image using dd per the instructions on the Linode site, using Finnux. I was a bit confused trying to access the contents of that image (EDIT: In a Linux KVM guest), but it turned out to be fantastically simple.
Someone pointed out here that the image produced using the dd command piped through SSH is simply a filesystem, the contents of a partition, and as such no partitions or partition table are visible. To load the image in my new web server and mount it I did the following.
On the guest:
sudo modprobe acpiphp
On the host:
virsh attach-disk <guest name> </path/to/lvm logvol holding the image> vdc --driver phy
On the guest again:
sudo mkdir /mnt/tmp
sudo mount /dev/vdc /mnt/tmp
Done. Hope this helps someone else as well.
First night on the new web server and one of my php scripts filled the logs with error messages. Back up now.
Today, I have shut down my primary web server running on Linode. Linode provides virtual servers, and have been doing so for a long time. Before Xen and KVM and VMWare (etc) were available and popular, Linode pioneered virtual servers using something really cool called User Mode Linux, wherein Linux runs as a program inside Linux on the host system.
I used Linode for a while when they were running User Mode Linux, transitioned to shared web hosting for a while when my needs were not so sophisticated, and then came back to Linode for about three years, running at times 4-5 virtual servers.
Recently, I found good, local colocation, ran the numbers on running my own server, and am now running this site and many others from the one server. It’s a little scary running all this stuff myself and depending on it. I have some backups in place but once I settle in I will probably buy another server and set up some kind of failover. Ultimately, at this point in my life I’m doing HPC consulting and I know the hardware and software stacks used in enterprise computing, so I’m much better off than when I was running an FTP and webserver from under my bed in my dorm room on a Pentuim 100 MHz.
Nonetheless, I’m sure there will still be some glitches now and then as I work out the new setup. Here’s hoping they’re nothing major. Just in case, I’m dumping an image over SSH at this very moment from my old Linode to the storage on the new server. If I’m ever really stuck I can always push it back up there to a new account. I also have my account until the end of the month, so that’s a bit of a safety net.
I’ve always been very happy with Linode. It’s a polished operation and they really know their stuff. They don’t oversell their capacity or other shady things like that. The only complaint I have is their recent security issue with the Linode Manager, and I think they handled that pretty well. I’d readily recommend them to others or go back to them in the future if necessary.
So long, Linode!