problem after update to proxmox-ve-2.6.32

S

spoonman

New Member
Apr 11, 2011
13
0
1
After dist-upgrade I have this error:
Code: 
# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]?
Setting up pve-manager (2.3-13) ...
Restarting PVE Daemon: pvedaemon.
Restarting PVE Status Daemon: pvestatd.
dpkg: error processing pve-manager (--configure):
 subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
                                      dpkg: dependency problems prevent configuration of proxmox-ve-2.6.32:
 proxmox-ve-2.6.32 depends on pve-manager; however:
  Package pve-manager is not configured yet.
dpkg: error processing proxmox-ve-2.6.32 (--configure):
 dependency problems - leaving unconfigured
configured to not write apport reports
                                      Errors were encountered while processing:
 pve-manager
 proxmox-ve-2.6.32
E: Sub-process /usr/bin/dpkg returned an error code (1)

This is my # pveversion -v
Code: 
pve-manager: not correctly installed (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
pve-kernel-2.6.32-19-pve: 2.6.32-95
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-20
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-7
vncterm: 1.0-4
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1

Ho can I fix it ?

Best regards
Fabio
 
spoonman said:
After dist-upgrade I have this error:
Code: 
# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]?
Setting up pve-manager (2.3-13) ...
Restarting PVE Daemon: pvedaemon.
Restarting PVE Status Daemon: pvestatd.
dpkg: error processing pve-manager (--configure):
 subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
                                      dpkg: dependency problems prevent configuration of proxmox-ve-2.6.32:
 proxmox-ve-2.6.32 depends on pve-manager; however:
  Package pve-manager is not configured yet.
dpkg: error processing proxmox-ve-2.6.32 (--configure):
 dependency problems - leaving unconfigured
configured to not write apport reports
                                      Errors were encountered while processing:
 pve-manager
 proxmox-ve-2.6.32
E: Sub-process /usr/bin/dpkg returned an error code (1)

This is my # pveversion -v
Code: 
pve-manager: not correctly installed (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
pve-kernel-2.6.32-19-pve: 2.6.32-95
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-20
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-7
vncterm: 1.0-4
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1

Ho can I fix it ?

Best regards
Fabio
Click to expand...
Hi,
look at hostname, entry in /etc/hosts and network-config (/etc/network/interfaces) - you must have an fixed IP on vmbr0 (or eth0 but the normal behavior is vmbr0 with attached eth0).

Udo
 
I fixed mine by logging in direct to the server via ssh. I tried a shortcut via proxmox gui shell and ran into the problem , but I only faced it on one machine of 4.
 
udo said:
Hi,
look at hostname, entry in /etc/hosts and network-config (/etc/network/interfaces) - you must have an fixed IP on vmbr0 (or eth0 but the normal behavior is vmbr0 with attached eth0).

Udo
Click to expand...


my /etc/hosts is

Code: 
127.0.0.1       localhost

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
95.141.37.8 server.mydomain.it server

...


my /etc/network/interfaces

Code: 
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 95.141.37.8
        netmask 255.255.255.0
        network 95.141.37.0
        broadcast 95.141.37.255
        gateway 95.141.37.1
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0
        bridge_maxwait 0
auto eth0
iface eth0 inet manual

auto vmbr1
iface vmbr1 inet static
        address 10.10.11.1
        netmask 255.255.255.0
        bridge_ports none
        bridge_stp off
        bridge_fd 0
        post-up echo 1 > /proc/sys/net/ipv4/ip_forward
        post-up iptables -t nat -A POSTROUTING -s '10.10.11.0/24' -o vmbr1 -j MASQUERADE
        post-down iptables -t nat -D POSTROUTING -s '10.10.11.0/24' -o vmbr1 -j MASQUERADE

best regards
Fabio
 
Hello if can't fix the problem in the upgrade, can I revert to the old release ?

best regards
Fabio
 
You must log in or register to reply here.
Top Bottom