[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#514443: upgrade-reports: etch->lenny upgrade: problems with dhcp, user-mode-linux, apcupsd, atftpd, x11-apps, cpufreq-info, nfs-common



clone 514443 -1 -2
reassign -1 x11-apps
found -1 7.3+4
retitle -1 xconsole uses a very weird, ugly, large font after upgrade to lenny
reassign -2 user-mode-linux 
found -2 2.6.26-1um-2
retitle -2 uml hostfs mounts and console stop working after upgrade to lenny
thanks

On Sat, Feb 07, 2009 at 05:22:13PM +0100, reportbug wrote:
> Package: upgrade-reports
> Severity: normal
> 
> >My previous release is: 
> Etch (including all updates as of today) + volatile + debian-multimedia.org
> 
> >I am upgrading to: 
> Lenny (as of today) + volatile + debian-multimedia.org
> 

Thanks for your report.

> >- Were there any problems with the system after upgrading?
> 
> Yes, several:

Processing some of them below.
As you seem to be experienced enough to find out which packages are
involved, be aware that you can assign bugs directly to packages on
upgrade issues.

> * DHCP server (dhcp3-server):
>   The system being upgraded acted as a DHCP server for the windows laptop 
>   client used to connect via ssh for the upgrade. The DHCP server was shut 
>   down for an extended period of time during the upgrade (as aptitude 
>   worked its way through the packages).
[..]
>   Following this, the putty session was immediately disconnected and any 
>   attempt to reconnect resulted in "no route to host". This happened in
>   the middle of aptitude running "Setting up package...."
> 
>   To continue, I had to hook up a monitor and keyboard to the server,
>   and log in as root on the console. "ps ax" showed "aptitude" stuck in
>   "dpkg --configure -a" (iirc), so I killed the aptitude and dpkg process,
>   and had to restart aptitude / dpkg configure. Fortunately this seemed
>   to work out well; I completed the upgrade via the console.
> 
>   Suggestion: Try to minimize the downtime for dhcpd during a dist upgrade.
>   (restart it sooner instead of waiting until all other unrelated packages 
>   have been upgraded, if possible?)

Warning about network/SSH and suggestion of screen at:
http://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.fr.html#upgrade-preparations

> * UML guests (user-mode-linux):
>   The system hosts a user-mode-linux guest (running debian etch).
>   (Before starting the upgrade on the host system, the guest was shut down
>    gracefully manually).
>   After upgrading to lenny's user-mode-linux package, the guest failed to
>   boot properly. This seems to be caused by a change in how "hostfs" mounts
>   are handled: Inside the guest, /lib/modules is configured to be mounted
>   via hosts from the host's /usr/lib/uml/modules. The old fstab entry 
>   on the guest, which was
>       hostfs /lib/modules  hostfs  defaults,ro,/usr/lib/uml/modules 0 0
>   failed to run, yielding an error "mount: special device hostfs does not 
>   exist".  Correcting the fstab entry in the guest to:
>      none /lib/modules  hostfs defaults 0 0
>   fixed the issue. (On the host, the uml process is started with:
>      screen -d -m linux.uml ubd0=/path/to/guest/root.img ubd1=/path/to/guest/swap.img mem=256M umid=guestname eth0=tuntap,tap0,,redacted hostfs=/usr/lib/uml/modules con=pty con0=fd:0,fd:1
>   )
> 
>   Also, for some reason, I can no longer connect to the console of the uml 
>   guest.  Previously, I could use both "screen /dev/ttyp0" or "screen -r" 
>   to connect. Now, using "screen /dev/ttyp0" gives a blank terminal, and 
>   "screen -r" (as the user running linux.uml process) gives: "Cannot open 
>   your terminal '/dev/pts/6' - please check."
>   Apparently there's been a change in how pseudo-terminals work? /dev/pts/6 
>   appears to be owned by the uid owning the 'xterm'? 

Cloned to user-mode-linux version 2.6.26-1um-2.

> * cpufrequtils: 
>   "/usr/bin/cpufreq-info" no longer prints a linebreak at the end of the 
>   last line of each CPU's statistics, causing the text "analyzing CPU 1" 
>   to appear at the same line as the last statusline for CPU 0. This broke 
>   a simple script that used to parse the output via "cpufreq-info | grep 'CPU '"

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513715
Found in version cpufrequtils/004-2
Fixed in version 006-1 (testing, unstable)

> * x11-apps:
>   xconsole uses a very weird, ugly, large font after upgrading (running 
>   inside 'vncserver' / 'Xrealvnc'). I had to add this to ~/.Xdefaults to 
>   get back the usual font:
>   XConsole*text*font: -*-fixed-bold-*-*-*-*-*-*-*-*-*-*-*
>   and add this to the middle of ~/.Xsession: 
>   xrdb -merge "$HOME/.Xdefaults". 

Cloned to x11-apps package, version 7.3+4.

> * atftpd:
>   During upgrade, this package threw a weird warning about an unrecognized
>   entry in /etc/inetd.conf:
>   "tftp            dgram   udp    wait    nobody /usr/sbin/tcpd /usr/sbin/in.tftpd --tftpd-timeout 300 --retry-timeout 5     --mcast-port 1758 --mcast-addr 239.239.239.0-255 --mcast-ttl 1 --maxthread 100 --verbose=5  /tftpboot"
>   while trying to add:
>   "tftp            dgram   udp4    wait    nobody /usr/sbin/tcpd /usr/sbin/in.tftpd --tftpd-timeout 300 --retry-timeout 5     --mcast-port 1758 --mcast-addr 239.239.239.0-255 --mcast-ttl 1 --maxthread 100 --verbose=5  /tftpboot"
>   Had to manually edit this file and replace 'udp' with 'udp4'

Fixed in Lenny http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484932
So I will not affect further upgrades.

> * nfs-common:
[..]
>   Preparing to replace mount 2.12r-19etch1 (using .../mount_2.13.1.1-1_i386.deb) ...
>   You have NFS mount points currently mounted, and this version of mount
>   requires that nfs-common be upgraded before NFS mounts will work.
[..]
>   To work around this, I had to manually "apt-get install nfs-common" before
>   proceeding with "aptitude safe-upgrade"

Covered by
http://www.debian.org/releases/stable/i386/release-notes/ch-information.fr.html#nfs-common

> * samba:
>   Windows XP client mappings stopped working. Previously, smb.conf used
>   "security = share" and the client drive mapping was configured with
>   the server's IP address (as in "\\1.2.3.4\sharename"). After a lot of
>   trial and failure, it would appear that the new samba package no longer
>   responded correctly to mounts based on the IP address, (yielding
>   'resource not found' type errors), so the mapping had to be 
>   changed to "\\servername\sharename" on the client). (I also took the
>   opportunity to change over to "security = user", but I don't 
>   think that's related)

If you still experience this, please report a bug against samba.
 
> > Further Comments/Problems:  
> 
> Trying to run "aptitude upgrade" as specified in the release notes at 
> http://www.debian.org/releases/lenny/i386/release-notes/ch-upgrading.en.html#minimal-upgrade
> resulted in a warning: 
> W: The "upgrade" command is deprecated; use "safe-upgrade" instead.
> 
> I used "safe-upgrade" throughout the process, perhaps the release notes 
> should be updated to prevent confusion.

Fixed in #547220 / SVN r6961.

> Also, clamav was stuck for a while during upgrading as it tried to run 
> freshclam to download new signatures, this failed naturally as the
> bind9 daemon was shutdown by aptitude. It'd be useful for both 
> named and dhcpd to become available earlier during the aptitude upgade run.

Indeed.

-- 
Simon Paillard



Reply to: