[SOLVED] connection refused after pve 9.0 update

[kmw]

to update to PVE 9.0, i changed the proxmox.sources and ceph.sources from pve-test to pve-no-subscription(ceph: no-subscription)and updated.

however, while the first server updated normally, the second server was unable to start the pvedaemon and pveproxy services, resulting in connection refused errors in all functions except the shell. (the problem occurs on the second server, which is configured as a cluster)

how can this issue be resolved? i was planning to reinstall after migration, but i couldn't do it.

+ i tried reinstalling some services, but it seems that other services also fail..

# systemctl --failed\

  UNIT                   LOAD   ACTIVE SUB    DESCRIPTION                           
● 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
● pve-sdn-commit.service loaded failed failed Commit Proxmox VE SDN changes
● pvedaemon.service      loaded failed failed PVE API Daemon
● pveproxy.service       loaded failed failed PVE API Proxy Server
● pvescheduler.service   loaded failed failed Proxmox VE scheduler
● pvestatd.service       loaded failed failed PVE Status Daemon

Legend: 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.

# pveversion -v

proxmox-ve: 9.0.0 (running kernel: 6.14.8-1-pve)
pve-manager: 9.0.3 (running version: 9.0.3/025864202ebb6109)
proxmox-kernel-helper: 9.0.3
proxmox-kernel-6.14.8-1-pve-signed: 6.14.8-1
proxmox-kernel-6.14: 6.14.8-1
proxmox-kernel-6.8.12-12-pve-signed: 6.8.12-12
proxmox-kernel-6.8: 6.8.12-12
proxmox-kernel-6.8.12-11-pve-signed: 6.8.12-11
proxmox-kernel-6.8.12-10-pve-signed: 6.8.12-10
proxmox-kernel-6.8.12-9-pve-signed: 6.8.12-9
proxmox-kernel-6.8.12-8-pve: 6.8.12-8
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
ceph-fuse: 19.2.2-pve5
corosync: 3.1.9-pve2
criu: 4.1.1-1
ifupdown2: 3.3.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.3
libpve-apiclient-perl: 3.4.0
libpve-cluster-api-perl: 9.0.6
libpve-cluster-perl: 9.0.6
libpve-common-perl: 9.0.9
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.3
libpve-network-perl: 1.1.0
libpve-rs-perl: 0.10.7
libpve-storage-perl: 9.0.13
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2
lxc-pve: 6.0.4-2
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.0.9-1
proxmox-backup-file-restore: 4.0.9-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.1.1
proxmox-kernel-helper: 9.0.3
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.0
proxmox-widget-toolkit: 5.0.4
pve-cluster: 9.0.6
pve-container: 6.0.9
pve-docs: 9.0.7
pve-edk2-firmware: 4.2025.02-4
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.3
pve-firmware: 3.16-3
pve-ha-manager: 5.0.4
pve-i18n: 3.5.2
pve-qemu-kvm: 10.0.2-4
pve-xtermjs: 5.5.0-2
qemu-server: 9.0.16
smartmontools: 7.4-pve1
spiceterm: 3.4.0
swtpm: 0.8.0+pve2
vncterm: 1.9.0
zfsutils-linux: 2.3.3-pve1

 

[bbgeek17]

There is likely a lot of useful data in the system's log/journal:
journalctl -b0

You may also get some info from "systemctl status [service-name]"
You can slo zoom in on a particular service: journalctl -xe -u <service-name>

Since you have a system-wide failure, the cause is likely cluster-services related, if you have any. Regardless, you need to dive into the logs.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[kmw]

There is likely a lot of useful data in the system's log/journal:
journalctl -b0

You may also get some info from "systemctl status [service-name]"
You can slo zoom in on a particular service: journalctl -xe -u <service-name>

Since you have a system-wide failure, the cause is likely cluster-services related, if you have any. Regardless, you need to dive into the logs.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

after trying various things, i solved the problem by reinstalling the package
i guess there was an error while updating

 

[klx]

In the same boat, just updated the packages, I THOUGHT the install went well, lost access to node, I have ssh access, but no GUI been working on this for a couple of hours, decided to reinstall version 8..not sure what happened..Lenovo m710q a bunch of packages failed to start even after a forced update and a crap ton of help from the AI..