I've been updating pve 7 to 8 via ssh (unfortunately without screen/tmux).
At the end stage (the one with package configuration and dialogs) the ssh connection broke.
After some time seeing no CPU activity on apt I killed its process and did dpkg --configure -a
Until the reboot the new PVE 8.4 web interface and lxc containers did run.
After the reboot I am experiencing the following:
Any ideas how to go on fixing that?
At the end stage (the one with package configuration and dialogs) the ssh connection broke.
After some time seeing no CPU activity on apt I killed its process and did dpkg --configure -a
Until the reboot the new PVE 8.4 web interface and lxc containers did run.
After the reboot I am experiencing the following:
Code:
# systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● pve-cluster.service loaded failed failed The Proxmox VE cluster filesystem
● pve-firewall.service loaded failed failed Proxmox VE firewall
● pve-guests.service loaded failed failed PVE guests
● pve-ha-crm.service loaded failed failed PVE Cluster HA Resource Manager Daemon
● pve-ha-lrm.service loaded failed failed PVE Local HA Resource Manager Daemon
● pvescheduler.service loaded failed failed Proxmox VE scheduler
● pvestatd.service loaded failed failed PVE Status Daemon
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
7 loaded units listed.
Code:
# dpkg-reconfigure pve-cluster
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145.
# sed -n '145p' /usr/bin/deb-systemd-invoke
system('systemctl', '--quiet', @instance_args, $action, @start_units) == 0 or die("Could not execute systemctl: $!");
Any ideas how to go on fixing that?