On Tue, Oct 25, 2011 at 09:11:17PM +0200, Santiago Garcia Mantinan wrote: > Package: unattended-upgrades > Version: 0.62.2 > Severity: critical
Thanks for your bugreport. > This is the status of this machine right now: > > root 1718 0.0 0.0 22912 1040 ? Ss Sep13 0:02 > /usr/sbin/cron > root 29687 0.0 0.0 33292 1100 ? S Oct10 0:00 \_ > /USR/SBIN/CRON > root 29688 0.0 0.0 11072 1304 ? Ss Oct10 0:00 \_ > /bin/sh -c test -x /usr/sbin/anacron || ( cd / && run-parts --report > /etc/cron.daily ) > root 29689 0.0 0.0 11076 676 ? S Oct10 0:00 \_ > /bin/sh -c test -x /usr/sbin/anacron || ( cd / && run-parts --report > /etc/cron.daily ) > root 29690 0.0 0.0 3852 588 ? S Oct10 0:00 > \_ run-parts --report /etc/cron.daily > root 29692 0.0 0.0 0 0 ? Z Oct10 0:00 > \_ [apt] <defunct> > > As you can see it is 25th Oct now and the apt that is in a zombie state is > from the 10th, I've seen this happen on i386 and amd64 arches at least in > stable, I can't confirm if this has happened on testing/sid as well, but I > think I has happened to me on those as well before. Thanks for this output, this is puzzling. So this ps output indicates that the script /etc/cron.daily/apt itself is in a zombie state. That means that run-parts has not collected the result of the apt cron shell script. Do you have anything in the logs (e.g. /var/log/unattended-upgrades.log or /var/log/apt/history.log) from around this time that might give a clue why this happend? Does this mean that since the 10th no other cron.daily runs for apt happend? > It seems weird I have not found this bug as it is hitting me from some time > now on machines at work and at home, I tried to look at /proc a bit to find > info on the process but didn't know what to look for and didn't find > anything relevant. > > I hope to hear back from you soon and leave the process in that state in > case you want to have a look at some of the data of the running process or > similar. It might be interessting to get a "strace -p 29690" to see what the parent is doing and if its waiting for a different PID maybe? > Please tell me how to proceed from here as I don't know what info to add I > can tell you that this doesn't always happen, it happens from time to time. > > I'm setting some of the machines with APT::Periodic::Verbose 3; to gather > some info on other machines that are also seing this. I think that is the best course of action for now, I would really like to know what happend before this process exited and turned into a zombie. Cheers, Michael P.S. I might be a bit slow responding in the next days as I will be traveling, but I will do my best to keep up. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
