How To Upgrade An Ubuntu 7.04 Server ("The Perfect Setup" + ISPConfig) To Ubuntu 7.10

Version 1.0
Author: Falko Timme

This article explains how you can upgrade an Ubuntu 7.04 (Feisty Fawn) server to Ubuntu 7.10 (Gutsy Gibbon). I'm using an Ubuntu 7.04 server, set up according to The Perfect Setup - Ubuntu Feisty Fawn (Ubuntu 7.04) and with ISPConfig installed, with web sites, email and ftp accounts, databases, DNS records, etc., and upgrade it to Ubuntu 7.10.

I do not issue any guarantee that this will work for you!

 

1 Preliminary Note

As mentioned in the introduction, my Ubuntu 7.04 server is configured according to The Perfect Setup - Ubuntu Feisty Fawn (Ubuntu 7.04) and has ISPConfig installed. I have used ISPConfig to set up web sites, email and ftp accounts, databases, DNS records, etc. I have upgraded it to Ubuntu 7.10 and tested the existing web sites, email and ftp accounts, databases, DNS records, etc. as well as ISPConfig afterwards, and I have then set up new web sites, users, databases, DNS records etc. to test the functionality of the server after the distribution upgrade, and found no errors. Everything is working as expected.

 

2 Distribution Upgrade To Ubuntu 7.10 Server

First we run

apt-get update

to update the system's package database.

Then we install the package update-manager-core:

apt-get install update-manager-core

To start the distribution upgrade, we type in:

do-release-upgrade

During the upgrade process, the system will ask a few questions which we answer as follows:

root@server1:~# do-release-upgrade
Checking for a new ubuntu release
Done Upgrade tool signature
Done Upgrade tool
Done downloading
extracting '/tmp/tmpj_2RBY/gutsy.tar.gz'
authenticate '/tmp/tmpj_2RBY/gutsy.tar.gz' against '/tmp/tmpj_2RBY/gutsy.tar.gz.gpg'
Reading cache
Checking package manager
Continue running under SSH?
This session appears to be running under ssh. It is not recommended to perform a upgrade over ssh currently because in case of failure it is harder to recover.

If you continue, a additional ssh daemon will be started at port '9004'.
Do you want to continue?
Continue [yN] <-- y

(Indeed I used SSH to update the system; although the upgrade process tells us that it is not recommended to run the upgrade over SSH, I didn't have any problems; the connection was stable, and I didn't have to go to the console, nor did I have to connect my SSH client to port 9004. If you are having connection problems, please direct your SSH client to port 9004, or use the console, if you have physical access to the system.)

Starting additional sshd
To make recovery in case of failure easier a additional sshd will be started on port '9004'. If anything goes wrong with the running ssh you can still connect to the additional one.
Reading package lists: Done
Reading state information: Done
Reading state information: Done
Reading state information: Done
Done http://us.archive.ubuntu.com feisty-backports Release.gpg
Done http://de.archive.ubuntu.com feisty Release.gpg
Done http://de.archive.ubuntu.com feisty-updates Release.gpg
Done http://security.ubuntu.com feisty-security Release.gpg
Hit http://de.archive.ubuntu.com feisty Release
Done http://de.archive.ubuntu.com feisty Release
Hit http://security.ubuntu.com feisty-security Release
Done http://security.ubuntu.com feisty-security Release
Hit http://de.archive.ubuntu.com feisty-updates Release
Done http://de.archive.ubuntu.com feisty-updates Release
Hit http://de.archive.ubuntu.com feisty/main Packages
Hit http://de.archive.ubuntu.com feisty/restricted Packages
Hit http://de.archive.ubuntu.com feisty/main Sources
Hit http://security.ubuntu.com feisty-security/main Packages
Hit http://de.archive.ubuntu.com feisty/restricted Sources
Hit http://de.archive.ubuntu.com feisty/universe Packages
Hit http://de.archive.ubuntu.com feisty/universe Sources
Hit http://de.archive.ubuntu.com feisty/multiverse Packages
Hit http://de.archive.ubuntu.com feisty/multiverse Sources
Hit http://de.archive.ubuntu.com feisty-updates/main Packages
Hit http://de.archive.ubuntu.com feisty-updates/restricted Packages
Hit http://de.archive.ubuntu.com feisty-updates/main Sources
Hit http://de.archive.ubuntu.com feisty-updates/restricted Sources
Hit http://security.ubuntu.com feisty-security/restricted Packages
Hit http://security.ubuntu.com feisty-security/main Sources
Hit http://security.ubuntu.com feisty-security/restricted Sources
Done http://us.archive.ubuntu.com feisty-backports Release
Done http://us.archive.ubuntu.com feisty-backports Release
Hit http://security.ubuntu.com feisty-security/universe Packages
Hit http://security.ubuntu.com feisty-security/universe Sources
Hit http://security.ubuntu.com feisty-security/multiverse Packages
Hit http://security.ubuntu.com feisty-security/multiverse Sources
Done http://us.archive.ubuntu.com feisty-backports/main/debian-installer Packages
Done http://us.archive.ubuntu.com feisty-backports/main/debian-installer Packages
Done downloading
Reading package lists: Donem feisty-backports/main/debian-installer Packages: 98
Reading state information: Done
Reading state information: Done
Reading state information: Done
Done http://us.archive.ubuntu.com feisty-backports/main/debian-installer release-upgrader-dpkg 1.14.5ubuntu11.2
Done http://us.archive.ubuntu.com feisty-backports/main/debian-installer release-upgrader-apt 0.6.46.4ubuntu10.3
Done downloading
Reading cache
Checking package manager
Continue running under SSH?
This session appears to be running under ssh. It is not recommended to perform a upgrade over ssh currently because in case of failure it is harder to recover.

