proxmox install on Debian Squeeze fails

[nicolasdiogo]

hello

i have installed a fresh Debian x64 (6.0.4)

and added the repo for proxmox as per documents,

but while installing the packages it gives the following error:

# apt-get install -y proxmox-ve-2.6.32
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  clvm fence-agents-pve libpve-access-control libpve-storage-perl pve-cluster pve-manager qemu-server redhat-cluster-pve resource-agents-pve
  vzctl
The following NEW packages will be installed:
  clvm fence-agents-pve libpve-access-control libpve-storage-perl proxmox-ve-2.6.32 pve-cluster pve-manager qemu-server redhat-cluster-pve
  resource-agents-pve vzctl
0 upgraded, 11 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/3,680 kB of archives.
After this operation, 6,439 kB of additional disk space will be used.
Preconfiguring packages ...
Selecting previously deselected package pve-cluster.
(Reading database ... 43421 files and directories currently installed.)
Unpacking pve-cluster (from .../pve-cluster_1.0-23_amd64.deb) ...
Selecting previously deselected package redhat-cluster-pve.
Unpacking redhat-cluster-pve (from .../redhat-cluster-pve_3.1.8-3_amd64.deb) ...
Selecting previously deselected package fence-agents-pve.
Unpacking fence-agents-pve (from .../fence-agents-pve_3.1.7-1_amd64.deb) ...
Selecting previously deselected package libpve-access-control.
Unpacking libpve-access-control (from .../libpve-access-control_1.0-17_amd64.deb) ...
Selecting previously deselected package clvm.
Unpacking clvm (from .../clvm_2.02.88-2pve1_amd64.deb) ...
Selecting previously deselected package libpve-storage-perl.
Unpacking libpve-storage-perl (from .../libpve-storage-perl_2.0-12_all.deb) ...
Selecting previously deselected package qemu-server.
Unpacking qemu-server (from .../qemu-server_2.0-25_amd64.deb) ...
Selecting previously deselected package resource-agents-pve.
Unpacking resource-agents-pve (from .../resource-agents-pve_3.9.2-3_amd64.deb) ...
Selecting previously deselected package pve-manager.
Unpacking pve-manager (from .../pve-manager_2.0-38_all.deb) ...
Selecting previously deselected package vzctl.
Unpacking vzctl (from .../vzctl_3.0.30-2pve1_amd64.deb) ...
unable to backup existing configuration
dpkg: error processing /var/cache/apt/archives/vzctl_3.0.30-2pve1_amd64.deb (--unpack):
 subprocess new pre-installation script returned error exit status 1
configured to not write apport reports
                                      Selecting previously deselected package proxmox-ve-2.6.32.
Unpacking proxmox-ve-2.6.32 (from .../proxmox-ve-2.6.32_2.0-60_all.deb) ...
Processing triggers for man-db ...
Errors were encountered while processing:
 /var/cache/apt/archives/vzctl_3.0.30-2pve1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

and for some reason i am also failing to the the IP correctly set on this system:

pmxcfs 
[main] crit: Unable to get local IP address

but i have my setup as:
/etc/hostname

myserver01.local.lan

and, /etc/hosts

27.0.0.1        localhost
127.0.1.1      myserver01.local.lan myserver01
192.168.1.22 myserver01.local.lan myserver01
...

with a static IP = 192.168.1.22

any suggestions on how to complete the installation successfully?

thanks,

 

[dietmar]

Try

# rmdir /etc/vz/conf

any try again - does that help?

 

[nicolasdiogo]

Try

# rmdir /etc/vz/conf

any try again - does that help?

tried that and did not help - same error.
uninstalled every thing related to pve.
rebooted
removed any folder related to the failed installation
tried installing again and got same error.

also tried on another box on a fresh install of Debian 6.0.2 (netinstall) x64 - and i got same error.

but reading on the forum i can not find nobody else having this problem.

what can i try now?

thanks,

 

[dietmar]

Please try:

# rm -rf /etc/vz/conf.org

then run apt-get again.

 

[Xentux]

I have had the same prob and installed vzctl manually with dpkg -i vzctl_3.0.30-2pve1_amd64.deb
After that the rest could be installed the normal way ... but in my case the whole setup was messed up due to my testing and a fresh installation was needed.

 

[PauloEmerique]

Hi, I was having same problem, what solved was to change FQDN to simple name (servername.domain.com to servername), as stated in another forum post: http://forum.proxmox.com/threads/9001-Problem-with-pve-upgrade-1-9-to-2-0?p=52091#post52091

Cheers,

Paulo Emerique
eSense Tecnologia
http://www.esensetec.com.br