The Goldfish Chronicles

Upgraded my second, and more important, server from Debian woody to Debian sarge tonight. The previous one had gone pretty well, with the only casualty being a forum whose backend used bdb and the debian upgrade changed the installed version of bdb [at which point it all becomes very painful, so I had high hopes.

It chugged along and at the end of the day I had a broken database, broken spamassassin and looks like Java GUI stuff isn’t happy (such as the dynamically generated image at the top of this blog).

The database (postgres) had failed halfway through the automated update, but I think it was simply because the update process had made me turn it off at one point without telling me to turn it on again. A bit of reading and I was able to finish the job.

Spamassassin is less obvious. Some problem with perl that the only person on google to suffer from speaks either Spanish or Catalan (Altavista couldn’t handle it): Starting SpamAssassin Mail Filter Daemon: /usr/bin/perl: relocation error: /usr/lib/perl/5.8/auto/DB_File/DB_File.so: undefined symbol: db_version_4002.

Java’s also not too healthy, Exception in thread "main" java.lang.UnsatisfiedLinkError:
/opt/j2sdk1.4.2_05/jre/lib/i386/libawt.so: libXp.so.6: cannot open shared object file: No such file or directory. Which is probably ugly and painful.

I moved to Debian because SuSE installs involved me having to have physical access to the machine, whilst Debian promised a nice trustworthy remote upgrade. It’s not gone badly, but it’s dangerously close to being a problem.

This entry was posted on Monday, November 21st, 2005 at 7:38 pm and is filed under Tech. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.