pve-manager not updated correctly 1.7

Is there a way to test to see if something is not working correctly? everything seems to be working fine since the update.

I am a bit out of ideas. Try to download the pve-manager package manually, and reinstall it with "dpkg -i ..." - does that help?
 
I had grabbed it from the cache and it done it manually that way. I just removed the cached pve-manager file and remove and installed pve-manager using apt and the same error happened.. If I still get the same problem next time there is a major release I will just start from scratch to avoid it.
 
Last edited:
Hi all, first time here.

Just found out my problem with:pve-manager: not correctly installed


All I did was to configure a hostname for the ProxMox as it was defaulted to the IP address of the system (or I never set it up in the first place).

My setup was continuous upgrade from 1.4 or 1.5 an so... (currently 1.8).

I hope this helps someone.
 
Here it is (I changed to 2.6.35 from 2.6.32 right after fixing this issue):

Code:
pve-manager: 1.8-18 (pve-manager/1.8/6070)
running kernel: 2.6.35-1-pve
proxmox-ve-2.6.35: 1.8-11
pve-kernel-2.6.32-4-pve: 2.6.32-33 (for back out purposes)
pve-kernel-2.6.35-1-pve: 2.6.35-11
pve-kernel-2.6.24-7-pve: 2.6.24-11 (to be cleaned)
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.27-1pve1
vzdump: 1.2-13
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.14.1-1
ksm-control-daemon: 1.0-6
 
The Bug is already present in pve-manager 2.0-14.

The Solution:
Code:
diff  /var/lib/dpkg/info/pve-manager.postinst /var/lib/dpkg/info/pve-manager.postinst~
44c44
<     update-rc.d pvebanner start 99 2 3 4 5 . >/dev/null
---
>     update-rc.d pvebanner start 99 2 3 4 5 >/dev/null
 
The Bug is already present in pve-manager 2.0-14.

The Solution:
Code:
diff  /var/lib/dpkg/info/pve-manager.postinst /var/lib/dpkg/info/pve-manager.postinst~
44c44
<     update-rc.d pvebanner start 99 2 3 4 5 . >/dev/null
---
>     update-rc.d pvebanner start 99 2 3 4 5 >/dev/null

Why do you think that is a solution (what for)? For me both commands works without problems (with or without dot).