tasksel packages stays at 100%

[Robin Stein]

Binary package hint: tasksel

Fresh pxe Gutsy cli install
tasksel 2.67ubuntu7

When running tasksel from prompt some of the packages stays and is stuck at 100%.
The only way i figured out to get my prompt back is another tty and kill the process manually.

Packages that sits at 100%:
DNS server
LAMP server
PostgreSQL database
Samba File server

Packages that works:
Mail server
OpenSSH server

Those are tha packages i tried so far.

[celticmonkey (jamesboston)]

I had the same problem after running this command:

sudo tasksel install lamp-server

The progress meter just hangs at 100%. A ps -A shows that tasksel is still running. I just closed the terminal and hoped for the best. My lamp server does seem to be working okay, though.

[Ruben Laban (r-laban)]

Same issue here. Installing "any" task (tried SSH/LAMP/Samba) causes tasksel to hang at 100%. I don't recall the details but it involves a process ending up in the Zombie state. Killing procs works, but is a nasty workaround.

This is on a fresh-feisty-with-all-updates-upgraded-to-gutsy. As in: I didn't bother downloading a Gutsy install disc so I took my Feisty disc, installed it, ran apt-get dist-upgrade, ran do-release-update (or whatever that command was). I didn't ran any tasksel's until Gutsy was up and running.

[Ruben Laban (r-laban)]

Excerpt from "ps uaxfww" :

ruben 4576 0.0 0.1 20692 3640 pts/0 Ss 20:13 0:00 | \_ -bash
root 4796 0.1 0.4 36460 12568 pts/0 S+ 20:13 0:00 | \_ /usr/bin/perl /usr/bin/tasksel
root 4816 0.0 0.3 47924 10772 pts/0 S+ 20:13 0:00 | \_ /usr/bin/perl -w /usr/share/debconf/frontend /usr/bin/debconf-apt-progress -- apt-get -q --no-install-recommends -y install lamp-server^
root 4822 0.0 0.1 27120 5364 pts/0 S+ 20:13 0:00 | \_ /usr/bin/perl -w /usr/bin/debconf-apt-progress -- apt-get -q --no-install-recommends -y install lamp-server^
root 4825 0.2 0.0 0 0 pts/0 Z+ 20:13 0:01 | | \_ [apt-get] <defunct>
root 4824 0.0 0.0 19424 1824 pts/0 S+ 20:13 0:00 | \_ whiptail --backtitle Package configuration --title Installing packages --output-fd 7 --nocancel --gauge --

[Michael Vogt (mvo)]

Thanks for your bugreport.

Could you please install the apt from gutsy-proposed and check if that fixes the issue? There is a problem with apt under some circumstance when it leaves zombies like this.

[Nick Barcet (nijaba)]

I confirm that I was able to reproduce this on Gutsy server 64bit and JeOS 32bit.

Work around: use "apt-get install taskname^" where taskname is the name of the task (ie lamp-server^).

[Robin Stein (netz)]

Michael:

Made a fresh gutsy netboot cli install and added gutsy-proposed.
#tasksel install lamp-server
Stuck at 100%

Issue still exists with apt Version: 0.7.6ubuntu14.1.

[Colin Watson (cjwatson)]

Soren Hansen identified this as a debconf issue. Patch on its way.

[Colin Watson (cjwatson)]

debconf (1.5.18) unstable; urgency=low

  [ Søren Hansen ]
  * debconf-apt-progress sometimes gets captured by buggy daemons, causing
    tasksel to hang because $debconf_command_eof never becomes true.
    STATUS_READ should be the last fd to close, so checking $status_eof is
    sufficient (LP: #141601).

  [ Joey Hess ]
  * debconf(1): Document that this command is rarely used. Closes: #457598
  * Add missing newlines to some error messages. Closes: #457609

 -- Colin Watson <email address hidden> Tue, 08 Jan 2008 14:08:27 +0000

[mbana (m.bana)]

i've got the same problem, i also need a full system update about 1hr prior to installing lamp by using this command 'sudo tasksel install lamp-server'.

here is where its stopped at; http://img526.imageshack.us/img526/7597/lampcrashxr2.png. What shall i do?

please help

thanks

[Ruben Laban (r-laban)]

Mohamed,

The current workaround is to use "sudo apt-get install lamp-server^" instead of using tasksel. It also *seems* to be safe to just kill the processes that tasksel has hanging around, since when doing so everything *looks* being installed just ok. I ran a "sudo apt-get install lamp-server^" to make sure that it installed properly, though I'm not sure if that's a proper confirmation of it having been installed properly.

HTH.

Regards,
Ruben

[Neal McBurnett (nealmcb)]

A symptom that may be part of this syndrome that we saw was "Exiting subroutine via next at /usr/bin/debconf-apt-progress line 153". This was on gutsy during an install of LAMP, when it also prompted for the cdrom to be installed.

[Colin Watson (cjwatson)]

That last bit is definitely a bug; I'll get that sorted out, thanks. However, gutsy predates the fix to this bug ...

[Nick Barcet (nijaba)]

Still have this issue with yesterday's build of hardy jeos...

[xteejx (xteejx-deactivatedaccount)]

Hi guys, this was last updated almost 2 years ago. I have tried to reproduce this in Lucid without any problems. Can you confirm if this is still an issue for you? Thank you.