If you continue, a additional ssh daemon will be started at port '9004'.
Do you want to continue?
Continue [yN] <-- y

[...]
Done http://de.archive.ubuntu.com gutsy/universe Sources
Done http://de.archive.ubuntu.com gutsy/multiverse Packages
Done http://de.archive.ubuntu.com gutsy/multiverse Sources
Done http://de.archive.ubuntu.com gutsy-updates/main Packages
Done http://de.archive.ubuntu.com gutsy-updates/restricted Packages
Done http://de.archive.ubuntu.com gutsy-updates/main Sources
Done http://de.archive.ubuntu.com gutsy-updates/restricted Sources
Done downloading
Checking package manager
Reading package lists: Donegutsy-security/multiverse Packages: 98
Reading state information: Done
Reading state information: Done
Reading state information: Done
Asking for confirmation
Support for some applications ended
Canonical Ltd. no longer provides support for the following software packages. You can still get support from the community.
If you have not enabled community maintained software (universe), these packages will be suggested for removal at the end of the upgrade.
libdb3
libdb3-util
liblzo1
Do you want to start the upgrade?
2 packages are going to be removed. 35 new packages are going to be installed. 339 packages are going to be upgraded.
You have to download a total of 181M. This download will take about 23 minutes with a 1Mbit DSL connection and about 7 hours 1 minutes with a 56k modem.

Fetching and installing the upgrade can take several hours and cannot be canceled at any time later.
Continue [yN] <-- y

[...]

Services to restart for PAM library upgrade: <-- saslauthd proftpd cron courier-authdaemon atd

[...]

Configuration file `/etc/mysql/my.cnf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : background this process to examine the situation
The default action is to keep your current version.
*** my.cnf (Y/I/N/O/D/Z) [default=N] ? <-- ENTER or N

[...]
A new version of configuration file /etc/php5/cli/php.ini is available, but your version has been locally modified.

What would you like to do about php.ini? <-- keep your currently-installed version

[...]

Configuration file `/etc/apache2/apache2.conf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : background this process to examine the situation
The default action is to keep your current version.
*** apache2.conf (Y/I/N/O/D/Z) [default=N] ? <-- ENTER or N

[...]

Configuration file `/etc/apache2/ports.conf'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : background this process to examine the situation
The default action is to keep your current version.
*** ports.conf (Y/I/N/O/D/Z) [default=N] ? <-- ENTER or N

[...]
A new version of configuration file /etc/php5/apache2/php.ini is available, but your version has been locally modified.

What would you like to do about php.ini? <-- keep your currently-installed version

[...]
Searching for obsolete software
Reading package lists: Done
Reading state information: Done
Reading state information: Done
Reading state information: Done
Remove obsolete packages?

10 packages are going to be removed.
Continue [yN] Details [d] <-- y

Done downloading
(Reading database ... 28724 files and directories currently installed.)
Removing libbind9-0 ...
Removing libdevmapper1.02 ...
Removing libisccfg1 ...
Removing libdns22 ...
Removing libisccc0 ...
Removing libisc11 ...
Removing libiw28 ...
Removing libjasper-1.701-1 ...
Removing liblwres9 ...
Removing libsnmp9 ...
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
System upgrade is complete.

At the end of the upgrade, a system restart is required:

Restart required
To fully ugprade, please restart
Continue [yN] <-- y

Broadcast message from [email protected]
(/dev/pts/0) at 15:01 ...
The system is going down for reboot NOW!

After the reboot, you can use your new Ubuntu 7.10 (Gutsy Gibbon) Server.

A

uname -a

shows that you have a new kernel...

root@server1:~# uname -a
Linux server1.example.com 2.6.22-14-server #1 SMP Sun Oct 14 23:34:23 GMT 2007 i686 GNU/Linux
root@server1:~#

... and:

cat /etc/debian_version

shows:

root@server1:~# cat /etc/debian_version
lenny/sid
root@server1:~#

which is correct for Ubuntu 7.10 (Gutsy Gibbon).

In the last step make sure that /bin/sh is a symlink to /bin/bash, not /bin/dash by running:

ln -sf /bin/bash /bin/sh

 

3 Links

Share this page:

0 Comment(s)