upgrade to lucid froze at 'gssd stop/pre-start'

Bug #550064 reported by Mike
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

running 'update-manager -d' on my up-to-date karmic box. I was stumped for a while at the prompt to install grub on my drive or partition (hda or hda1). Chose hda. The install continued for a while, and now the progress bar states about 45 minutes remaining. It's said that for the past 2 hrs. Assuming something broke. Here are the last few lines of output from the dist. upgrade dialog box:
====
Setting up portmap (6.0.0-1ubuntu1) ...
portmap start/running, process 334
There are RPC services which were registered with the portmapper
before the configuration was changed.
You need to manually restart them in order for the changes to take effect.
Current registered services:
------------------------------------------------
    100024 1 udp 60169 status
...
    100005 3 udp 48591 mountd
    100005 3 tcp 38705 mountd
------------------------------------------------

Setting up nfs-common (1:1.2.0-4ubuntu4) ...
Installing new version of config file /etc/init/statd.conf ...
Installing new version of config file /etc/init/gssd.conf ...
Installing new version of config file /etc/init/idmapd.conf ...
statd start/running, process 543
gssd stop/pre-start, process 566
====

I checked for a process 566 and it doesn't exist at the moment. This seemed to have happened around 2010-03-27 23:45. I'll attach logs.

Revision history for this message
Mike (bild85) wrote :
summary: - upgrade to lucid froze at gssd stop/pre-start
+ upgrade to lucid froze at 'gssd stop/pre-start'
Revision history for this message
Mike (bild85) wrote :
Revision history for this message
Mike (bild85) wrote :
Revision history for this message
Mike (bild85) wrote :

looks like this may be caused by the tftp-hpa package. See Bug #147520. I'm leaving this assigned to update-manager until a more knowledgeable person confirms this.

Revision history for this message
jetpeach (jetster) wrote :

this failure also occurred for me, and i'm guessing it's caused by but 147520, but i'm not sure. for anyone trying to work around, after when i killed the upgrade, i then had to kill the stuck process that had the package lock taken (used "ps -aux" to find something that i thought had the lock, which i guessed right, it was listed as process "/usr/bin/dpkg --force-overwrite --status-fd 24 --conf "). i was then able to restart the distribution upgrade without the package lock error. but it immediately stuck again after saying in the terminal.
This time, in the terminal I hit "control-C" to kill it, but only the window closed and packages continued to be set up. it seems to have successfully finished setting up the distribution upgrade now, hope this can help anyone else who might see the problem (all 3 of my other ubuntu computers upgraded fine, so program or something specific to this computer must have caused it.)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.