pve-manager not updated correctly 1.7

vorgusa

Well-Known Member
Oct 28, 2009
37
0
46
Hi,
I just upgraded 1.6 to 1.7 and ran into an error during the update. Everything appears to be fine now, but if I run pveversion -v I get:

# pveversion -v
pve-manager: not correctly installed (pve-manager/1.7/5323)
running kernel: 2.6.35-1-pve
pve-kernel-2.6.35-1-pve: 2.6.35-7
qemu-server: 1.1-25
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-16
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-9
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1

and after running apt-get dist-upgrade I received error messages saying:

subprocess post-installation script returned error exit status 1

should I be concerned about this?
 
I get the same errors when I try to install that. I already had 2.6.35 installed though

dpkg: error processing pve-manager (--configure):
subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve-2.6.35:
proxmox-ve-2.6.35 depends on pve-manager; however:
Package pve-manager is not configured yet.
dpkg: error processing proxmox-ve-2.6.35 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-manager
proxmox-ve-2.6.35
E: Sub-process /usr/bin/dpkg returned an error code (1)
 
its a plain proxmox installation. I installed it with the proxmox 1.6 CD
 
It is a normal installation, I just did apt-get remove and then tried to install it to see if it would fix the problem. All I did was update the box and the error happened.. nothing fancy. The only thing unusual I have on the box is an NFS server
 
I already tried to reinstall them again, and it did not work

Server:~# apt-get install pve-manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
pve-manager is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Setting up pve-manager (1.7-10) ...
dpkg: error processing pve-manager (--configure):
subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve-2.6.35:
proxmox-ve-2.6.35 depends on pve-manager; however:
Package pve-manager is not configured yet.
dpkg: error processing proxmox-ve-2.6.35 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-manager
proxmox-ve-2.6.35
E: Sub-process /usr/bin/dpkg returned an error code (1)
 
try to resolve the dependency issues with 'aptitude' instead of 'apt-get'.
 
same errors :( Nothing seems to be wrong with the program. The web interface still works and I was able to create a VM. I just dont know what will happen next time I upgrade or update.
 
looking back at the initial install log I see this:

Log started: 2010-12-05 13:25:30
Setting up pve-manager (1.7-10) ...
dpkg: error processing pve-manager (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
pve-manager
Log ended: 2010-12-05 13:25:30
 
dpkg: error processing pve-manager (--configure):
subprocess post-installation script returned error exit status 1

Seems you removed a package which is needed by the postinst script (but we have no dependency for it). Is apache2-common installed? Is there more info in /var/log/dpkg.log?
 
Try to run the postinst script manually - maybe you get a more verbose error message then?

# /var/lib/dpkg/info/pve-manager.postinst configure
 
I have not messed with anything Apache related.. the only time I removed a package was after I ran the update and pve-manager would not configure... I then reinstalled the package. Looks like its apache2.2-common now, which is installed, and the configure script showed even less then the apt-get install. All outputs are below


Server:~# apt-get install apache2-common
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package apache2-common is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
apache2.2-common apache2-utils
E: Package apache2-common has no installation candidate

Server:~# apt-get install apache2.2-common
Reading package lists... Done
Building dependency tree
Reading state information... Done
apache2.2-common is already the newest version.

Server:~# /var/lib/dpkg/info/pve-manager.postinst configure
Server:~#
 
Also, I do not see anything at all in the dpkg.log or dpkg.log.1... the last thing was in october. I see older pve-manager 1.6-5 updates in there, but nothing related to the recent one. the logs in /var/log/apt/term.log are just the output from apt-get install, which I have posted before.
 
Server:/mnt/Virtual/iso# dpkg-reconfigure pve-manager
/usr/sbin/dpkg-reconfigure: pve-manager is broken or not fully installed

Server:/mnt/Virtual/iso# cat /etc/apt/sources.list
deb http://ftp.us.debian.org/debian lenny main contrib

# PVE packages provided by proxmox.com
deb http://download.proxmox.com/debian lenny pve

#deb http://download.proxmox.com/debian lenny pvetest

# security updates
deb http://security.debian.org/ lenny/updates main contrib

I have the test repository in there, but I have not used it on this installation.

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

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!