After upgrading from 3.2 to 3.3 proxmox doesnt start

[reji]

root@cloud1:~# aptitude reinstall pve-manager
The following packages will be REINSTALLED:
pve-manager
0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 4 not upgraded.
Need to get 0 B/3,875 kB of archives. After unpacking 0 B will be used.
Preconfiguring packages ...
(Reading database ... 54924 files and directories currently installed.)
Preparing to replace pve-manager 3.3-5 (using .../pve-manager_3.3-5_amd64.deb) ...
Unpacking replacement pve-manager ...
Processing triggers for pve-firewall ...
Restarting Proxmox VE firewall: pve-firewall.
Processing triggers for man-db ...
Setting up pve-manager (3.3-5) ...
Restarting PVE Daemon: pvedaemonunabe to find handler for 'GET: /access/ticket' at /usr/share/perl5/PVE/RESTHandler.pm line 260.
Compilation failed in require at /usr/bin/pvedaemon line 16.
BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 16.
(warning).
Restarting PVE API Proxy Server: pveproxyunabe to find handler for 'GET: /access/ticket' at /usr/share/perl5/PVE/RESTHandler.pm line 260.
Compilation failed in require at /usr/bin/pveproxy line 24.
BEGIN failed--compilation aborted at /usr/bin/pveproxy line 24.
(warning).
Restarting PVE SPICE Proxy Server: spiceproxy.
Restarting PVE Status Daemon: pvestatd.

root@cloud1:~# pvedaemon -v
unabe to find handler for 'GET: /access/ticket' at /usr/share/perl5/PVE/RESTHandler.pm line 260.
Compilation failed in require at /usr/bin/pvedaemon line 16.
BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 16.

What information you need?

 

[dietmar]

# pveversion -v

 

[reji]

I have two problem server.
Without apt-get dist-upgrade(only apt-get upgrade):

root@cloud1:~# pveversion -v
proxmox-ve-2.6.32: 3.2-132 (running kernel: 2.6.32-31-pve)
pve-manager: 3.3-5 (running version: 3.3-5/bfebec03)
pve-kernel-2.6.32-25-pve: 2.6.32-113
pve-kernel-2.6.32-31-pve: 2.6.32-132
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-15
qemu-server: 3.3-1
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-25
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

With apt-get dist-upgrade:

root@cloud2:~# pveversion -v
proxmox-ve-2.6.32: 3.3-138 (running kernel: 2.6.32-33-pve)
pve-manager: 3.3-2 (running version: 3.3-2/995e687e)
pve-kernel-2.6.32-33-pve: 2.6.32-138
pve-kernel-2.6.32-31-pve: 2.6.32-132
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-1
pve-cluster: 3.0-15
qemu-server: 3.1-35
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-15
libpve-storage-perl: 3.0-23
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: not correctly installed
vzquota: 3.1-2
pve-qemu-kvm: 2.1-9
ksm-control-daemon: not correctly installed
glusterfs-client: 3.5.2-1

On second machine apt-get --reinstall install pve-manager qemu-server libpve-storage-perl solve problem

 

[reji]

upd: seems to do multiple times apt-get upgrade -y && apt-get dist-upgrade -y solve problem.
Strange. If i do "apt-get upgrade" without "apt-get dist-upgrade", then i will break my Proxmox VE.