ERROR after update to 2.2

[robson_ek]

Hello,

Today i`m updateing my proxmox VE. After apdate i have some errors:

root@proxmox:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
 openssh-server : Depends: openssh-client (= 1:5.5p1-6+squeeze2) but 1:5.5p1-6+squeeze1 is installed
                  Recommends: openssh-blacklist-extra but it is not installed
 python : Depends: python-minimal (= 2.6.6-3+squeeze7) but 2.6.6-3+squeeze6 is installed
E: Unmet dependencies. Try using -f.
root@proxmox:~#

root@proxmox:~# apt-get dist-upgrade -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
Calculating upgrade... Done
The following packages will be upgraded:
  openssh-client procps python-minimal
3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
73 not fully installed or removed.
Need to get 0 B/1217 kB of archives.
After this operation, 94.2 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Reading changelogs... Done
(Reading database ... 30533 files and directories currently installed.)
Preparing to replace procps 1:3.2.8-9 (using .../procps_1%3a3.2.8-9squeeze1_amd64.deb) ...
Unpacking replacement procps ...
dpkg: error processing /var/cache/apt/archives/procps_1%3a3.2.8-9squeeze1_amd64.deb (--unpack):
 unable to make backup link of `./usr/bin/top' before installing new version: Operation not permitted
configured to not write apport reports
                                      dpkg-deb: subprocess paste killed by signal (Broken pipe)
dpkg: error while cleaning up:
 subprocess new post-removal script returned error exit status 1
Preparing to replace python-minimal 2.6.6-3+squeeze6 (using .../python-minimal_2.6.6-3+squeeze7_all.deb) ...
find: invalid predicate `-delete'
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
find: invalid predicate `-delete'
dpkg: error processing /var/cache/apt/archives/python-minimal_2.6.6-3+squeeze7_all.deb (--unpack):
 subprocess new pre-removal script returned error exit status 1
configured to not write apport reports
                                      Preparing to replace openssh-client 1:5.5p1-6+squeeze1 (using .../openssh-client_1%3a5.5p1-6+squeeze2_amd64.deb) ...
Unpacking replacement openssh-client ...
dpkg: error processing /var/cache/apt/archives/openssh-client_1%3a5.5p1-6+squeeze2_amd64.deb (--unpack):
 unable to make backup link of `./usr/bin/scp' before installing new version: Operation not permitted
configured to not write apport reports
                                      dpkg-deb: subprocess paste killed by signal (Broken pipe)
Processing triggers for man-db ...
Errors were encountered while processing:
 /var/cache/apt/archives/procps_1%3a3.2.8-9squeeze1_amd64.deb
 /var/cache/apt/archives/python-minimal_2.6.6-3+squeeze7_all.deb
 /var/cache/apt/archives/openssh-client_1%3a5.5p1-6+squeeze2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@proxmox:~#

root@proxmox:~# pveversion -v
pve-manager: not correctly installed (pve-manager/2.2/d3818aa7)
running kernel: 2.6.32-11-pve
pve-kernel-2.6.32-11-pve: 2.6.32-66
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: not correctly installed
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: not correctly installed
resource-agents-pve: 3.9.2-3
fence-agents-pve: not correctly installed
pve-cluster: not correctly installed
qemu-server: not correctly installed
pve-firmware: not correctly installed
libpve-common-perl: not correctly installed
libpve-access-control: not correctly installed
libpve-storage-perl: not correctly installed
vncterm: not correctly installed
vzctl: not correctly installed
vzprocps: 2.0.11-2
vzquota: not correctly installed
root@proxmox:~#

Proxmox working correctly....

Please help me.

 

[tom]

...

Proxmox working correctly....

Please help me.

no, looks not ok. how did you install this server? what version did you have before you try to upgrade to 2.2?

 

[robson_ek]

2.1

 

[robson_ek]

no, looks not ok. how did you install this server? what version did you have before you try to upgrade to 2.2?

I type two command from proxmox wiki. (apt-get update & apt-get disp-upgrade)
Before i was Proxmox 2.1

 

[robson_ek]

I use this instuction: http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_2.x_to_latest_2.2

It was Proxmox VE 2.1

 

[mir]

no, looks not ok. how did you install this server? what version did you have before you try to upgrade to 2.2?

I looks as an upgrade made from pve < 2.0. Eg. an upgrade from Lenny to Squeeze.

 

[robson_ek]

No, i was Debian Proxmox 2.1.

I wrote about this some hours ago, but this post i still waiting for publish.