[PVE-User] pve-kernel-4.4.8-1-pve upgrade hanging

[Antoine Jacques de Dixmude]

I found that in /var/log/dpkg.log :
2016-06-09 10:01:00 startup archives unpack
2016-06-09 10:01:00 upgrade pve-kernel-4.4.8-1-pve:amd64 4.4.8-52 4.4.8-52
2016-06-09 10:01:00 status half-installed pve-kernel-4.4.8-1-pve:amd64 
4.4.8-52

Obviously, the package pve-kernel was half-installed before I runned the 
dist-upgrade command. But I don't understand why dpkg is hanging.

The question is : can I cancel the unpaking of pve-kernel without 
consequences ?

On 06/09/2016 01:55 PM, Antoine Jacques de Dixmude wrote:
> Thank you for your response.
>
> I checked (with df) and there is still plenty of free space.
>
> On 06/09/2016 12:46 PM, Thiago Damas wrote:
>> Hi,
>> Check the free disk space (/ and /boot).
>>
>> Thiago
>>
>> Em quinta-feira, 9 de junho de 2016, Antoine Jacques de Dixmude <
>> antoine at earlytracks.com> escreveu:
>>
>>> Hello everyone,
>>>
>>> Previously, this morning, I runned a "apt-get dist-upgrade" and I've 
>>> got
>>> this output :
>>>
>>> Reading package lists... Done
>>> Reading package lists... Done
>>> Building dependency tree
>>> Reading state information... Done
>>> Calculating upgrade... Done
>>> The following NEW packages will be installed:
>>>    pve-docs pve-kernel-4.4.8-1-pve
>>> The following packages will be upgraded:
>>>    libexpat1 proxmox-ve pve-manager
>>> 3 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
>>> Need to get 50.0 MB of archives.
>>> After this operation, 5,804 kB of additional disk space will be used.
>>> Do you want to continue? [Y/n] Y
>>> Get:1 http://security.debian.org/ jessie/updates/main libexpat1 amd64
>>> 2.1.0-6+deb8u3 [80.0 kB]
>>> Get:2 https://enterprise.proxmox.com/debian/ jessie/pve-enterprise
>>> pve-kernel-4.4.8-1-pve amd64 4.4.8-52 [43.9 MB]
>>> Get:3 https://enterprise.proxmox.com/debian/ jessie/pve-enterprise
>>> pve-docs all 4.2-5 [926 kB]
>>> Get:4 https://enterprise.proxmox.com/debian/ jessie/pve-enterprise
>>> pve-manager amd64 4.2-11 [5,024 kB]
>>> Get:5 https://enterprise.proxmox.com/debian/ jessie/pve-enterprise
>>> proxmox-ve all 4.2-52 [4,736 B]
>>> Fetched 50.0 MB in 1s (34.6 MB/s)
>>> Reading changelogs... Done
>>> Preconfiguring packages ...
>>> (Reading database ... 50086 files and directories currently installed.)
>>> Preparing to unpack .../libexpat1_2.1.0-6+deb8u3_amd64.deb ...
>>> Unpacking libexpat1:amd64 (2.1.0-6+deb8u3) over (2.1.0-6+deb8u2) ...
>>> Selecting previously unselected package pve-kernel-4.4.8-1-pve.
>>> Preparing to unpack .../pve-kernel-4.4.8-1-pve_4.4.8-52_amd64.deb ...
>>> Unpacking pve-kernel-4.4.8-1-pve (4.4.8-52) ...
>>> E: Sub-process /usr/bin/dpkg exited unexpectedly
>>>
>>> So, I retried :
>>> # apt-get dist-upgrade
>>> E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to
>>> correct the problem.
>>>
>>> I followed the instruction got from the previous output:
>>> # dpkg --configure -a
>>> Setting up libexpat1:amd64 (2.1.0-6+deb8u3) ...
>>> Processing triggers for libc-bin (2.19-18+deb8u4) ...
>>>
>>> I've runned a third dist-upgrade and got the following output :
>>> Reading package lists... Done
>>> Building dependency tree
>>> Reading state information... Done
>>> Calculating upgrade... Done
>>> The following NEW packages will be installed:
>>>    pve-docs
>>> The following packages will be upgraded:
>>>    proxmox-ve pve-kernel-4.4.8-1-pve pve-manager
>>> 3 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
>>> 1 not fully installed or removed.
>>> Need to get 0 B/49.9 MB of archives.
>>> After this operation, 5,803 kB of additional disk space will be used.
>>> Do you want to continue? [Y/n] Y
>>> Reading changelogs... Done
>>> Preconfiguring packages ...
>>> (Reading database ... 50086 files and directories currently installed.)
>>> Preparing to unpack .../pve-kernel-4.4.8-1-pve_4.4.8-52_amd64.deb ...
>>> Unpacking pve-kernel-4.4.8-1-pve (4.4.8-52) over (4.4.8-52) ...
>>>
>>> I'm stuck with the "Unpacking pve-kernel-4.4.8-1-pve (4.4.8-52) over
>>> (4.4.8-52) ..." since 2 hours. And, as you can see, dpkg is 
>>> unpacking the
>>> package on the same version ((4.4.8-52) over (4.4.8-52)).
>>>
>>> Any idea ? (knowing that the upgrading node is also running some VMs)
>>> _______________________________________________
>>> pve-user mailing list
>>> pve-user at pve.proxmox.com
>>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>>
>> _______________________________________________
>> pve-user mailing list
>> pve-user at pve.proxmox.com
>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>