update VE 1.5 to 1.6 - dpkg: error processing vzctl (--configure)

L

lbm

Renowned Member
Feb 11, 2010
8
0
66
Hi guys!

this is output of my update:

Code: 
moving openvz sysctl settings to /etc/sysctl.d/vzctl.conf
/etc/init.d/vz: line 503: /var/lock/subsys/vz_lock.26076: No such file or directory
Can't write to /var/lock/subsys/vz_lock.26076
cat: /var/lock/subsys/vz_lock: No such file or directory
/etc/init.d/vz: line 518: /var/lock/subsys/vz_lock: No such file or directory
Starting OpenVZ: failed to load module vzmon..failed
invoke-rc.d: initscript vz, action "start" failed.
dpkg: error processing vzctl (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of pve-manager:
 pve-manager depends on vzctl (>= 3.0.23-1pve2); however:
  Package vzctl is not configured yet.
dpkg: error processing pve-manager (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of vzdump:
 vzdump depends on vzctl; however:
  Package vzctl is not configured yet.
dpkg: error processing vzdump (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve-2.6.24:
 proxmox-ve-2.6.24 depends on pve-manager; however:
  Package pve-manager is not configured yet.
 proxmox-ve-2.6.24 depends on vzctl; however:
  Package vzctl is not configured yet.
 proxmox-ve-2.6.24 depends on vzdump; however:
  Package vzdump is not configured yet.
dpkg: error processing proxmox-ve-2.6.24 (--configure):
 dependency problems - leaving unconfigured
before update:

Code: 
 pveversion -v
pve-manager: 1.5-10 (pve-manager/1.5/4822)
running kernel: 2.6.24-11-pve
proxmox-ve-2.6.24: 1.5-23
pve-kernel-2.6.24-11-pve: 2.6.24-23
qemu-server: 1.1-16
pve-firmware: 1.0-5
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.23-1pve11
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.4-1
Do you have some idea...?

Correction: Old versin of VE has been pve-manager/1.5/4728
sorry!
 
Last edited:
do you run aptitude update before with success? it would be a good idea to post the full log and not just a part.
 
dietmar said:
Is /var/lock mounted on RAM?

If so, do
# mkdir /var/lock/subsys/

then try to update again.
Click to expand...

to tom: of course, aptitude update has been run

/var/lock do not mounted on RAM, should be?

I ran "mkdir /var/lock/subsys/" after configure error, this error message:

Code: 
/etc/init.d/vz: line 503: /var/lock/subsys/vz_lock.26076: No such file or directory

clear off, but "vzctl" package still leaving unconfigured:
Code: 
# aptitude safe-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Reading extended state information      
Initializing package states... Done
Reading task descriptions... Done  
The following partially installed packages will be configured:
  proxmox-ve-2.6.24 pve-manager vzctl vzdump 
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Setting up vzctl (3.0.24-1pve3) ...
Starting OpenVZ: failed to load module vzmon..failed
invoke-rc.d: initscript vz, action "start" failed.
dpkg: error processing vzctl (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of pve-manager:
 pve-manager depends on vzctl (>= 3.0.23-1pve2); however:
  Package vzctl is not configured yet.
dpkg: error processing pve-manager (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of vzdump:
 vzdump depends on vzctl; however:
  Package vzctl is not configured yet.
dpkg: error processing vzdump (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve-2.6.24:
 proxmox-ve-2.6.24 depends on pve-manager; however:
  Package pve-manager is not configured yet.
 proxmox-ve-2.6.24 depends on vzctl; however:
  Package vzctl is not configured yet.
 proxmox-ve-2.6.24 depends on vzdump; however:
  Package vzdump is not configured yet.
dpkg: error processing proxmox-ve-2.6.24 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 vzctl
 pve-manager
 vzdump
 proxmox-ve-2.6.24
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up vzctl (3.0.24-1pve3) ...
Starting OpenVZ: failed to load module vzmon..failed
invoke-rc.d: initscript vz, action "start" failed.
dpkg: error processing vzctl (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of pve-manager:
 pve-manager depends on vzctl (>= 3.0.23-1pve2); however:
  Package vzctl is not configured yet.
dpkg: error processing pve-manager (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve-2.6.24:
 proxmox-ve-2.6.24 depends on pve-manager; however:
  Package pve-manager is not configured yet.
 proxmox-ve-2.6.24 depends on vzctl; however:
  Package vzctl is not configured yet.
dpkg: error processing proxmox-ve-2.6.24 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of vzdump:
 vzdump depends on vzctl; however:
  Package vzctl is not configured yet.
dpkg: error processing vzdump (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 vzctl
 pve-manager
 proxmox-ve-2.6.24
 vzdump
 
No, it should no be on tmpfs. I just wonder why that directory is not there?

what is the output of

# modprobe vzmon;echo $?
 
dietmar said:
No, it should no be on tmpfs. I just wonder why that directory is not there?

what is the output of

# modprobe vzmon;echo $?
Click to expand...
here is output:
Code: 
root@caddy1:# modprobe vzmon;echo $?
FATAL: Could not load /lib/modules/2.6.24-11-pve/modules.dep: No such file or directory
1
But i found out that "vzmon" (and other vz... modules) are loaded and try this:
in /etc/vz/vz.conf uncomment "MODULES_DISABLED=yes"

and then:
Code: 
root@caddy1:/etc/network# /etc/init.d/vz start
Starting OpenVZ: ..done
root@caddy1:/etc/network# aptitude safe-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Reading extended state information      
Initializing package states... Done
Reading task descriptions... Done  
The following partially installed packages will be configured:
  proxmox-ve-2.6.24 pve-manager vzctl vzdump 
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Setting up vzctl (3.0.24-1pve3) ...
OpenVZ already running..failed
Setting up pve-manager (1.6-2) ...
Restarting PVE daemon: pvedaemon.
Restarting PVE Tunnel Server: pvetunnel.
Restarting PVE Cluster Server: pvemirror.
Restarting web server: apache2 ... waiting .
Setting up vzdump (1.2-7) ...
Setting up proxmox-ve-2.6.24 (1.5-24) ...
installing proxmox release key: OK
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Reading extended state information      
Initializing package states... Done
Reading task descriptions... Done
...it is look like good or not? ;-)
 
lbm said:
here is output:
Code: 
root@caddy1:# modprobe vzmon;echo $?
FATAL: Could not load /lib/modules/2.6.24-11-pve/modules.dep: No such file or directory
1
Click to expand...

Yep, now I see the issue: "/lib/modules/2.6.24-11-pve/modules.dep"
update procedure install new version of kernel package befor configure "vzctl" package an new path is: "/lib/modules/2.6.24-12-pve/modules.dep" ...
 
BTW: I think, that proxmoxVE "KVM only" fork is good idea. I used on other nodes kernel 2.6.32 kvm heretofore and everything has been simpliest... little. ;) In any case Proxmox VE is very good piece of software. Thank you for your job!
 
You must log in or register to reply here.
Top Bottom