Proxmox 4.x Clean installation 8.2 Jessie - dpkg error

ssaman

Active Member
Oct 28, 2015
38
2
28
Hello,

We are trying to install Proxmox 4 like in "wiki/Install_Proxmox_VE_on_Debian_Jessie" and have a problem to install
Code:
apt install proxmox-ve ntp ssh postfix ksm-control-daemon open-iscsi

this is our output:
Code:
Job for pve-cluster.service failed. See 'systemctl status pve-cluster.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript pve-cluster, action "start" failed.
dpkg: error processing package pve-cluster (--configure):
 subprocess installed post-installation script returned error exit status 1
....
Code:
Setting up oathtool (2.4.1-1) ...
dpkg: dependency problems prevent configuration of libpve-access-control:
 libpve-access-control depends on pve-cluster; however:
  Package pve-cluster is not configured yet.
...
Code:
dpkg: error processing package libpve-access-control (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of librados2-perl:
 librados2-perl depends on libpve-access-control; however:
  Package libpve-access-control is not configured yet.
...
Code:
dpkg: error processing package librados2-perl (--configure):
 dependency problems - leaving unconfigured
Setting up libtie-ixhash-perl (1.23-1) ...
...
Code:
dpkg: dependency problems prevent configuration of pve-firewall:
 pve-firewall depends on pve-cluster; however:
  Package pve-cluster is not configured yet.
 pve-firewall depends on libpve-access-control; however:
  Package libpve-access-control is not configured yet.
..
Code:
dpkg: error processing package pve-firewall (--configure):
 dependency problems - leaving unconfigured
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.
...
Code:
dpkg: error processing package pve-ha-manager (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of qemu-server:
 qemu-server depends on libpve-access-control; however:
  Package libpve-access-control is not configured yet.
 qemu-server depends on pve-cluster; however:
  Package pve-cluster is not configured yet.
 qemu-server depends on pve-firewall; however:
  Package pve-firewall is not configured yet.
 qemu-server depends on pve-ha-manager; however:
  Package pve-ha-manager is not configured yet.
...
Code:
dpkg: error processing package qemu-server (--configure):
 dependency problems - leaving unconfigured
Setting up spiceterm (2.0-1) ...
Setting up libev-perl (4.18-1) ...
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.
...
Code:
dpkg: error processing package pve-container (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-manager:
 pve-manager depends on qemu-server (>= 1.1-1); however:
  Package qemu-server is not configured yet.
 pve-manager depends on pve-cluster (>= 1.0-29); however:
  Package pve-cluster is not configured yet.
 pve-manager depends on libpve-access-control (>= 3.0-2); however:
  Package libpve-access-control is not configured yet.
 pve-manager depends on librados2-perl; however:
  Package librados2-perl is not configured yet.
 pve-manager depends on pve-firewall; however:
  Package pve-firewall is not configured yet.
 pve-manager depends on pve-ha-manager; however:
  Package pve-ha-manager is not configured yet.
 pve-manager depends on pve-container; however:
  Package pve-container is not configured yet.
..
Code:
dpkg: error processing package pve-manager (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on pve-manager; however:
  Package pve-manager is not configured yet.
 proxmox-ve depends on qemu-server; however:
  Package qemu-server is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
...
Code:
Setting up apparmor (2.9.0-3) ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Job for apparmor.service failed. See 'systemctl status apparmor.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript apparmor, action "start" failed.
...
Code:
Errors were encountered while processing:
 pve-cluster
 libpve-access-control
 librados2-perl
 pve-firewall
 pve-ha-manager
 qemu-server
 pve-container
 pve-manager
 proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

do you have any advice for us?

EDIT:

output of: systemctl status pve-cluster.service

Code:
● pve-cluster.service - The Proxmox VE cluster filesystem
   Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled)
   Active: failed (Result: exit-code) since Thu 2015-11-05 12:11:06 CET; 6min ago

Nov 05 12:11:06 pve4-node1 pmxcfs[8385]: [main] crit: Unable to get local IP address
Nov 05 12:11:06 pve4-node1 pmxcfs[8385]: [main] crit: Unable to get local IP address
Nov 05 12:11:06 pve4-node1 systemd[1]: pve-cluster.service: control process exited, code=exited status=255
Nov 05 12:11:06 pve4-node1 systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Nov 05 12:11:06 pve4-node1 systemd[1]: Unit pve-cluster.service entered failed state.

and journalctl -xn

Code:
-- Logs begin at Thu 2015-11-05 09:49:50 CET, end at Thu 2015-11-05 12:19:07 CET. --
Nov 05 12:11:22 pve4-node1 systemd-sysv-generator[14077]: Ignoring creation of an alias umountiscsi.service for itself
Nov 05 12:11:22 pve4-node1 systemd-sysv-generator[14094]: Ignoring creation of an alias umountiscsi.service for itself
Nov 05 12:11:22 pve4-node1 systemd-sysv-generator[14107]: Ignoring creation of an alias umountiscsi.service for itself
Nov 05 12:11:39 pve4-node1 systemd-timesyncd[8383]: interval/delta/delay/jitter/drift 64s/+0.009s/0.009s/0.003s/+10ppm
Nov 05 12:12:43 pve4-node1 systemd-timesyncd[8383]: interval/delta/delay/jitter/drift 128s/-0.001s/0.009s/0.004s/+7ppm
Nov 05 12:14:51 pve4-node1 systemd-timesyncd[8383]: interval/delta/delay/jitter/drift 256s/-0.002s/0.009s/0.004s/+3ppm
Nov 05 12:17:01 pve4-node1 CRON[17784]: pam_unix(cron:session): session opened for user root by (uid=0)
Nov 05 12:17:01 pve4-node1 CRON[17785]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Nov 05 12:17:01 pve4-node1 CRON[17784]: pam_unix(cron:session): session closed for user root
Nov 05 12:19:07 pve4-node1 systemd-timesyncd[8383]: interval/delta/delay/jitter/drift 512s/-0.003s/0.008s/0.005s/+0ppm
 
Last edited:
I do not understand... I have done tens of proxmox installations but today's cluster installation gives me errors, perhaps I need more coffe, but I cannot see where I'm failing
Code:
root@t01:~# cat /etc/hosts
127.0.0.1       localhost               
192.168.200.81  t01
root@t01:~# getent hosts t01
192.168.200.81  t01
root@t01:~# getent hosts 192.168.200.81
192.168.200.81  t01
root@t01:~# cat /etc/hostname
t01


root@t01:~# dpkg --configure -a
Setting up pve-cluster (4.0-41) ...
Error opening Private Key /etc/pve/priv/authkey.key
140452977940112:error:02001002:system library:fopen:No such file or directory:bss_file.c:398:fopen('/etc/pve/priv/authkey.key','r')
140452977940112:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:400:
unable to load Private Key
command 'openssl rsa -in /etc/pve/priv/authkey.key -pubout -out /etc/pve/authkey.pub' failed: exit code 1
dpkg: error processing package pve-cluster (--configure):
subprocess installed post-installation script returned error exit status 1
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
dpkg: dependency problems prevent configuration of qemu-server:
qemu-server depends on pve-cluster; however:
Package pve-cluster is not configured yet.
qemu-server depends on pve-firewall; however:
Package pve-firewall is not configured yet.

dpkg: error processing package qemu-server (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on qemu-server; however:
Package qemu-server is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-manager:
pve-manager depends on qemu-server (>= 1.1-1); however:
Package qemu-server is not configured yet.
pve-manager depends on pve-cluster (>= 1.0-29); however:
Package pve-cluster is not configured yet.
pve-manager depends on pve-firewall; however:
Package pve-firewall is not configured yet.

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

dpkg: error processing package libpve-access-control (--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.

dpkg: error processing package pve-container (--configure):
dependency problems - leaving unconfigured
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.
pve-ha-manager depends on qemu-server; however:
Package qemu-server is not configured yet.

dpkg: error processing package pve-ha-manager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of librados2-perl:
librados2-perl depends on libpve-access-control; however:
Package libpve-access-control is not configured yet.

dpkg: error processing package librados2-perl (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-cluster
pve-firewall
qemu-server
proxmox-ve
pve-manager
libpve-access-control
pve-container
pve-ha-manager
librados2-perl

I now must be a IP related issue, but I can't really see it... any idea?
 
packages are uploaded and tested, works again.
 
Hi

I actually have the same issue as above, thank for your time and help

a full netinstall debian8 and after I followed this howto https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Jessie


I have the good values in /etc/hosts

root@htpc:/home/lsd# getent hosts $(hostname)
127.0.1.1 htpc.lan htpc htpc
192.168.12.100 htpc.lan htpc htpc

root@htpc:/home/lsd# getent hosts 192.168.12.100
192.168.12.100 htpc.lan htpc

the error messages of apt are

...

dpkg: des problèmes de dépendances empêchent la configuration de libpve-access-control :
libpve-access-control dépend de pve-cluster ; cependant :
Le paquet pve-cluster n'est pas encore configuré.

dpkg: erreur de traitement du paquet libpve-access-control (--configure) :
problèmes de dépendances - laissé non configuré
Paramétrage de thin-provisioning-tools (0.3.2-1) ...
Paramétrage de libpve-storage-perl (4.0-55) ...
dpkg: des problèmes de dépendances empêchent la configuration de librados2-perl :
librados2-perl dépend de libpve-access-control ; cependant :
Le paquet libpve-access-control n'est pas encore configuré.

dpkg: erreur de traitement du paquet librados2-perl (--configure) :
problèmes de dépendances - laissé non configuré
Paramétrage de libtie-ixhash-perl (1.23-1) ...
Paramétrage de libusbredirparser1:amd64 (0.7-1) ...
Paramétrage de libxml-xpathengine-perl (0.13-1) ...
Paramétrage de libapparmor1:amd64 (2.9.0-3) ...
Paramétrage de libapparmor-perl (2.9.0-3) ...
Paramétrage de uidmap (1:4.2-3+deb8u1) ...
Paramétrage de lxcfs (2.0.0-pve2) ...
Paramétrage de lzop (1.03-3) ...
Paramétrage de netcat6 (1.0-8) ...
update-alternatives: utilisation de « /bin/nc6 » pour fournir « /bin/nc » (nc) en mode automatique
Paramétrage de novnc-pve (0.5-6) ...
Paramétrage de numactl (2.0.10-1) ...
Paramétrage de open-iscsi (2.0.873+git0.3b4b4500-8+deb8u1) ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Paramétrage de powermgmt-base (1.31+nmu1) ...
Paramétrage de pve-kernel-4.4.13-1-pve (4.4.13-56) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.13-1-pve /boot/vmlinuz-4.4.13-1-pve
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.13-1-pve /boot/vmlinuz-4.4.13-1-pve
update-initramfs: Generating /boot/initrd.img-4.4.13-1-pve
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.13-1-pve /boot/vmlinuz-4.4.13-1-pve
Generating grub configuration file ...
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
Found linux image: /boot/vmlinuz-4.4.13-1-pve
Found initrd image: /boot/initrd.img-4.4.13-1-pve
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
Found linux image: /boot/vmlinuz-3.16.0-4-amd64
Found initrd image: /boot/initrd.img-3.16.0-4-amd64
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
done
Paramétrage de pve-firmware (1.1-8) ...
Paramétrage de vncterm (1.2-1) ...
Paramétrage de pve-libspice-server1 (0.12.5-2) ...
Paramétrage de pve-qemu-kvm (2.5-19) ...
Paramétrage de socat (1.7.2.4-2) ...
Paramétrage de ipset (6.23-2) ...
dpkg: des problèmes de dépendances empêchent la configuration de pve-firewall :
pve-firewall dépend de pve-cluster ; cependant :
Le paquet pve-cluster n'est pas encore configuré.
pve-firewall dépend de libpve-access-control ; cependant :
Le paquet libpve-access-control n'est pas encore configuré.

dpkg: erreur de traitement du paquet pve-firewall (--configure) :
problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de pve-ha-manager :
pve-ha-manager dépend de pve-cluster (>= 3.0-17) ; cependant :
Le paquet pve-cluster n'est pas encore configuré.

dpkg: erreur de traitement du paquet pve-ha-manager (--configure) :
problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de qemu-server :
qemu-server dépend de libpve-access-control ; cependant :
Le paquet libpve-access-control n'est pas encore configuré.
qemu-server dépend de pve-cluster ; cependant :
Le paquet pve-cluster n'est pas encore configuré.
qemu-server dépend de pve-firewall ; cependant :
Le paquet pve-firewall n'est pas encore configuré.
qemu-server dépend de pve-ha-manager ; cependant :
Le paquet pve-ha-manager n'est pas encore configuré.

dpkg: erreur de traitement du paquet qemu-server (--configure) :
problèmes de dépendances - laissé non configuré
Paramétrage de spiceterm (2.0-1) ...
Paramétrage de gdisk (0.8.10-2) ...
Paramétrage de libev-perl (4.18-1) ...
dpkg: des problèmes de dépendances empêchent la configuration de pve-container :
pve-container dépend de pve-cluster (>= 4.0-8) ; cependant :
Le paquet pve-cluster n'est pas encore configuré.
pve-container dépend de pve-ha-manager ; cependant :
Le paquet pve-ha-manager n'est pas encore configuré.

dpkg: erreur de traitement du paquet pve-container (--configure) :
problèmes de dépendances - laissé non configuré
Paramétrage de pve-docs (4.2-7) ...
dpkg: des problèmes de dépendances empêchent la configuration de pve-manager :
pve-manager dépend de qemu-server (>= 1.1-1) ; cependant :
Le paquet qemu-server n'est pas encore configuré.
pve-manager dépend de pve-cluster (>= 1.0-29) ; cependant :
Le paquet pve-cluster n'est pas encore configuré.
pve-manager dépend de libpve-access-control (>= 3.0-2) ; cependant :
Le paquet libpve-access-control n'est pas encore configuré.
pve-manager dépend de librados2-perl ; cependant :
Le paquet librados2-perl n'est pas encore configuré.
pve-manager dépend de pve-firewall ; cependant :
Le paquet pve-firewall n'est pas encore configuré.
pve-manager dépend de pve-ha-manager ; cependant :
Le paquet pve-ha-manager n'est pas encore configuré.
pve-manager dépend de pve-container ; cependant :
Le paquet pve-container n'est pas encore configuré.

dpkg: erreur de traitement du paquet pve-manager (--configure) :
problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de proxmox-ve :
proxmox-ve dépend de pve-manager ; cependant :
Le paquet pve-manager n'est pas encore configuré.
proxmox-ve dépend de qemu-server ; cependant :
Le paquet qemu-server n'est pas encore configuré.

dpkg: erreur de traitement du paquet proxmox-ve (--configure) :
problèmes de dépendances - laissé non configuré
Paramétrage de python-blinker (1.3.dfsg2-1) ...
Paramétrage de python-ply (3.4-5) ...
Paramétrage de python-pycparser (2.10+dfsg-3) ...
Paramétrage de python-cffi (0.8.6-1) ...
Paramétrage de python-cryptography (0.6.1-1) ...
Paramétrage de python-openssl (0.14-1) ...
Paramétrage de python-ndg-httpsclient (0.3.2-1) ...
Paramétrage de python-pyasn1 (0.1.7-1) ...
Paramétrage de python-pyinotify (0.9.4-1) ...
Paramétrage de dh-python (1.20141111-2) ...
Paramétrage de python3 (3.4.2-2) ...
running python rtupdate hooks for python3.4...
running python post-rtupdate hooks for python3.4...
Paramétrage de apparmor (2.9.0-3) ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Job for apparmor.service failed. See 'systemctl status apparmor.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript apparmor, action "start" failed.
Paramétrage de lxc-pve (1.1.5-7) ...
Traitement des actions différées (« triggers ») pour systemd (215-17+deb8u4) ...
Traitement des actions différées (« triggers ») pour libc-bin (2.19-18+deb8u4) ...
Traitement des actions différées (« triggers ») pour initramfs-tools (0.120+deb8u2) ...
update-initramfs: Generating /boot/initrd.img-4.4.13-1-pve
Traitement des actions différées (« triggers ») pour python-support (1.0.15) ...
Des erreurs ont été rencontrées pendant l'exécution :
pve-cluster
libpve-access-control
librados2-perl
pve-firewall
pve-ha-manager
qemu-server
pve-container
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)
 
Last edited:
I have also tried to reconfigure

root@htpc:/home/lsd# dpkg --configure -a
Paramétrage de pve-cluster (4.0-42) ...
Job for pve-cluster.service failed. See 'systemctl status pve-cluster.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript pve-cluster, action "start" failed.
dpkg: erreur de traitement du paquet pve-cluster (--configure) :
le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
dpkg: des problèmes de dépendances empêchent la configuration de pve-firewall :
pve-firewall dépend de pve-cluster ; cependant :
Le paquet pve-cluster n'est pas encore configuré.

dpkg: erreur de traitement du paquet pve-firewall (--configure) :
problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de qemu-server :
qemu-server dépend de pve-cluster ; cependant :
Le paquet pve-cluster n'est pas encore configuré.
qemu-server dépend de pve-firewall ; cependant :
Le paquet pve-firewall n'est pas encore configuré.

dpkg: erreur de traitement du paquet qemu-server (--configure) :
problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de proxmox-ve :
proxmox-ve dépend de qemu-server ; cependant :
Le paquet qemu-server n'est pas encore configuré.

dpkg: erreur de traitement du paquet proxmox-ve (--configure) :
problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de pve-manager :
pve-manager dépend de qemu-server (>= 1.1-1) ; cependant :
Le paquet qemu-server n'est pas encore configuré.
pve-manager dépend de pve-cluster (>= 1.0-29) ; cependant :
Le paquet pve-cluster n'est pas encore configuré.
pve-manager dépend de pve-firewall ; cependant :
Le paquet pve-firewall n'est pas encore configuré.

dpkg: erreur de traitement du paquet pve-manager (--configure) :
problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de libpve-access-control :
libpve-access-control dépend de pve-cluster ; cependant :
Le paquet pve-cluster n'est pas encore configuré.

dpkg: erreur de traitement du paquet libpve-access-control (--configure) :
problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de pve-container :
pve-container dépend de pve-cluster (>= 4.0-8) ; cependant :
Le paquet pve-cluster n'est pas encore configuré.

dpkg: erreur de traitement du paquet pve-container (--configure) :
problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de pve-ha-manager :
pve-ha-manager dépend de pve-cluster (>= 3.0-17) ; cependant :
Le paquet pve-cluster n'est pas encore configuré.
pve-ha-manager dépend de qemu-server ; cependant :
Le paquet qemu-server n'est pas encore configuré.

dpkg: erreur de traitement du paquet pve-ha-manager (--configure) :
problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de librados2-perl :
librados2-perl dépend de libpve-access-control ; cependant :
Le paquet libpve-access-control n'est pas encore configuré.

dpkg: erreur de traitement du paquet librados2-perl (--configure) :
problèmes de dépendances - laissé non configuré
Des erreurs ont été rencontrées pendant l'exécution :
pve-cluster
pve-firewall
qemu-server
proxmox-ve
pve-manager
libpve-access-control
pve-container
pve-ha-manager
librados2-perl
 
as noted in the instructions, the hosts file should looke like this, not like what you posted:
Code:
127.0.0.1       localhost.localdomain localhost
192.168.15.77   prox4m1.proxmox.com prox4m1 pvelocalhost

# The following lines are desirable for IPv6 capable hosts
::1     localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

you only need to touch the second line and replace the IP address, the FQDN and the hostname (leave the pvelocalhost like it is).
 
as noted in the instructions, the hosts file should looke like this, not like what you posted:
Code:
127.0.0.1       localhost.localdomain localhost
192.168.15.77   prox4m1.proxmox.com prox4m1 pvelocalhost

# The following lines are desirable for IPv6 capable hosts
::1     localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

you only need to touch the second line and replace the IP address, the FQDN and the hostname (leave the pvelocalhost like it is).


Ok Thanks, I will try it again in a vm for this time....I went with the build in zfs raid
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!