Silver's Simple Site - Weblog - Tags - CompSoc

BFL - June 19th to 23rd

So it's that time of year again, when I disappear for an entire week to spend it in a room full of 55 other computer 'freaks' and generally have a good time (that's play games and socialise, before anyone gets any weird ideas!).


The past few days I've been building up my own PPM (ActiveState Perl Package Manager) repository, which basically involves downloading CPAN packages, building them, testing, then packaging up the built code. It's really not fun, as plenty of CPAN packages fail to build, or fail tests, and generally cause problems. Still, it's getting there. The aim, what there is of one, is to have all the packages needed for Task::Catalyst and the new CompSoc website project. I think the website will be finished before my repo. is. :(

Permalink | Author: | Tags: Fun, CompSoc | Posted: 04:09PM on Friday, 16 June, 2006 | Modified: 04:26PM on Friday, 16 June, 2006 | Comments: 0

Summer Break

It's that time of year again. I will be away from Monday (25th) to Friday (29th), enjoying the annual mega LAN.

Permalink | Author: | Tags: CompSoc, Fun | Posted: 06:27AM on Sunday, 24 June, 2007 | Comments: 0

How Not to Migrate a Server

  1. E-mail people at 6PM saying the server will be offline as of 10AM the next day.
  2. The next day, find out that the new server doesn't want to work with the disks from the old server.
  3. Overwrite the partition table on one of the disks.
  4. Spend hours backing up the data and rewriting the partition table by hand.
  5. The next day, copy data and install new server into limited-access server room.
  6. While remotely migrating setup, remove /etc/passwd file (thus preventing all remote access).
  7. Wait 3 days to gain physical access to the machine.
  8. Slowly start setting up everything.
  9. Have users find out that some of the services are now running different software and didn't have their data migrated over.

Things which could have been better:

  • Advanced notice of migration. Server migration is never simple, advertising it the night before is seriously inadequate for most people.
  • Notice of which services, if any, will not be migrated exactly as-is, and how the decision was made.
  • Setting up existing services on the new server prior to the swap.

Even now, the server still isn't running all services correctly, but hopefully it will be soon. I look forward to receiving mail via the new server, 4 days after it was supposed to be all working. ;-)

Permalink | Author: | Tags: CompSoc | Posted: 04:51PM on Monday, 09 July, 2007 | Comments: 0

Powered by the Content Parser System, copyright 2002 - 2022 James G. Ross.