PVE4 Beta Install Failed

A

auser

Renowned Member
Jul 17, 2014
37
7
73
Hi there.
First off - I have been succesfully using ProxmoxVE for years and just love it.
So congratulations to all of you who have worked so hard to make it so great. :-)

I decided to give ProxmoxVE4 Beta a try on my test server.
I need to have control of partitioning so installed Debian8 from DVD.

On my third attempt I had a minimal install that I can ssh into without Desktop or network-manager.

I followed the wiki instructions:
"Install Proxmox VE on Debian Jessie"
http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Jessie

I am stuck at a point where stuff won't install and the errors tell me that is not configured correctly.


Code: 
root@amdx4:~# apt-get dist-upgrade | tee apt-get_dist-upgrade3
Reading package lists...
Building dependency tree...
Reading state information...
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-14) ...
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.
...

Code: 
root@amdx4:~# systemctl status pve-cluster.service
● pve-cluster.service - The Proxmox VE cluster filesystem
   Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled)
   Active: failed (Result: exit-code) since Wed 2015-08-05 15:39:13 BST; 38s ago
  Process: 505 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=255)

Aug 05 15:39:13 amdx4 pmxcfs[505]: [main] crit: Unable to get local IP address
Aug 05 15:39:13 amdx4 pmxcfs[505]: [main] crit: Unable to get local IP address
Aug 05 15:39:13 amdx4 systemd[1]: pve-cluster.service: control process exited, code=exited status=255
Aug 05 15:39:13 amdx4 systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Aug 05 15:39:13 amdx4 systemd[1]: Unit pve-cluster.service entered failed state.
root@amdx4:~#

Code: 
root@amdx4:~/admin# journalctl -xn                      
-- Logs begin at Wed 2015-08-05 15:39:07 BST, end at Wed 2015-08-05 15:40:13 BST. --
Aug 05 15:40:13 amdx4 systemd-timesyncd[443]: interval/delta/delay/jitter/drift 64s/-0.004s/0.050s/0.002s/+465ppm
Aug 05 15:40:13 amdx4 dhclient[504]: No DHCPOFFERS received.
Aug 05 15:40:13 amdx4 dhclient[504]: No working leases in persistent database - sleeping.
Aug 05 15:40:13 amdx4 ifup[490]: No DHCPOFFERS received.
Aug 05 15:40:13 amdx4 ifup[490]: No working leases in persistent database - sleeping.
Aug 05 15:40:13 amdx4 sshd[700]: Received SIGHUP; restarting.
Aug 05 15:40:13 amdx4 sshd[700]: Server listening on 0.0.0.0 port 22.
Aug 05 15:40:13 amdx4 sshd[700]: Server listening on :: port 22.
Aug 05 15:40:13 amdx4 postfix/master[874]: reload -- version 2.11.3, configuration /etc/postfix
Aug 05 15:40:13 amdx4 postfix[1040]: Reloading Postfix configuration...done.
root@amdx4:~/admin#

Code: 
root@amdx4:~/admin# dig amdx4

; <<>> DiG 9.9.5-9+deb8u2-Debian <<>> amdx4
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24763
;; flags: qr aa rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;amdx4.                         IN      A

;; ANSWER SECTION:
amdx4.                  0       IN      A       192.168.5.123

;; Query time: 2 msec
;; SERVER: 192.168.5.1#53(192.168.5.1)
;; WHEN: Wed Aug 05 15:40:48 BST 2015
;; MSG SIZE  rcvd: 39

root@amdx4:~/admin# ping amdx4
PING amdx4 (127.0.1.1) 56(84) bytes of data.
64 bytes from amdx4 (127.0.1.1): icmp_seq=1 ttl=64 time=0.033 ms
64 bytes from amdx4 (127.0.1.1): icmp_seq=2 ttl=64 time=0.027 ms
^C
--- amdx4 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.027/0.030/0.033/0.003 ms
root@amdx4:~/admin#

Can anyone help me with this?

(I do not have an immediate need for cluster-manager as probably I will not have further PXVE4 instances to cluster with, until I have lived with the Beta for at least a few weeks. )

thankyou all
Colin
 
Code: 
root@amdx4:~/admin# ifconfig 
eth0      Link encap:Ethernet  HWaddr 00:21:85:9d:f1:f7  
          inet addr:192.168.5.123  Bcast:192.168.15.255  Mask:255.255.240.0
          inet6 addr: fe80::221:85ff:fe9d:f1f7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:620 errors:0 dropped:0 overruns:0 frame:0
          TX packets:436 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:60190 (58.7 KiB)  TX bytes:54880 (53.5 KiB)

eth1      Link encap:Ethernet  HWaddr 00:1c:f0:5b:63:3f  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1440 (1.4 KiB)  TX bytes:1440 (1.4 KiB)

root@amdx4:~/admin#

One potential wrinkle:
configuring eth0 with static address details did not seem to want to work
just a thought:
maybe systemd is letting Jessie boot up before DHCP details have arrived ?

But even in that case I would expect cluster-manager to start when called explicitly on CLI, via ssh.
Code: 
root@amdx4:~/admin# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface

allow-hotplug eth0
iface eth0 inet dhcp
#iface eth0 inet static
#address 192.168.5.123          # IP address
#network 192.168.5.0            # network address
#netmask 255.255.240.0          # subnet mask
#broadcast 192.168.15.255       # broadcast address
#gateway 192.168.5.1            # default gateway
#dns-nameservers 192.168.5.118  # name server


allow-hotplug eth1
iface eth1 inet dhcp
root@amdx4:~/admin#
 
this is part of my Error
---****************-----
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.
===========================================================


The Last Part of ERRORS

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
================================================================
 
You must ensure that you have networking working properly.

So I would suggest that you check that out first.

Check that you can reach all necessary services e.g. gateway, DNS
Check that you have put any hostnames into your /etc/hosts

As I recall, If you follow the wiki, it also warns you what NOT to do.
http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Jessie

i.e. Do not install
network-manager or resolvconf or rdnssd

see also '[Solved] PVE 4.0 DNS settings disapearing'
https://forum.proxmox.com/threads/solved-pve-4-0-dns-settings-disapearing.24007/
 
  • Like
Reactions: hamada omara
auser said:
You must ensure that you have networking working properly.

So I would suggest that you check that out first.

Check that you can reach all necessary services e.g. gateway, DNS
Check that you have put any hostnames into your /etc/hosts

As I recall, If you follow the wiki, it also warns you what NOT to do.
http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Jessie

i.e. Do not install
network-manager or resolvconf or rdnssd

see also '[Solved] PVE 4.0 DNS settings disapearing'
https://forum.proxmox.com/threads/solved-pve-4-0-dns-settings-disapearing.24007/
Click to expand...
I will try install it again
 
You must log in or register to reply here.
Top Bottom