-
#1
Hi!
I’m trying to install Proxmox over Debian stretch and stuck up with the problem.
After apt install proxmox-ve postfix open-iscsi I got the dependencies error:
Настраивается пакет 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: ошибка при обработке пакета pve-firewall (—configure):
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
dpkg: зависимости пакетов не позволяют настроить пакет qemu-server:
qemu-server зависит от pve-firewall, однако:
Пакет pve-firewall пока не настроен.
dpkg: ошибка при обработке пакета qemu-server (—configure):
проблемы зависимостей — оставляем не настроенным
dpkg: зависимости пакетов не позволяют настроить пакет proxmox-ve:
proxmox-ve зависит от qemu-server, однако:
Пакет qemu-server пока не настроен.
dpkg: ошибка при обработке пакета proxmox-ve (—configure):
проблемы зависимостей — оставляем не настроенным
dpkg: зависимости пакетов не позволяют настроить пакет pve-manager:
pve-manager зависит от pve-firewall, однако:
Пакет pve-firewall пока не настроен.
pve-manager зависит от qemu-server (>= 1.1-1), однако:
Пакет qemu-server пока не настроен.
dpkg: ошибка при обработке пакета pve-manager (—configure):
проблемы зависимостей — оставляем не настроенным
dpkg: зависимости пакетов не позволяют настроить пакет pve-ha-manager:
pve-ha-manager зависит от qemu-server, однако:
Пакет qemu-server пока не настроен.
dpkg: ошибка при обработке пакета pve-ha-manager (—configure):
проблемы зависимостей — оставляем не настроенным
dpkg: зависимости пакетов не позволяют настроить пакет pve-container:
pve-container зависит от pve-ha-manager, однако:
Пакет pve-ha-manager пока не настроен.
dpkg: ошибка при обработке пакета pve-container (—configure):
проблемы зависимостей — оставляем не настроенным
При обработке следующих пакетов произошли ошибки:
pve-firewall
qemu-server
proxmox-ve
pve-manager
pve-ha-manager
pve-container
dietmar
Proxmox Staff Member
Staff member
-
#2
So what is the output of:
# systemctl status pve-firewall.service
-
#3
root@cluster:/home/anton# systemctl status pve-firewall.service
● pve-firewall.service — Proxmox VE firewall
Loaded: loaded (/lib/systemd/system/pve-firewall.service; disabled; vendor pr
Active: failed (Result: exit-code) since Sun 2018-01-28 22:48:26 MSK; 20h ago
Process: 3778 ExecStart=/usr/sbin/pve-firewall start (code=exited, status=111)
CPU: 856ms
янв 28 22:48:26 cluster pve-firewall[3778]: ipcc_send_rec[1] failed: Connection
янв 28 22:48:26 cluster pve-firewall[3778]: ipcc_send_rec[2] failed: Connection
янв 28 22:48:26 cluster pve-firewall[3778]: ipcc_send_rec[2] failed: Connection
янв 28 22:48:26 cluster pve-firewall[3778]: ipcc_send_rec[3] failed: Connection
янв 28 22:48:26 cluster pve-firewall[3778]: ipcc_send_rec[3] failed: Connection
янв 28 22:48:26 cluster pve-firewall[3778]: Unable to load access control list:
янв 28 22:48:26 cluster systemd[1]: pve-firewall.service: Control process exited
янв 28 22:48:26 cluster systemd[1]: Failed to start Proxmox VE firewall.
янв 28 22:48:26 cluster systemd[1]: pve-firewall.service: Unit entered failed st
янв 28 22:48:26 cluster systemd[1]: pve-firewall.service: Failed with result ‘ex
lines 1-16/16 (END)
-
#4
So is there a solution to that?
-
#5
Hello! Please show your
file. firewall-pve may be unable to configure itself if there is a host configuration issue
-
#6
Quite right, Gleb. The hostname in hostnamectl command and the one in /etc/hosts must match to avoid the installation errors described in OP’s post.
Setting the hostname in Debian 9 Stretch:
Code:
hostnamectl set-hostname [your-hostname]To check your hostname:
or just:
Last edited: Feb 23, 2018
0
1
Обычный хост, baremetal, поставил debian 9, настроил сеть, свой обычный файрволл начал ставить пакеты proxmox согласно доке https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Stretch Словил в конце
ipcc_send_rec[1] failed: Connection refused ipcc_send_rec[2] failed: Connection refused ipcc_send_rec[3] failed: Connection refused Unable to load access control list: Connection refused Created symlink /etc/systemd/system/multi-user.target.wants/pvedaemon.service → /lib/systemd/system/pvedaemon.service. Created symlink /etc/systemd/system/multi-user.target.wants/pveproxy.service → /lib/systemd/system/pveproxy.service. Created symlink /etc/systemd/system/multi-user.target.wants/spiceproxy.service → /lib/systemd/system/spiceproxy.service. Created symlink /etc/systemd/system/multi-user.target.wants/pvestatd.service → /lib/systemd/system/pvestatd.service. Created symlink /etc/systemd/system/getty.target.wants/pvebanner.service → /lib/systemd/system/pvebanner.service. Created symlink /etc/systemd/system/timers.target.wants/pvesr.timer → /lib/systemd/system/pvesr.timer. Created symlink /etc/systemd/system/timers.target.wants/pve-daily-update.timer → /lib/systemd/system/pve-daily-update.timer. Created symlink /etc/systemd/system/sysinit.target.wants/pvenetcommit.service → /lib/systemd/system/pvenetcommit.service. Created symlink /etc/systemd/system/pve-manager.service → /lib/systemd/system/pve-guests.service. Created symlink /etc/systemd/system/multi-user.target.wants/pve-guests.service → /lib/systemd/system/pve-guests.service. Job for pvestatd.service failed because the control process exited with error code. See «systemctl status pvestatd.service» and «journalctl -xe» for details. pvestatd.service couldn't start. dpkg: error processing package pve-manager (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of proxmox-ve: proxmox-ve depends on pve-manager; however: Package pve-manager is not configured yet. dpkg: error processing package proxmox-ve (--configure): dependency problems - leaving unconfigured Processing triggers for initramfs-tools (0.130) ... update-initramfs: Generating /boot/initrd.img-4.15.18-5-pve Processing triggers for libc-bin (2.24-11+deb9u3) ... Processing triggers for systemd (232-25+deb9u4) ... Processing triggers for rsyslog (8.24.0-1) ... Processing triggers for pve-ha-manager (2.0-5) ... Errors were encountered while processing: pve-manager proxmox-ve E: Sub-process /usr/bin/dpkg returned an error code (1)
я так понимаю, что мой обычный файрволл сработал…
Короче, не получается исправить установку пакета
pve-manager
Есть предложения?
I reciently install proxmox on Debian and the install failed. Here is the error:
apt-get update Hit:1 http://download.proxmox.com/debian/pve buster InRelease Hit:2 http://security.debian.org/debian-security buster/updates InRelease Hit:3 http://deb.debian.org/debian buster InRelease Hit:4 http://deb.debian.org/debian buster-updates InRelease Reading package lists... Done root@px1:~# apt 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. 2 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-manager (6.3-3) ... Job for pveproxy.service failed because the control process exited with error code. See "systemctl status pveproxy.service" and "journalctl -xe" for details. dpkg: error processing package pve-manager (--configure): installed pve-manager package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of proxmox-ve: proxmox-ve depends on pve-manager; however: Package pve-manager is not configured yet. dpkg: error processing package proxmox-ve (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: pve-manager proxmox-ve E: Sub-process /usr/bin/dpkg returned an error code (1)
The resolution was to make sure the network was set to a static IP:
# The primary network interface
allow-hotplug enp4s0
iface enp4s0 inet static
address 192.168.0.16
netmask 255.255.255.0
gateway 192.168.0.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 1.1.1.1 1.0.0.1
dns-search geekdecoder.com
The second issue was to make sure there was a host entry. Comment out the 127.0.0.1 and make sure to use the full host.domain host as below. Leaving out the end “px1” caused the issue.
#127.0.1.1 px1.geekdecoder.com px1 192.168.0.16 px1.geekdecoder.com px1
Job for pvestatd.service failed because the control process exited with error code.
See "systemctl status pvestatd.service" and "journalctl -xe" for details.
dpkg: error processing package pve-manager (--configure):
installed pve-manager package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve:
proxmox-ve depends on pve-manager; however:
Package pve-manager is not configured yet.
dpkg: error processing package proxmox-ve (--configure):
dependency problems - leaving unconfigured
Processing triggers for dbus (1.12.20-2) ...
Processing triggers for initramfs-tools (0.140) ...
Processing triggers for libglib2.0-0:arm64 (2.66.8-1) ...
Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u3) ...
Processing triggers for rsyslog (8.2102.0-2+deb11u1) ...
Processing triggers for man-db (2.9.4-2) ...
Setting up zfs-zed (2.1.5-1~bpo11~rpt1) ...
Created symlink /etc/systemd/system/zed.service → /lib/systemd/system/zfs-zed.service.
Created symlink /etc/systemd/system/zfs.target.wants/zfs-zed.service → /lib/systemd/system/zfs-zed.service.
Setting up glib-networking:arm64 (2.66.0-2) ...
Setting up libsoup2.4-1:arm64 (2.72.0-2) ...
Setting up gstreamer1.0-plugins-good:arm64 (1.18.4-2+~rpt1) ...
Processing triggers for libgdk-pixbuf-2.0-0:arm64 (2.42.2+dfsg-1) ...
Processing triggers for pve-ha-manager (3.3-4) ...
Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u3) ...
Errors were encountered while processing:
pve-manager
proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)
Pull request incoming once I finalize testing.
Go to Proxmox
Problem when updating proxmox
Good day to all,
It seems I can’t update properly as I get the following error when doing apt update && apt dist-upgrade
root@enode304:~# apt update && apt dist-upgrade Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB] Hit:2 http://ftp.debian.org/debian buster InRelease Hit:3 http://ftp.debian.org/debian buster-updates InRelease Hit:4 http://download.proxmox.com/debian/pve buster InRelease Fetched 65.4 kB in 0s (168 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. 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. 3 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-kernel-5.4.114-1-pve (5.4.114-1) ... Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.4.114-1-pve /boot/vmlinuz-5.4.114-1-pve run-parts: executing /etc/kernel/postinst.d/dkms 5.4.114-1-pve /boot/vmlinuz-5.4.114-1-pve run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.4.114-1-pve /boot/vmlinuz-5.4.114-1-pve update-initramfs: Generating /boot/initrd.img-5.4.114-1-pve run-parts: executing /etc/kernel/postinst.d/proxmox-auto-removal 5.4.114-1-pve /boot/vmlinuz-5.4.114-1-pve run-parts: executing /etc/kernel/postinst.d/zz-proxmox-boot 5.4.114-1-pve /boot/vmlinuz-5.4.114-1-pve Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace.. No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync. run-parts: executing /etc/kernel/postinst.d/zz-update-grub 5.4.114-1-pve /boot/vmlinuz-5.4.114-1-pve /usr/sbin/grub-mkconfig: 1: /etc/default/grub: If: not found run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 127 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/pve-kernel-5.4.114-1-pve.postinst line 19. dpkg: error processing package pve-kernel-5.4.114-1-pve (--configure): installed pve-kernel-5.4.114-1-pve package post-installation script subprocess returned error exit status 2 dpkg: dependency problems prevent configuration of pve-kernel-5.4: pve-kernel-5.4 depends on pve-kernel-5.4.114-1-pve; however: Package pve-kernel-5.4.114-1-pve is not configured yet. dpkg: error processing package pve-kernel-5.4 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of proxmox-ve: proxmox-ve depends on pve-kernel-5.4; however: Package pve-kernel-5.4 is not configured yet. dpkg: error processing package proxmox-ve (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: pve-kernel-5.4.114-1-pve pve-kernel-5.4 proxmox-ve E: Sub-process /usr/bin/dpkg returned an error code (1)
This is my sources.list :
deb http://ftp.debian.org/debian buster main contrib deb http://ftp.debian.org/debian buster-updates main contrib # PVE pve-no-subscription repository provided by proxmox.com, # NOT recommended for production use deb http://download.proxmox.com/debian/pve buster pve-no-subscription # security updates deb http://security.debian.org/debian-security buster/updates main contrib
Does anyone have an idea how to solve this ?