[gelöst] Proxmox und Debian Jessie - Compilation failed

[McAldo]

Hallo,

ich versuche gerade Proxmox Version 4.x zu installieren, das scheitert aber an Abhängigkeiten und Fehlern beim Kompilieren. Es lief Debian/Wheezy und Proxmox 3.x. In der sources.list habe ich alles auf Jessie geändert und beim Proxmox-Debian-Archiv auf.

Code: Alles auswählen

deb http://download.proxmox.com/debian jessie pvetest

Nun scheitert es an der Installation der pve-* Pakete. Der Proxmox-Kernel aus pvetest ist drauf. Ich versuche also pve-cluster per dpkg zu installieren:

Code: Alles auswählen

dpkg -i --force-all pve-cluster_4.0-14_amd64.deb 
(Reading database ... 40082 files and directories currently installed.)
Preparing to unpack pve-cluster_4.0-14_amd64.deb ...
Unpacking pve-cluster (4.0-14) over (4.0-14) ...
Setting up pve-cluster (4.0-14) ...
Socket object version 2.013 does not match bootstrap parameter 2.016 at /usr/share/perl/5.20/XSLoader.pm line 92.
Compilation failed in require at /usr/bin/pvecm line 6.
BEGIN failed--compilation aborted at /usr/bin/pvecm line 6.
dpkg: error processing package pve-cluster (--install):
 subprocess installed post-installation script returned error exit status 2
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for systemd (215-17+deb8u1) ...
Errors were encountered while processing:
 pve-cluster

Und per dist-upgrade:

Code: Alles auswählen

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.
4 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-cluster (4.0-14) ...
Socket object version 2.013 does not match bootstrap parameter 2.016 at /usr/share/perl/5.20/XSLoader.pm line 92.
Compilation failed in require at /usr/bin/pvecm line 6.
BEGIN failed--compilation aborted at /usr/bin/pvecm line 6.
dpkg: error processing package pve-cluster (--configure):
 subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of pve-ha-manager:
 pve-ha-manager depends on pve-cluster (>= 3.0-17); however:
  Package pve-cluster is not configured yet.

dpkg: error processing package pve-ha-manager (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-container:
 pve-container depends on pve-cluster (>= 4.0-8); however:
  Package pve-cluster is not configured yet.
 pve-container depends on pve-ha-manager; however:
  Package pve-ha-manager is not configured yet.

dpkg: error processing package pve-container (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-firewall:
 pve-firewall depends on pve-cluster; however:
  Package pve-cluster is not configured yet.

dpkg: error processing package pve-firewall (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 pve-cluster
 pve-ha-manager
 pve-container
 pve-firewall
E: Sub-process /usr/bin/dpkg returned an error code (1)

Was könnte der Fehler sein und wie ist dieser zu beheben?

[rendegast]

Socket object version 2.013 does not match bootstrap parameter 2.016 at /usr/share/perl/5.20/XSLoader.pm line 92.

Geht wohl um den Befehl

Code: Alles auswählen

[/usr/bin/]pvecm updatecerts --silent

in postinst, service-Datei und init-Skript.

Wohl irgendeine perl-Inkompatibilität.

Code: Alles auswählen

$ grep -r 2.01[36] 5.20.2/* -C1
5.20.2/Module/CoreList.pm-            'SDBM_File'             => '1.10',
5.20.2/Module/CoreList.pm:            'Socket'                => '2.013',
5.20.2/Module/CoreList.pm-            'TAP::Base'             => '3.30',
--
5.20.2/Module/CoreList.pm-            'POSIX'                 => '1.45',
5.20.2/Module/CoreList.pm:            'Socket'                => '2.016',
5.20.2/Module/CoreList.pm-            'Test::Builder'         => '1.001008',
--

(das ist wohl so eine Art changelog)

Melde den Fehler doch bei proxmox.

[McAldo]

Danke für den Hinweis. Manchmal sieht man es selber nicht.

Die Installation konnte nun abgeschlossen werden. Ich habe ein Perl-Paket deinstalliert:

Code: Alles auswählen

apt-get remove --purge libsocket-perl

und dann wieder installiert:

Code: Alles auswählen

apt-get install libsocket-perl

Danach wurde die Installation von Proxmox 4.x abgeschlossen.

Code: Alles auswählen

pveversion -v
proxmox-ve: 4.0-3 (running kernel: 3.19.8-1-pve)
pve-manager: 4.0-24 (running version: 4.0-24/946af136)
pve-kernel-3.19.8-1-pve: 3.19.8-3
lvm2: 2.02.116-pve1
corosync-pve: 2.3.4-2
libqb0: 0.17.1-3
pve-cluster: 4.0-14
qemu-server: 4.0-13
pve-firmware: 1.1-5
libpve-common-perl: 4.0-10
libpve-access-control: 4.0-5
libpve-storage-perl: 4.0-12
pve-libspice-server1: 0.12.5-1
vncterm: 1.2-1
pve-qemu-kvm: 2.3-6
pve-container: 0.9-3
pve-firewall: 2.0-4
pve-ha-manager: 1.0-4
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2
lxc-pve: 1.1.2-1
lxcfs: 0.9-pve1
cgmanager: 0.37-pve1