[SOLVED] Connection refused (595) after Upgrade from Proxmox 6.4 to 7

[SoporteIB]

Hello.
We have gone to update a node of the Cluster, it has two, but after carrying out the process it has given the following error:

Processing triggers for libc-bin (2.28-10+deb10u4) ...
dpkg: dependency problems prevent processing triggers for pve-manager:
pve-manager depends on librados2-perl; however:
Package librados2-perl is not configured yet.

dpkg: error processing package pve-manager (--configure):
dependency problems - leaving triggers unprocessed
Processing triggers for pve-ha-manager (3.1-1) ...
Errors were encountered while processing:
librados2-perl
libpve-u2f-server-perl
pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)

This node appears with the following error and we cannot start the containers, although we can access it via SSH or terminal from the other node.

pveversion -v

Use of uninitialized value $PVE::JSONSchema:VE_TAG_RE in concatenation (.) or string at /usr/share/perl5/PVE/DataCenterConfig.pm line 169.
Use of uninitialized value $PVE::JSONSchema:VE_TAG_RE in concatenation (.) or string at /usr/share/perl5/PVE/DataCenterConfig.pm line 204.
Use of uninitialized value $PVE::JSONSchema:VE_TAG_RE in concatenation (.) or string at /usr/share/perl5/PVE/DataCenterConfig.pm line 204.
Use of uninitialized value $PVE::JSONSchema:VE_TAG_RE in concatenation (.) or string at /usr/share/perl5/PVE/DataCenterConfig.pm line 230.
Use of uninitialized value $PVE::JSONSchema:VE_TAG_RE in concatenation (.) or string at /usr/share/perl5/PVE/DataCenterConfig.pm line 230.
proxmox-ve: 7.4-1 (running kernel: 5.15.158-2-pve)
pve-manager: not correctly installed (running version: 6.4-15/af7986e6)
pve-kernel-5.15: 7.4-15
pve-kernel-5.4: 6.4-20
pve-kernel-5.15.158-2-pve: 5.15.158-2
pve-kernel-5.4.203-1-pve: 5.4.203-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
ceph-fuse: 12.2.11+dfsg1-2.1+deb10u1
corosync: 3.1.5-pve2~bpo10+1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx4
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2~bpo10+1
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.1.0-1
libpve-access-control: 6.4-3
libpve-apiclient-perl: 3.2-2
libpve-common-perl: 6.4-5
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-5
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 1.1.14-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.7.4
pve-cluster: 6.4-1
pve-container: 3.3-6
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-4~bpo11+3
pve-firewall: 4.1-4
pve-firmware: 3.6-6
pve-ha-manager: 3.1-1
pve-i18n: 2.12-1
pve-qemu-kvm: 5.2.0-8
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.2-2
vncterm: 1.6-2
zfsutils-linux: 2.0.7-pve1

 

[cheiss]

Hi,

first, please provide the configured package repositories - best would be the output of tail -n+0 /etc/apt/sources.list; tail -n+0 /etc/apt/sources.list.d/*, in codetags please!.

Also, did you otherwise follow all the instructions at Upgrade from 6.x to 7.0?

Did apt update produce any warnings/errors?

How exactly did you upgrade the node? Via the web UI? If not, did you use apt dist-upgrade, not apt upgrade?

 

[SoporteIB]

Hi,

#deb http://ftp.es.debian.org/debian bullseye main contrib

deb http://ftp.es.debian.org/debian bullseye-updates main contrib

# security updates
deb http://security.debian.org bullseye-security main contrib

deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription

#deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription

From terminal, following this manual https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#Testing_the_Upgrade
I used:
apt update
apt dist-upgrade

 

[cheiss]

#deb http://ftp.es.debian.org/debian bullseye main contrib

Why do you have the main Debian repository commented out? That's not supposed to be like that.

E.g. an example on how the package repositories should look like can be found in our documentation here: Proxmox VE No-Subscription Repository (replacing bookworm with bullseye of course, as you're upgrading to 7.x).

I'd first try adding that back in and trying to run apt update && apt --fix-broken install &&apt dist-upgrade, that may fix things.

 

[SoporteIB]

Why do you have the main Debian repository commented out? That's not supposed to be like that.

E.g. an example on how the package repositories should look like can be found in our documentation here: Proxmox VE No-Subscription Repository (replacing bookworm with bullseye of course, as you're upgrading to 7.x).

I'd first try adding that back in and trying to run apt update && apt --fix-broken install &&apt dist-upgrade, that may fix things.

I was getting an error saying that line 1 was duplicated with line 8 before trying to update, that's why I mentioned it.

I've already configured it and I'm going to try it now with the command you've indicated, I'll let you know. Thanks.

deb http://ftp.debian.org/debian bullseye main contrib
deb http://ftp.debian.org/debian bullseye-updates main contrib

# Proxmox VE pve-no-subscription repository provided by proxmox.com,
# NOT recommended for production use
deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription

# security updates
deb http://security.debian.org/debian-security bullseye-security main contrib

 

[SoporteIB]

Hello
A question, is it possible to repair it and keep it in 6 as it was?
I ask this because I have old containers that are giving me problems in a Proxmox v8 test, I am reviewing it.

 

[SoporteIB]

Why do you have the main Debian repository commented out? That's not supposed to be like that.

E.g. an example on how the package repositories should look like can be found in our documentation here: Proxmox VE No-Subscription Repository (replacing bookworm with bullseye of course, as you're upgrading to 7.x).

I'd first try adding that back in and trying to run apt update && apt --fix-broken install &&apt dist-upgrade, that may fix things.

Perfect, it worked for me, thank you very much. I'm going to update the other node and test that all the containers are working fine.

 

[cheiss]

A question, is it possible to repair it and keep it in 6 as it was?

(Partially) downgrading is not supported. So I'd suggest rather updating & staying on 7.4, which I assume also presents no problems to you (since you mention 8 specifically).