Bookworm installation fails with pve-manager dependency error

vu2swx

New Member
Jun 23, 2023
6
0
1
I am trying to install version 8 on a fresh install of debian 12. I am getting dependency error for pve-manager


Setting up pve-manager (8.0.3) ...
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/multi-user.target.wants/pvescheduler.service
→ /lib/systemd/system/pvescheduler.service.
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/pv
e-guests.service.
Created symlink /etc/systemd/system/multi-user.target.wants/pve-guests.service →
/lib/systemd/system/pve-guests.service.
Backing up lvm.conf before setting pve-manager specific settings..
'/etc/lvm/lvm.conf' -> '/etc/lvm/lvm.conf.bak'
Setting 'global_filter' in /etc/lvm/lvm.conf to prevent zvols from being scanned
:
global_filter=["a|.*|"] => global_filter=["r|/dev/zd.*|"]
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145.
dpkg: error processing package pve-manager (--configure):
installed pve-manager package post-installation script subprocess returned erro
r 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.


I tried this on a second machine with same results
 

Attachments

  • Screenshot from 2023-06-23 16-22-59.png
    Screenshot from 2023-06-23 16-22-59.png
    84.2 KB · Views: 5
Hi,
what is the output of pvecm status and pve7to8?
EDIT: sorry, wrongly assumed it was an upgrade. Can you post the output of
Code:
systemctl status pveproxy.service pvedaemon.service pve-cluster.service
systemctl start pveproxy.service pvedaemon.service pve-cluster.service
?
 
Last edited:
Sure, But after the weekend.

Hi,
what is the output of pvecm status and pve7to8?
EDIT: sorry, wrongly assumed it was an upgrade. Can you post the output of
Code:
systemctl status pveproxy.service pvedaemon.service pve-cluster.service
systemctl start pveproxy.service pvedaemon.service pve-cluster.service
?
 
I think I was running into the same exact issue. I installed Debian 12, then following instructions to install Proxmox on top. However, I skipped some steps :')

Regarding the hosts file I thought I'll think about this later; so it only had default 127.0.1.1 entry.. Well it seems that setting host entry to actual IP-address made the error related to "Could not execute systemctl" go away.

Then I still had some errors from services not starting: "/etc/pve/local/pve-ssl.key: failed to load local private key"
Which I solved by (note this regens other things like SSH keys as well it seems!): pvecm updatecerts --force

Ps. I'm new to using Proxmox so just trying things out as I go along :)
 
  • Like
Reactions: fiona
Please see the status @fiona
Hi,
what is the output of pvecm status and pve7to8?
EDIT: sorry, wrongly assumed it was an upgrade. Can you post the output of
Code:
systemctl status pveproxy.service pvedaemon.service pve-cluster.service
systemctl start pveproxy.service pvedaemon.service pve-cluster.service
?
 

Attachments

  • Screenshot from 2023-06-26 16-23-21.png
    Screenshot from 2023-06-26 16-23-21.png
    125.4 KB · Views: 8
  • Screenshot from 2023-06-26 16-52-50.png
    Screenshot from 2023-06-26 16-52-50.png
    19 KB · Views: 6
So the issue seems to be with the pve-cluster.service. Please post the output of journalctl -xeu pve-cluster.service or the full journal since last boot. That hopefully shows what the actual issue is.
 
Doesn't show the error unfortunately. Please check/share the file resulting with journalctl -b > /tmp/journal.log
 
Code:
Jun 23 16:21:11 debian systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
Jun 23 16:21:11 debian systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
Jun 23 16:21:11 debian pmxcfs[8885]: [main] crit: Unable to get local IP address
Jun 23 16:21:11 debian pmxcfs[8885]: [main] crit: Unable to get local IP address
Jun 23 16:21:11 debian systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Jun 23 16:21:11 debian systemd[1]: pve-cluster.service: Failed with result 'exit-code'

Seem to be related to /etc/hosts

you need to resolve your hostname to the real ip.
if you have any "127.0.1.1 <hosntame>" in this file, remove it.
 
  • Like
Reactions: fiona

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!