cron.daily/apt script hung

[Greg]

Binary package hint: apt

Something happened to cause the apt-get process launched by the cron.day/apt script to hang. I haven't tried to kill the process yet to see if it can be repeated. If there is any information that can be gathered before killing it, please let me know.

top:
  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
 2335 root 0 10 6656 0 0 R 99.9 0.0 23844:26 apt-get

ls -lu /etc/cron.daily/:
-rwxr-xr-x 1 root root 311 2010-11-12 22:27 0anacron
-rwxr-xr-x 1 root root 189 2010-11-12 22:27 apport
-rwxr-xr-x 1 root root 15655 2010-11-12 22:27 apt
-rwxr-xr-x 1 root root 314 2010-11-04 03:54 aptitude
-rwxr-xr-x 1 root root 502 2010-11-04 03:54 bsdmainutils
-rwxr-xr-x 1 root root 71 2010-11-04 03:54 debtags
-rwxr-xr-x 1 root root 256 2010-11-04 03:54 dpkg
-rwxr-xr-x 1 root root 89 2010-11-04 03:54 logrotate
-rwxr-xr-x 1 root root 1335 2010-11-04 23:01 man-db
-rwxr-xr-x 1 root root 606 2010-11-04 03:55 mlocate
-rwxr-xr-x 1 root root 293 2010-11-04 03:55 mythvideo
-rwxr-xr-x 1 root root 1154 2010-11-04 03:55 ntp
-rwxr-xr-x 1 root root 2149 2010-11-04 03:55 popularity-contest
-rwxr-xr-x 1 root root 383 2010-11-04 03:55 samba
-rwxr-xr-x 1 root root 3594 2010-11-04 22:59 standard
-rwxr-xr-x 1 root root 1309 2010-11-04 03:55 sysklogd

Sorry if the text alignment is off. Given the time from top of 23844:26 (assuming this is minutes) gives 16.5 days which basically lines up with the last used time of the cron.daily script.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: apt 0.8.3ubuntu7
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Tue Nov 30 10:44:59 2010
ExecutablePath: /usr/bin/apt-get
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/sh
SourcePackage: apt

[David Kalnischkies (donkult)]

Do you have a cdrom/dvd listed in your sources?

If so comment it out or upgrade to APT 0.8.9:
  * cmdline/acqprogress.cc:
    - don't ask the user for media change if quiet >= 2, stdout is not
      a tty and assume-yes, force-yes or trivial-only option is set to
      avoid cpu eating endless loops in unattended runs like apt.cron
      (Closes: #602354, LP: #665580)

[Greg (iskimj)]

Yes, that's it. Thanks.

The fix you pointed out addresses the media change when running in a script which is fine. I've seen this pop up before when I manually run apt-get because the cd is in my source list. Is there a root bug whereby the cd is put in the sources in the first place (or left there)? I too upgraded using a mounted iso image, I expect that for this reason, the cd is listed as a source, but should the upgrade remove the cd from the sources afterwards? That would be my preference. I wouldn't expect anyone leaves the cd (or mounted image) in the computer after the upgrade.