Bug#545701: dash.postinst abort in infinite loop
Excerpts from Jonathan Nieder's message of sáb ago 20 23:47:04 -0400 2011:
tags 545701 + moreinfo
quit
Jonathan Nieder wrote:
Alvaro Herrera wrote on 2009-09-08:
I started an aptitude safe-upgrade and left the computer for half an
hour. Upon return I find that there's a suspicious process eating 100%
of a CPU for a long time.
[...]
/usr/bin/perl-w/usr/share/debconf/frontend/var/lib/dpkg/info/dash.postinstabort-upgrade0.5.5.1-2.3
[...]
ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B0 -opost -isig icanon -echo
...}) = 0
repeats ad nauseam
(isatty, I think.)
If I had to guess, this loop is somewhere in the guts of debconf
machinery. So I fear it was probably silently fixed.
Yeah, perhaps.
But still:
- do you remember anything more about what was happening when this
occured (for example, did you interrupt any previous upgrade, and
was there a terminal available)?
No previous interrupted upgrades.
- did it ever happen again?
Nope. I happened to notice now that I reported that I was using
aptitude to upgrade. I no longer do that; I always use apt-get now.
Not sure if that means anything.
- any other clues or symptoms?
I don't really remember anything else.
Sorry we didn't get to this in time.
Yeah ... I guess this can safely be closed.
--
Álvaro Herrera alvhe...@alvh.no-ip.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545701: dash.postinst abort in infinite loop
tags 545701 - moreinfo quit Alvaro Herrera wrote: Excerpts from Jonathan Nieder's message of sáb ago 20 23:47:04 -0400 2011: Sorry we didn't get to this in time. Yeah ... I guess this can safely be closed. Thanks for the clarifications. Closing since it's hard to see how to move this forward, but I will remember it next time something similar happens. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545701: dash.postinst abort in infinite loop
tags 545701 + moreinfo
quit
Jonathan Nieder wrote:
Alvaro Herrera wrote on 2009-09-08:
I started an aptitude safe-upgrade and left the computer for half an
hour. Upon return I find that there's a suspicious process eating 100%
of a CPU for a long time.
[...]
/usr/bin/perl-w/usr/share/debconf/frontend/var/lib/dpkg/info/dash.postinstabort-upgrade0.5.5.1-2.3
[...]
ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B0 -opost -isig icanon -echo ...})
= 0
repeats ad nauseam
(isatty, I think.)
If I had to guess, this loop is somewhere in the guts of debconf
machinery. So I fear it was probably silently fixed.
But still:
- do you remember anything more about what was happening when this
occured (for example, did you interrupt any previous upgrade, and
was there a terminal available)?
- did it ever happen again?
- any other clues or symptoms?
Sorry we didn't get to this in time.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545701: dash.postinst abort in infinite loop
Hi Alvaro,
Alvaro Herrera wrote:
I started an aptitude safe-upgrade and left the computer for half an
hour. Upon return I find that there's a suspicious process eating 100%
of a CPU for a long time.
Sorry for the long silence. Let's see.
/proc/pid/cmdline says:
# cat cmdline
/usr/bin/perl-w/usr/share/debconf/frontend/var/lib/dpkg/info/dash.postinstabort-upgrade0.5.5.1-2.3
- prerm upgrade and prerm failed-upgrade failed, or
- preinst upgrade failed and postrm abort-upgrade succeeded, or
- postrm upgrade and postrm failed-upgrade failed and
preinst abort-upgrade and postrm abort-upgrade succeeded.
Which is to say, something went seriously wrong.
strace'ing the process yields this:
[...]
ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B0 -opost -isig icanon -echo ...}) = 0
repeats ad nauseam
(isatty, I think.)
Killing that process and doing an aptitude install dash reports this:
[...]
dpkg: error processing /var/cache/apt/archives/dash_0.5.5.1-2.3_amd64.deb
(--unpack):
trying to overwrite `/bin/sh', which is also in package bash
At last, something simpler to understand. Does a more recent version
of the dash package work?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545701: dash.postinst abort in infinite loop
Package: dash
Version: 0.5.5.1-2
Severity: important
I started an aptitude safe-upgrade and left the computer for half an
hour. Upon return I find that there's a suspicious process eating 100%
of a CPU for a long time. /proc/pid/cmdline says:
# cat cmdline
/usr/bin/perl-w/usr/share/debconf/frontend/var/lib/dpkg/info/dash.postinstabort-upgrade0.5.5.1-2.3
strace'ing the process yields this:
ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B0 -opost -isig icanon -echo ...}) = 0
ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B0 -opost -isig icanon -echo ...}) = 0
ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B0 -opost -isig icanon -echo ...}) = 0
repeats ad nauseam
Killing that process and doing an aptitude install dash reports this:
# LC_ALL=C sudo aptitude install dash
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
The following packages will be upgraded:
dash
1 packages upgraded, 0 newly installed, 0 to remove and 473 not upgraded.
Need to get 0B/99.5kB of archives. After unpacking 0B will be used.
Do you want to continue? [Y/n/?]
Writing extended state information... Done
Reading changelogs...
Preconfiguring packages ...
(Reading database ... 213689 files and directories currently installed.)
Preparing to replace dash 0.5.5.1-2 (using .../dash_0.5.5.1-2.3_amd64.deb) ...
Adding `diversion of /usr/share/man/man1/sh.1.gz to
/usr/share/man/man1/sh.distrib.1.gz by dash'
Unpacking replacement dash ...
dpkg: error processing /var/cache/apt/archives/dash_0.5.5.1-2.3_amd64.deb
(--unpack):
trying to overwrite `/bin/sh', which is also in package bash
Removing `diversion of /usr/share/man/man1/sh.1.gz to
/usr/share/man/man1/sh.distrib.1.gz by dash'
Processing triggers for man-db ...
Processing triggers for menu ...
Errors were encountered while processing:
/var/cache/apt/archives/dash_0.5.5.1-2.3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
And this is the status of bash and dash in my system:
LC_ALL=C apt-cache policy bash dash
bash:
Installed: 4.0-4
Candidate: 4.0-4
Version table:
*** 4.0-4 0
990 http://ftp.debian.org testing/main Packages
100 /var/lib/dpkg/status
dash:
Installed: 0.5.5.1-2
Candidate: 0.5.5.1-2.3
Version table:
0.5.5.1-2.3 0
990 http://ftp.debian.org testing/main Packages
*** 0.5.5.1-2 0
100 /var/lib/dpkg/status
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_CL.UTF-8, LC_CTYPE=es_CL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages dash depends on:
ii libc6 2.9-25 GNU C Library: Shared libraries
dash recommends no packages.
dash suggests no packages.
-- debconf information:
dash/sh: false
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
