Brian Fairchild

Today been kinda long day, it started out working on this site and getting the final upgrades to the site done. Then I decided to apply all the latest and greatest patches and upgrades to the server. The server was running Ubuntu 8.04 server edition, this is about a year and half old software. I just didn't find the time to keep applying patches and updates. I wrote a few programs a few years back that do this automatically, but I had them disabled for some reason I do not remember. So anyhow I enable them and started the patches and upgrades. Everything went in just fine, ubuntu patches went right in. I should have stopped the software there, and went and did something else. But I left it run, and the next thing it wanted to do is apply a dist-upgrade from 8.04 to 10.04. So I hit the enter button to continue, a little note popped up telling me to not use SSH for upgrade. I hit enter anyways and let it run, everything went in like it was suppose to. After about 30 minutes of files and installs it asked me for a reboot. I hit enter and let it do its thing. After about 20 minutes, I checked to see if the server was back up. To my dismay it was still down and stuck on a broken grub. Come to find out the server was trying to boot to one of the backup drives. I had to pull the sata plugs from both backup drives. Finally, the server was ready to boot. Once I got it booted up, I tried to patch the ISPconfig to the latest and greatest. This failed 3 times right off the start, it was complaining about all sorts of things. The Ubuntu upgrade removed and changed a ton of things, I spent over 4 hours getting ISPconfig to finally install. I put the automatic backup on hold for a few days, just to make sure there is no more problems.  The biggest problem I had on the upgrade besides the 3 failures on ISPconfig, was the dns issues causing my sites to not work. Took about 1 hour to solve the reverse dns issue, since the server is running on 192.168.x.x ip number. The servers dns was trying to post all the websites to the actual internet ip numbers for my DSL connection. The trick was creating a sub-domain using the server name.