Hallo,
ich habe in den letzten zwei Jahren mehrere PVE-6-zu-7 Upgrades durchgeführt, bisher ohne größere Probleme,
aber jetzt ging bei einem entfernt stehendem Single-Server (kein Cluster) leider etwas schief.
Es lief vorher PVE 6.4.xx - Debian Buster
Da hatte ich noch mal mit apt update den letzten Stand hergestellt.
Da kam zuerst eine Fehlermeldung wegen einem veralteten Repository-Eintrag zu Sury - habe ich entfernt.
Update lief durch.
Danach dann Repositories von buster auf bullseye geändert
apt update - okay
! Habe aber später entdeckt, dass ich da bei Security Updates einen veralteten Debian Pfad ftp.debian.org statt deb.debian.org drin hatte.
pve6to7
- WARN: 2 running guests
- FAIL: resolved node IP xxx not configured or active for 'proxmox'
Eine VM runtergefahren - einen Container laufen gelassen
Wegen node IP hatte ich geschaut, aber keinen Fehler in den IP und PVE Configs gefunden
und nach Suche im Forum mit nur dieser Fehlermeldung gelesen dass man das Upgrade wagen kann.
apt dist-upgrade lief bis 55% - dann blieb Terminal-Anzeige lange dort hängen
und dann konnte man nicht mehr auf Proxmox GUI und Konsole von außen zugreifen.
Der Container lief weiter sauber - war erreichbar.
Jemand vor Ort konnte sich direkt am Server einloggen.
Dateien wie interfaces hosts .. wurden geprüft und waren unverändert und korrekt.
debian_version zeigte schon 11.11 an
pveversion zeigte pve-manager/7.4-19/f98bf8d4 (running kernel: 5.4.203-1-pve)
Hatten dann erstmal nichts mehr am System gemacht,
Am nächsten Tag ging auf einmal wieder der Zugriff auf die Proxmox GUI, aber das Login scheiterte.
SSH Zugriff ging aber wieder.
Und die vorher heruntergefahrene VM lief auch wieder, wie nach einem Neustart.
Aber laut uptime gab es keinen reboot.
Jetzt hängt das System im Upgrade Status fest.
Hatte jetzt versucht das Update/Upgrade neu anzustoßen / weiterlaufen zu lassen, aber hänge da fest.
Unten die Fehlermeldungen von:
pve6to7 -full
pveversion -v
apt update
apt upgrade
apt --fix-broken install
---------------------------------------------------------------------------------------------------------------------
aktuelle Statusmeldungen:
pve6to7 -full
root@proxmox:~# pve6to7 -full
= CHECKING VERSION INFORMATION FOR PVE PACKAGES =
Checking for package updates..
PASS: all packages uptodate
Checking proxmox-ve package version..
PASS: already upgraded to Proxmox VE 7
WARN: Proxmox VE 7 got superseeded by Proxmox VE 8.
Did you mean to use the pve7to8 checker script?
Checking running kernel version..
WARN: unexpected running and installed kernel '5.4.203-1-pve'.
= CHECKING CLUSTER HEALTH/SETTINGS =
SKIP: standalone node.
= CHECKING HYPER-CONVERGED CEPH STATUS =
SKIP: no hyper-converged ceph setup detected!
= CHECKING CONFIGURED STORAGES =
PASS: storage 'TEMP' enabled and active.
PASS: storage 'local' enabled and active.
PASS: storage 'local-lvm' enabled and active.
= MISCELLANEOUS CHECKS =
INFO: Checking common daemon services..
PASS: systemd unit 'pveproxy.service' is in state 'active'
PASS: systemd unit 'pvedaemon.service' is in state 'active'
PASS: systemd unit 'pvestatd.service' is in state 'active'
INFO: Checking for running guests..
WARN: 2 running guest(s) detected - consider migrating or stopping them.
INFO: Checking if the local node's hostname 'proxmox' is resolvable..
INFO: Checking if resolved IP is configured on local node..
FAIL: Resolved node IP '172.18.1.175' not configured or active for 'proxmox'
INFO: Check node certificate's RSA key size
PASS: Certificate 'pve-root-ca.pem' passed Debian Busters security level for TLS connections (4096 >= 2048)
PASS: Certificate 'pve-ssl.pem' passed Debian Busters security level for TLS connections (2048 >= 2048)
INFO: Checking backup retention settings..
INFO: storage 'local' - no backup retention settings defined - by default, PVE 7.x will no longer keep only the last backup, but all backups
WARN: storage 'TEMP' - parameter 'maxfiles' is deprecated with PVE 7.x and will be removed in a future version, use 'prune-backups' instead.
INFO: checking CIFS credential location..
PASS: no CIFS credentials at outdated location found.
INFO: Checking custom roles for pool permissions..
INFO: Checking node and guest description/note legnth..
PASS: All node config descriptions fit in the new limit of 64 KiB
PASS: All guest config descriptions fit in the new limit of 8 KiB
INFO: Checking container configs for deprecated lxc.cgroup entries
PASS: No legacy 'lxc.cgroup' keys found.
INFO: Checking storage content type configuration..
PASS: no problems found
INFO: Checking if the suite for the Debian security repository is correct..
PASS: already using 'bullseye-security'
= SUMMARY =
TOTAL: 23
PASSED: 16
SKIPPED: 2
WARNINGS: 4
FAILURES: 1
ATTENTION: Please check the output for detailed information!
Try to solve the problems one at a time and then run this checklist tool again.
--------------------------------------------------------------------------------------------------------------------------
pveversion -v
root@proxmox:~# pveversion -v
proxmox-ve: not correctly installed (running kernel: 5.4.203-1-pve)
pve-manager: not correctly installed (running version: 7.4-19/f98bf8d4)
pve-kernel-5.4: 6.4-20
pve-kernel-5.4.203-1-pve: 5.4.203-1
pve-kernel-5.4.157-1-pve: 5.4.157-1
pve-kernel-4.15: 5.4-19
pve-kernel-4.15.18-30-pve: 4.15.18-58
pve-kernel-4.15.18-10-pve: 4.15.18-32
ceph-fuse: not correctly installed
corosync: not correctly installed
criu: not correctly installed
glusterfs-client: not correctly installed
ifupdown: not correctly installed
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: not correctly installed
libproxmox-acme-perl: not correctly installed
libproxmox-backup-qemu0: not correctly installed
libproxmox-rs-perl: not correctly installed
libpve-access-control: not correctly installed
libpve-apiclient-perl: not correctly installed
libpve-common-perl: not correctly installed
libpve-guest-common-perl: not correctly installed
libpve-http-server-perl: not correctly installed
libpve-rs-perl: not correctly installed
libpve-storage-perl: not correctly installed
libqb0: 1.0.5-1
libspice-server1: not correctly installed
lvm2: not correctly installed
lxc-pve: not correctly installed
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: not correctly installed
proxmox-backup-file-restore: not correctly installed
proxmox-kernel-helper: not correctly installed
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: not correctly installed
proxmox-widget-toolkit: 3.7.4
pve-cluster: not correctly installed
pve-container: not correctly installed
pve-docs: not correctly installed
pve-edk2-firmware: not correctly installed
pve-firewall: not correctly installed
pve-firmware: 3.6-6
pve-ha-manager: not correctly installed
pve-i18n: 2.12-1
pve-qemu-kvm: not correctly installed
pve-xtermjs: 4.16.0-2
qemu-server: not correctly installed
smartmontools: 7.2-pve3
spiceterm: not correctly installed
swtpm: not correctly installed
vncterm: 1.7-1
zfsutils-linux: not correctly installed
------------------------------------------------------------------------------------------------------------
apt update
root@proxmox:~# apt update
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Hit:4 http://download.proxmox.com/debian/pve bullseye InRelease
Fetched 44.1 kB in 1s (51.6 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
--------------------------------------------------------------------------------------------------------------
apt upgrade
root@proxmox:~# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
487 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
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
Setting up libssl1.1:amd64 (1.1.1w-0+deb11u2) ...
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
dpkg: error processing package libssl1.1:amd64 (--configure):
installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of libkrb5-3:amd64:
libkrb5-3:amd64 depends on libssl1.1 (>= 1.1.0); however:
Package libssl1.1:amd64 is not configured yet.
dpkg: error processing package libkrb5-3:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libgssapi-krb5-2:amd64:
libgssapi-krb5-2:amd64 depends on libkrb5-3 (= 1.18.3-6+deb11u5); however:
Package libkrb5-3:amd64 is not configured yet.
dpkg: error processing package libgssapi-krb5-2:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libtirpc3:amd64:
libtirpc3:amd64 depends on libgssapi-krb5-2 (>= 1.17); however:
Package libgssapi-krb5-2:amd64 is not configured yet.
dpkg: error processing package libtirpc3:amd64 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
libssl1.1:amd64
libkrb5-3:amd64
libgssapi-krb5-2:amd64
libtirpc3:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
------------------------------------------------------------------------------------------------
apt --fix-broken install
root@proxmox:~# apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
487 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
Setting up libssl1.1:amd64 (1.1.1w-0+deb11u2) ...
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
dpkg: error processing package libssl1.1:amd64 (--configure):
installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of libkrb5-3:amd64:
libkrb5-3:amd64 depends on libssl1.1 (>= 1.1.0); however:
Package libssl1.1:amd64 is not configured yet.
dpkg: error processing package libkrb5-3:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libgssapi-krb5-2:amd64:
libgssapi-krb5-2:amd64 depends on libkrb5-3 (= 1.18.3-6+deb11u5); however:
Package libkrb5-3:amd64 is not configured yet.
dpkg: error processing package libgssapi-krb5-2:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libtirpc3:amd64:
libtirpc3:amd64 depends on libgssapi-krb5-2 (>= 1.17); however:
Package libgssapi-krb5-2:amd64 is not configured yet.
dpkg: error processing package libtirpc3:amd64 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
libssl1.1:amd64
libkrb5-3:amd64
libgssapi-krb5-2:amd64
libtirpc3:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
--------------------------------------------------------------------------------------------------------
ich habe in den letzten zwei Jahren mehrere PVE-6-zu-7 Upgrades durchgeführt, bisher ohne größere Probleme,
aber jetzt ging bei einem entfernt stehendem Single-Server (kein Cluster) leider etwas schief.
Es lief vorher PVE 6.4.xx - Debian Buster
Da hatte ich noch mal mit apt update den letzten Stand hergestellt.
Da kam zuerst eine Fehlermeldung wegen einem veralteten Repository-Eintrag zu Sury - habe ich entfernt.
Update lief durch.
Danach dann Repositories von buster auf bullseye geändert
apt update - okay
! Habe aber später entdeckt, dass ich da bei Security Updates einen veralteten Debian Pfad ftp.debian.org statt deb.debian.org drin hatte.
pve6to7
- WARN: 2 running guests
- FAIL: resolved node IP xxx not configured or active for 'proxmox'
Eine VM runtergefahren - einen Container laufen gelassen
Wegen node IP hatte ich geschaut, aber keinen Fehler in den IP und PVE Configs gefunden
und nach Suche im Forum mit nur dieser Fehlermeldung gelesen dass man das Upgrade wagen kann.
apt dist-upgrade lief bis 55% - dann blieb Terminal-Anzeige lange dort hängen
und dann konnte man nicht mehr auf Proxmox GUI und Konsole von außen zugreifen.
Der Container lief weiter sauber - war erreichbar.
Jemand vor Ort konnte sich direkt am Server einloggen.
Dateien wie interfaces hosts .. wurden geprüft und waren unverändert und korrekt.
debian_version zeigte schon 11.11 an
pveversion zeigte pve-manager/7.4-19/f98bf8d4 (running kernel: 5.4.203-1-pve)
Hatten dann erstmal nichts mehr am System gemacht,
Am nächsten Tag ging auf einmal wieder der Zugriff auf die Proxmox GUI, aber das Login scheiterte.
SSH Zugriff ging aber wieder.
Und die vorher heruntergefahrene VM lief auch wieder, wie nach einem Neustart.
Aber laut uptime gab es keinen reboot.
Jetzt hängt das System im Upgrade Status fest.
Hatte jetzt versucht das Update/Upgrade neu anzustoßen / weiterlaufen zu lassen, aber hänge da fest.
Unten die Fehlermeldungen von:
pve6to7 -full
pveversion -v
apt update
apt upgrade
apt --fix-broken install
---------------------------------------------------------------------------------------------------------------------
aktuelle Statusmeldungen:
pve6to7 -full
root@proxmox:~# pve6to7 -full
= CHECKING VERSION INFORMATION FOR PVE PACKAGES =
Checking for package updates..
PASS: all packages uptodate
Checking proxmox-ve package version..
PASS: already upgraded to Proxmox VE 7
WARN: Proxmox VE 7 got superseeded by Proxmox VE 8.
Did you mean to use the pve7to8 checker script?
Checking running kernel version..
WARN: unexpected running and installed kernel '5.4.203-1-pve'.
= CHECKING CLUSTER HEALTH/SETTINGS =
SKIP: standalone node.
= CHECKING HYPER-CONVERGED CEPH STATUS =
SKIP: no hyper-converged ceph setup detected!
= CHECKING CONFIGURED STORAGES =
PASS: storage 'TEMP' enabled and active.
PASS: storage 'local' enabled and active.
PASS: storage 'local-lvm' enabled and active.
= MISCELLANEOUS CHECKS =
INFO: Checking common daemon services..
PASS: systemd unit 'pveproxy.service' is in state 'active'
PASS: systemd unit 'pvedaemon.service' is in state 'active'
PASS: systemd unit 'pvestatd.service' is in state 'active'
INFO: Checking for running guests..
WARN: 2 running guest(s) detected - consider migrating or stopping them.
INFO: Checking if the local node's hostname 'proxmox' is resolvable..
INFO: Checking if resolved IP is configured on local node..
FAIL: Resolved node IP '172.18.1.175' not configured or active for 'proxmox'
INFO: Check node certificate's RSA key size
PASS: Certificate 'pve-root-ca.pem' passed Debian Busters security level for TLS connections (4096 >= 2048)
PASS: Certificate 'pve-ssl.pem' passed Debian Busters security level for TLS connections (2048 >= 2048)
INFO: Checking backup retention settings..
INFO: storage 'local' - no backup retention settings defined - by default, PVE 7.x will no longer keep only the last backup, but all backups
WARN: storage 'TEMP' - parameter 'maxfiles' is deprecated with PVE 7.x and will be removed in a future version, use 'prune-backups' instead.
INFO: checking CIFS credential location..
PASS: no CIFS credentials at outdated location found.
INFO: Checking custom roles for pool permissions..
INFO: Checking node and guest description/note legnth..
PASS: All node config descriptions fit in the new limit of 64 KiB
PASS: All guest config descriptions fit in the new limit of 8 KiB
INFO: Checking container configs for deprecated lxc.cgroup entries
PASS: No legacy 'lxc.cgroup' keys found.
INFO: Checking storage content type configuration..
PASS: no problems found
INFO: Checking if the suite for the Debian security repository is correct..
PASS: already using 'bullseye-security'
= SUMMARY =
TOTAL: 23
PASSED: 16
SKIPPED: 2
WARNINGS: 4
FAILURES: 1
ATTENTION: Please check the output for detailed information!
Try to solve the problems one at a time and then run this checklist tool again.
--------------------------------------------------------------------------------------------------------------------------
pveversion -v
root@proxmox:~# pveversion -v
proxmox-ve: not correctly installed (running kernel: 5.4.203-1-pve)
pve-manager: not correctly installed (running version: 7.4-19/f98bf8d4)
pve-kernel-5.4: 6.4-20
pve-kernel-5.4.203-1-pve: 5.4.203-1
pve-kernel-5.4.157-1-pve: 5.4.157-1
pve-kernel-4.15: 5.4-19
pve-kernel-4.15.18-30-pve: 4.15.18-58
pve-kernel-4.15.18-10-pve: 4.15.18-32
ceph-fuse: not correctly installed
corosync: not correctly installed
criu: not correctly installed
glusterfs-client: not correctly installed
ifupdown: not correctly installed
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: not correctly installed
libproxmox-acme-perl: not correctly installed
libproxmox-backup-qemu0: not correctly installed
libproxmox-rs-perl: not correctly installed
libpve-access-control: not correctly installed
libpve-apiclient-perl: not correctly installed
libpve-common-perl: not correctly installed
libpve-guest-common-perl: not correctly installed
libpve-http-server-perl: not correctly installed
libpve-rs-perl: not correctly installed
libpve-storage-perl: not correctly installed
libqb0: 1.0.5-1
libspice-server1: not correctly installed
lvm2: not correctly installed
lxc-pve: not correctly installed
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: not correctly installed
proxmox-backup-file-restore: not correctly installed
proxmox-kernel-helper: not correctly installed
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: not correctly installed
proxmox-widget-toolkit: 3.7.4
pve-cluster: not correctly installed
pve-container: not correctly installed
pve-docs: not correctly installed
pve-edk2-firmware: not correctly installed
pve-firewall: not correctly installed
pve-firmware: 3.6-6
pve-ha-manager: not correctly installed
pve-i18n: 2.12-1
pve-qemu-kvm: not correctly installed
pve-xtermjs: 4.16.0-2
qemu-server: not correctly installed
smartmontools: 7.2-pve3
spiceterm: not correctly installed
swtpm: not correctly installed
vncterm: 1.7-1
zfsutils-linux: not correctly installed
------------------------------------------------------------------------------------------------------------
apt update
root@proxmox:~# apt update
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Hit:4 http://download.proxmox.com/debian/pve bullseye InRelease
Fetched 44.1 kB in 1s (51.6 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
--------------------------------------------------------------------------------------------------------------
apt upgrade
root@proxmox:~# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
487 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
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
Setting up libssl1.1:amd64 (1.1.1w-0+deb11u2) ...
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
dpkg: error processing package libssl1.1:amd64 (--configure):
installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of libkrb5-3:amd64:
libkrb5-3:amd64 depends on libssl1.1 (>= 1.1.0); however:
Package libssl1.1:amd64 is not configured yet.
dpkg: error processing package libkrb5-3:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libgssapi-krb5-2:amd64:
libgssapi-krb5-2:amd64 depends on libkrb5-3 (= 1.18.3-6+deb11u5); however:
Package libkrb5-3:amd64 is not configured yet.
dpkg: error processing package libgssapi-krb5-2:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libtirpc3:amd64:
libtirpc3:amd64 depends on libgssapi-krb5-2 (>= 1.17); however:
Package libgssapi-krb5-2:amd64 is not configured yet.
dpkg: error processing package libtirpc3:amd64 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
libssl1.1:amd64
libkrb5-3:amd64
libgssapi-krb5-2:amd64
libtirpc3:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
------------------------------------------------------------------------------------------------
apt --fix-broken install
root@proxmox:~# apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
487 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
Setting up libssl1.1:amd64 (1.1.1w-0+deb11u2) ...
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
dpkg: error processing package libssl1.1:amd64 (--configure):
installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of libkrb5-3:amd64:
libkrb5-3:amd64 depends on libssl1.1 (>= 1.1.0); however:
Package libssl1.1:amd64 is not configured yet.
dpkg: error processing package libkrb5-3:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libgssapi-krb5-2:amd64:
libgssapi-krb5-2:amd64 depends on libkrb5-3 (= 1.18.3-6+deb11u5); however:
Package libkrb5-3:amd64 is not configured yet.
dpkg: error processing package libgssapi-krb5-2:amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libtirpc3:amd64:
libtirpc3:amd64 depends on libgssapi-krb5-2 (>= 1.17); however:
Package libgssapi-krb5-2:amd64 is not configured yet.
dpkg: error processing package libtirpc3:amd64 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
libssl1.1:amd64
libkrb5-3:amd64
libgssapi-krb5-2:amd64
libtirpc3:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
--------------------------------------------------------------------------------------------------------
