Bug#416303: upgrade-reports: upgrade report: success on a simple mail/web server
Package: upgrade-reports
Severity: normal
Hi,
as requested by Frans Pop on dda, here is a Sarge->Etch upgrade
report. Everything worked ok, details are below.
I hope this helps,
Jochen
The machine
-----------
a Qemu based virtual server, i386, 160MB of RAM
running up to date sarge
kernel-image-2.6.8-3-686 booted using grub
main applications: apache2, exim4, dovecot
no X11
The server was set-up to be as close as possible in
configuration to my real web/mail server.
Upgrade procedure
-----------------
I closely followed Method "C" as described on the Wiki
Minor glitches
--------------
The update went generally well. There were a few minor
issues, which I describe below.
1) The comment for "aptitude upgrade" mentions that this should lead
to glibc being upgraded early. This did not happen for me. It was
listed in the "The following packages have been kept back" section
and only was only upgraded when I did "aptitude install
initrd-tools" in the next step.
2) when I reached the "aptitude purge kernel-image-2.6-<flavour>"
step, I got a scary error message
----------------------------------------------------------------------
You are running a kernel (version 2.6.8-3-686) and attempting to remove
the same version. This is a potentially disastrous action. Not only
will /boot/vmlinuz-2.6.8-3-686 be removed, making it impossible to boot
it, (you will have to take action to change your boot loader to boot
a new kernel), it will also remove all modules under the directory
/lib/modules/2.6.8-3-686. Just having a copy of the kernel image is not
enough, you will have to replace the modules too.
I repeat, this is very dangerous. If at all in doubt, answer
no. If you know exactly what you are doing, and are prepared to
hose your system, then answer Yes.
Remove the running kernel image (not recommended) [No]?
----------------------------------------------------------------------
Probably the release notes should contain some encouragement for
users who reach this point. I decided to reboot before removing
the kernel.
3) The "various cleanup" section on the wiki page lists the point
"remove gcc-3.3, g++-3.3 ...". This happened automatically for me
during "aptitude dist-upgrade" ("The following packages are unused
and will be REMOVED").
4) During install the symbolic link
"/etc/apache2/sites-enabled/000-default" appeared. This broke my
common web server setup, because it slipped in between my own
"0-redir" and the virtual host definitions. Simply removing the
link fixed the web server.
5) The new dovecot config file looks very different from the old one
(the new one has blocks in curly brackets where the old one didn't
and some config options were renamed). This made me daubt that the
old file would work with the new version of the server and thus I
allowed the upgrade process to replace the config file.
Consequently I had to go throught the >1000 lines of the
dovecot.conf file to fix the SSL-certificates, authentication
mechanisms etc. Not very automatic and a bit of a hassle. Maybe
admins should be aware that dovecot will need a bit of attention
during upgrade.
6) Exim also neede a bit of fiddling, but since I had manually
custimised the setup before this seems ok to me.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=de_DE.utf-8, LC_CTYPE=de_DE.utf-8 (charmap=UTF-8)
Reply to: