Hello Martin, It is usually appreciated not to format copied content at all (i. e. the output of dpkg etc.), since most people can do that themselves when necessary and forcibly formatting it might lead to even uglier things than lines longer than 80 characters :) Martin McCormick <martin@x.it.okstate.edu> wrote: > PID TTY STAT TIME COMMAND > aptitude -q9 safe-upgrade > 5243 pts/2 Ss+ 0:00 /usr/bin/dpkg --status-fd 18 > [...] > libcpufreq0 cpufrequtils cu The above is dpkg. > 25838 ? Ss 0:00 /usr/sbin/cron Some random cronjob. > 25900 ? S<s 0:00 udevd --daemon udev > 25919 pts/2 S+ 0:01 /usr/bin/perl -w /usr/share/debconf/frontend /var/lib/dpkg/info/linux-base.postinst configure > 25925 pts/2 S+ 0:00 /usr/bin/perl /var/lib/dpkg/info/linux-base.postinst configure > 25951 pts/2 S+ 0:00 whiptail --backtitle Package configuration --title Configuring linux-base --output-fd 11 --nocancel --msgbox These devices will be assigned UUIDs or labels:??/dev/hda5:UUID=f148e250-746d-4c8e-a840-228ae3caa1bf??These configuration files will be updated:??/etc/fstab, /boot/grub/menu.lst, ?/etc/udev/rules.d/70-persistent-cd.rules, ?/etc/initramfs-tools/conf.d/resume??The device IDs will be changed as follows:??/dev/sda1: UUID=f39d1d00-89fc-41f2-a445-51ece1c53213?/dev/hda1: UUID=defdfcfb-ade5-4045-82a5-d2708a21acd2?/dev/sdb1: UUID=edc8ce83e323-4912-8ddd-9897493cbb18?/dev/hda5: UUID=f148e250-746d-4c8e-a840-228ae3caa1bf?/dev/hdb1: UUID=75873040-6936-40ec-aad1-1e5748446c54?/dev/hdd: /devcdrom?+PATH=pci-0000:00:07.1-scsi-1:0:1:0?+ PATH=pci-0000:00:07.1-scsi-1:0:0:0 --scrolltext 21 57 This appears to be the debconf query dialog. >25953 ? Ss 0:00 sshd: martin [priv] > 25955 ? S 0:00 sshd: martin@pts/1 25956 pts/1 Ss+ > 0:00 -bash 25974 ? S< 0:00 udevd --daemon 25976 ? S< > 0:00 udevd --daemon SSH and udev again. > That's where it stands now. > May 4 06:21:29 > wb5agz kernel: [410550.564743] udev[25900]: starting version 164 > May 4 06:57:00 wb5agz kernel: [412680.899917] usb 1-3: USB disconnect, > address 2 May 4 07:35:05 wb5agz rsyslogd: [origin software="rsyslogd" > swVersion="3.18.6" x-pid="2475" x-info="http://www.rsyslog.com";] > restart > May 4 06:21:29 wb5agz kernel: [410550.564743] udev[25900]: starting version 164 > May 4 06:57:00 wb5agz kernel: [412680.899917] usb 1-3: USB disconnect, address 2 > May 4 07:35:05 wb5agz rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="2475" x-info="http://www.rsyslog.com";] restart Looks good. > > > > Human error: > > - Are you sure that safe-upgrade is stuck rather than simply waiting > > for some input? > > I am not 100% sure of anything right now except that syslog > tried to restart and shows the following error: > > May 4 07:35:05 wb5agz rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="2475" x-info="http://www.rsyslog.com";] restart > May 4 07:35:05 wb5agz rsyslogd: could not load module '/usr/lib/rsyslog/imuxsock.so', rsyslog error -3003 > May 4 07:35:05 wb5agz rsyslogd: the last error occured in /etc/rsyslog.conf, line 11 > May 4 07:35:05 wb5agz rsyslogd: could not load module '/usr/lib/rsyslog/imklog.so', dlopen: /usr/lib/rsyslog/imklog.so: undefined symbol: MsgSetRcvFromIP > May 4 07:35:05 wb5agz rsyslogd: the last error occured in /etc/rsyslog.conf, line 12 This may well be due to the pending upgrade. The problem indeed appears to be whiptail waiting for input. As whiptail is called with the "nocancel" option, it is unlikely that its return value is checked, which then means that simply killing it should continue the upgrade. Best regards, Claudius -- NOTICE: Anyone seen smoking will be assumed to be on fire and will be summarily put out. http://chubig.net telnet nightfall.org 4242
Attachment:
signature.asc
Description: PGP signature