Proxmox Debian Install failed

Chris Welber

New Member
Mar 14, 2016
28
2
3
59
I tried to build a Proxmox from a Debian base system instead of installing from the ISO using this article:
https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Jessie

When I got the command which actually installs Proxmox:
apt-get install proxmox-ve ntp ssh postfix ksm-control-daemon open-iscsi systemd-sysv

It fails. The output from the command is listed below. Any help is greatly appreciated from the Proxmox guru's.


apt-get install proxmox-ve ntp ssh postfix ksm-control-daemon open-iscsi systemd-sysv
Reading package lists... Done
Building dependency tree
Reading state information... Done
ntp is already the newest version.
open-iscsi is already the newest version.
ssh is already the newest version.
postfix is already the newest version.
systemd-sysv is already the newest version.
proxmox-ve is already the newest version.
ksm-control-daemon is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
9 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up pve-cluster (4.0-43) ...
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
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 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
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.

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.

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.

dpkg: error processing package qemu-server (--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-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.

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
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)
 
Have you installed and rebootet the PVE kernel?

Why haven't you included the error messages reported? Please run

Code:
journalctl -xn
 
After running the command:
apt-get install proxmox-ve ntp ssh postfix ksm-control-daemon open-iscsi systemd-sysv

On a new Jessie build based on the above article, here is the is the output from the command:

journalctl -xn
-- Logs begin at Tue 2016-07-19 16:22:42 EDT, end at Wed 2016-07-20 08:01:28 EDT. --
Jul 20 07:59:49 pve04 su[7361]: + /dev/pts/1 labuser:root
Jul 20 07:59:49 pve04 su[7361]: pam_unix(su:session): session opened for user root by labuser(uid=1000)
Jul 20 08:01:28 pve04 systemd-sysv-generator[7407]: Ignoring creation of an alias umountiscsi.service for itself
Jul 20 08:01:28 pve04 systemd-sysv-generator[7437]: Ignoring creation of an alias umountiscsi.service for itself
Jul 20 08:01:28 pve04 systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
Jul 20 08:01:28 pve04 pmxcfs[7446]: [main] crit: Unable to get local IP address
Jul 20 08:01:28 pve04 pmxcfs[7446]: [main] crit: Unable to get local IP address
Jul 20 08:01:28 pve04 systemd[1]: pve-cluster.service: control process exited, code=exited status=255
Jul 20 08:01:28 pve04 systemd[1]: Failed to start The Proxmox VE cluster filesystem.
-- Subject: Unit pve-cluster.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit pve-cluster.service has failed.
--
-- The result is failed.
Jul 20 08:01:28 pve04 systemd[1]: Unit pve-cluster.service entered failed state.
root@pve04:~#
 
Your message

Code:
Unable to get local IP address

suggests, that you have something wrong with your /etc/hosts. Please check with the documentation you linked. There has to be pvelocalhost. Please post your /etc/hosts if your this the file is correct.
 

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!