[SOLVED] Failed to start Proxmox VE firewall.

[devonblzx]

Just installed from Debian (due to needing a custom partitioning scheme). I installed a similar server last week without issue but ran into this error installing on this system.

Upon trying to install proxmox-ve packages, pve-firewall fails to configure because it can't be started.

pve-firewall/stable,now 3.0-5 amd64 [installed]

In the logs, it cannot load the ACL:

Mar 27 19:38:56 w100 pve-firewall[3506]: ipcc_send_rec[1] failed: Connection refused
Mar 27 19:38:56 w100 pve-firewall[3506]: ipcc_send_rec[2] failed: Connection refused
Mar 27 19:38:56 w100 pve-firewall[3506]: ipcc_send_rec[2] failed: Connection refused
Mar 27 19:38:56 w100 pve-firewall[3506]: ipcc_send_rec[3] failed: Connection refused
Mar 27 19:38:56 w100 pve-firewall[3506]: ipcc_send_rec[3] failed: Connection refused
Mar 27 19:38:56 w100 pve-firewall[3506]: Unable to load access control list: Connection refused
Mar 27 19:38:56 w100 systemd[1]: pve-firewall.service: Control process exited, code=exited status=111
Mar 27 19:38:56 w100 systemd[1]: Failed to start Proxmox VE firewall

Any ideas?

---------------

I noticed /etc/pve is empty for some reason too. Trying to reboot, uninstall proxmox-ve (with autoremove) and reinstalling leads to the same issues. pve-firewall configuration fails and results in the rest failing:

Setting up pve-firewall (3.0-5) ...
Job for pve-firewall.service failed because the control process exited with error code.
See "systemctl status pve-firewall.service" and "journalctl -xe" for details.
dpkg: error processing package pve-firewall (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of qemu-server:
 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 pve-firewall; however:
  Package pve-firewall is not configured yet.
 pve-manager depends on qemu-server (>= 1.1-1); however:
  Package qemu-server is not configured yet.

dpkg: error processing package pve-manager (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-ha-manager:
 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 pve-container:
 pve-container depends on pve-ha-manager; however:
  Package pve-ha-manager is not configured yet.
 pve-container
E: Sub-process /usr/bin/dpkg returned an error code (1)

 

[Alwin]

Do you have a static network config and is the interface up? If 'pvereport' works, then you could do easily a comparison of your servers.

 

[devonblzx]

Do you have a static network config and is the interface up? If 'pvereport' works, then you could do easily a comparison of your servers.

pvereport is not available. It is a static network config and the interface is up (as I'm able to download the packages via apt):

# The primary network interface
allow-hotplug enp10s0f0
iface enp10s0f0 inet static
        address ***.***.***.13
        netmask 255.255.255.0
        gateway ***.***.***.1

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp10s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:25:90:18:9e:d0 brd ff:ff:ff:ff:ff:ff
    inet ***.***.***.13/24 brd ***.***.***.255 scope global enp10s0f0
       valid_lft forever preferred_lft forever
    inet6 fe80::225:90ff:fe18:9ed0/64 scope link
       valid_lft forever preferred_lft forever
3: enp10s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:25:90:18:9e:d1 brd ff:ff:ff:ff:ff:ff

 

[Alwin]

Are there pve entries in the /etc/hosts and does the hostname correspond to the host in the hosts file?

127.0.0.1 localhost.localdomain localhost
192.168.1.2 pve1.proxmox.com pve1 pvelocalhost

 

[devonblzx]

Are there pve entries in the /etc/host and does the hostname correspond to the host in the hosts file?

192.168.1.2 pve1.proxmox.com pve1 pvelocalhost

That solved it. Thank you!