I tried to upgrade virtualmin from 3.87 using apt. Its still running ok as far as I can tell but the upgrade will not complete.
I have cancelled a few times and after running 'sudo dpkg --configure -a' then cancelling again (as it just hung again) I can run apt a get as far as below then it doesnt do anything else.
root@server:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 6 not fully installed or removed. After this operation, 0B of additional disk space will be used. Do you want to continue [Y/n]? Y Setting up webmin-virtual-server (3.88.gpl) ...
I can see in the system information that it seems to have been at least partially upgraded as I see 'Virtualmin version 3.88.gpl GPL'.
When I look in the running processes I see:
12386 root 17:11 apt-get upgrade
12392 root 17:11 /usr/bin/dpkg --status-fd 26 --configure webmin-virtual-server webmin-virtualmin ...
12393 root 17:11 /bin/sh /var/lib/dpkg/info/webmin-virtual-server.postinst configure 3.87.gpl
12408 root 17:11 /usr/bin/perl /usr/share/webmin/run-postinstalls.pl virtual-server
12568 root 17:12 sh -c service lookup\-domain stop 2>&1 </dev/null
12569 root 17:12 stop lookup-domain
It always seems to have hung at stop or start lookup-domain whatever that is doing.
Install was standard a month or so ago with only base Ubuntu 10.04 then running th setup script. Extra packages I have addded are apt-get install php5-curl php5-gd php5-imagick php-apc imagemagick unattended-upgrades apticron libapache-mod-security.
Seems from the forums I am not the only one with this issue.
Thanks.
Comments
Submitted by andreychek on Mon, 10/03/2011 - 14:18 Comment #1
After speaking with Jamie, it sounds like there's a problem that comes up on occasion with Ubuntu systems, where the attempt to stop the lookup-domain service hangs.
There isn't a fix for this at the moment, as the root cause appears to be within the Ubuntu upstart system... however, a workaround is to kill the process with the name "service lookup-domain stop".
In your example above, it's the process with the ID "12568".
If you kill that, the upgrade process will continue.
Let us know if that does the trick for you!
Submitted by premierhw on Tue, 10/04/2011 - 02:39 Comment #2
Many thanks for getting back to me. Yes, killing the process fixed it, although I also had to kill another start domain lookup after it also.
Thanks again.
Submitted by andreychek on Tue, 10/04/2011 - 07:31 Comment #3
Super, thanks for letting us know how you fixed that.
We're looking into ways to work around the upstart problem so that others don't have this same problem in the future.
Submitted by Issues on Tue, 10/18/2011 - 07:45 Comment #4
Automatically closed -- issue fixed for 2 weeks with no activity.