Proxmox ungewollter Freeze

J

Jannik2020

Active Member
Jan 2, 2020
62
1
28
25
Hallo zusammen,

seit dem update auf Proxmox update auf 8.2.7
Linux 6.2.16-10-pve (2023-08-18T11:42Z)

freezed der Host immer nach einiger Zeit sodass ein Hard Reset erforderlich ist ich konnte in den Logs nichts aufälliges finden hat Jemand eine Indee?

Code: 
Since:
2024-10-26
Until:
2024-10-29

Oct 28 23:35:30 pve pveproxy[5932]: worker 795205 finished
Oct 28 23:35:30 pve pveproxy[5932]: starting 1 worker(s)
Oct 28 23:35:30 pve pveproxy[5932]: worker 974202 started
Oct 28 23:44:51 pve pveproxy[806543]: worker exit
Oct 28 23:44:51 pve pveproxy[5932]: worker 806543 finished
Oct 28 23:44:51 pve pveproxy[5932]: starting 1 worker(s)
Oct 28 23:44:51 pve pveproxy[5932]: worker 992539 started
Oct 28 23:45:52 pve pvedaemon[5914]: <root@pam> successful auth for user 'root@pam'
Oct 29 00:00:20 pve systemd[1]: Starting dpkg-db-backup.service - Daily dpkg database backup service...
Oct 29 00:00:20 pve systemd[1]: Starting logrotate.service - Rotate log files...
Oct 29 00:00:20 pve systemd[1]: dpkg-db-backup.service: Deactivated successfully.
Oct 29 00:00:20 pve systemd[1]: Finished dpkg-db-backup.service - Daily dpkg database backup service.
Oct 29 00:00:20 pve systemd[1]: Reloading pveproxy.service - PVE API Proxy Server...
Oct 29 00:00:20 pve pveproxy[1023351]: send HUP to 5932
Oct 29 00:00:20 pve pveproxy[5932]: received signal HUP
Oct 29 00:00:20 pve pveproxy[5932]: server closing
Oct 29 00:00:20 pve pveproxy[5932]: server shutdown (restart)
Oct 29 00:00:20 pve systemd[1]: Reloaded pveproxy.service - PVE API Proxy Server.
Oct 29 00:00:21 pve systemd[1]: Reloading spiceproxy.service - PVE SPICE Proxy Server...
Oct 29 00:00:21 pve spiceproxy[1023356]: send HUP to 5938
Oct 29 00:00:21 pve spiceproxy[5938]: received signal HUP
Oct 29 00:00:21 pve spiceproxy[5938]: server closing
Oct 29 00:00:21 pve spiceproxy[5938]: server shutdown (restart)
Oct 29 00:00:21 pve systemd[1]: Reloaded spiceproxy.service - PVE SPICE Proxy Server.
Oct 29 00:00:21 pve pvefw-logger[4844]: received terminate request (signal)
Oct 29 00:00:21 pve pvefw-logger[4844]: stopping pvefw logger
Oct 29 00:00:21 pve systemd[1]: Stopping pvefw-logger.service - Proxmox VE firewall logger...
Oct 29 00:00:21 pve spiceproxy[5938]: restarting server
Oct 29 00:00:21 pve spiceproxy[5938]: starting 1 worker(s)
Oct 29 00:00:21 pve spiceproxy[5938]: worker 1023381 started
Oct 29 00:00:21 pve systemd[1]: pvefw-logger.service: Deactivated successfully.
Oct 29 00:00:21 pve systemd[1]: Stopped pvefw-logger.service - Proxmox VE firewall logger.
Oct 29 00:00:21 pve systemd[1]: pvefw-logger.service: Consumed 2.181s CPU time.
Oct 29 00:00:21 pve pveproxy[5932]: restarting server
Oct 29 00:00:21 pve pveproxy[5932]: starting 3 worker(s)
Oct 29 00:00:21 pve pveproxy[5932]: worker 1023384 started
Oct 29 00:00:21 pve pveproxy[5932]: worker 1023385 started
Oct 29 00:00:21 pve pveproxy[5932]: worker 1023386 started
Oct 29 00:00:21 pve systemd[1]: Starting pvefw-logger.service - Proxmox VE firewall logger...
Oct 29 00:00:21 pve pvefw-logger[1023387]: starting pvefw logger
Oct 29 00:00:21 pve systemd[1]: Started pvefw-logger.service - Proxmox VE firewall logger.
Oct 29 00:00:21 pve systemd[1]: logrotate.service: Deactivated successfully.
Oct 29 00:00:21 pve systemd[1]: Finished logrotate.service - Rotate log files.
Oct 29 00:00:26 pve spiceproxy[5939]: worker exit
Oct 29 00:00:26 pve spiceproxy[5938]: worker 5939 finished
Oct 29 00:00:26 pve pveproxy[974202]: worker exit
Oct 29 00:00:26 pve pveproxy[992539]: worker exit
Oct 29 00:00:26 pve pveproxy[948931]: worker exit
Oct 29 00:00:26 pve pveproxy[5932]: worker 992539 finished
Oct 29 00:00:26 pve pveproxy[5932]: worker 948931 finished
Oct 29 00:00:26 pve pveproxy[5932]: worker 974202 finished
Oct 29 00:01:53 pve pvedaemon[5915]: <root@pam> successful auth for user 'root@pam'
Oct 29 00:17:01 pve CRON[1055908]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Oct 29 00:17:01 pve CRON[1055909]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Oct 29 00:17:01 pve CRON[1055908]: pam_unix(cron:session): session closed for user root
Oct 29 00:17:53 pve pvedaemon[5913]: <root@pam> successful auth for user 'root@pam'
Oct 29 00:33:53 pve pvedaemon[5913]: <root@pam> successful auth for user 'root@pam'
Oct 29 00:49:54 pve pvedaemon[5913]: <root@pam> successful auth for user 'root@pam'
Oct 29 01:17:01 pve CRON[1174612]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Oct 29 01:17:01 pve CRON[1174613]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Oct 29 01:17:01 pve CRON[1174612]: pam_unix(cron:session): session closed for user root
-- Reboot --
Oct 29 17:21:48 pve kernel: Linux version 6.2.16-10-pve (wolfgangb@sbuild) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PMX 6.2.16-10 (2023-08-18T11:42Z) ()
Oct 29 17:21:48 pve kernel: Command line: initrd=\EFI\proxmox\6.2.16-10-pve\initrd.img-6.2.16-10-pve root=ZFS=rpool/ROOT/pve-1 boot=zfs
Oct 29 17:21:48 pve kernel: KERNEL supported cpus:
Oct 29 17:21:48 pve kernel:   Intel GenuineIntel
 
Also ich sehe da nix. Aber eine Standardfrage drängt sich auf: warum verwendest du einen so alten Kern? Ich habe hier
Code: 
~# pveversion
pve-manager/8.2.7/3e0176e6bb2ade3b (running kernel: 6.8.12-2-pve)
...und du bist auf 6.2. Warum?
 
  • Like
Reactions: Johannes S
öhhh g
UdoB said:
Also ich sehe da nix. Aber eine Standardfrage drängt sich auf: warum verwendest du einen so alten Kern? Ich habe hier
Code: 
~# pveversion
pve-manager/8.2.7/3e0176e6bb2ade3b (running kernel: 6.8.12-2-pve)
...und du bist auf 6.2. Warum?
Click to expand...
öhhh gute Frage ich habe keine Updates ausstehend

Wie kann ich das sonst updaten?
 
Last edited:
Also, der sollte eigentlich automatisch installiert worden sein. Ein normaler Upgradevorgang sollte immer "full-" enthalten, also apt update && apt full-upgrade. Was liefert dies als Ergebnis bei dir? Hast du vielleicht "apt upgrade" aufgerufen? --> Das ist im Proxmox-Kontext nicht gut.

Der Default-Kernel wird automatisch installiert; man kann das aber auch manuell anstoßen: apt --reinstall install proxmox-default-kernel

Um im Voraus zu wissen, welcher konkrete Kernel das dann wohl werden wird, fragt man nach Abhängigkeiten:
Code: 
~# apt depends proxmox-default-kernel
proxmox-default-kernel
  Depends: proxmox-kernel-6.8

~# apt depends proxmox-kernel-6.8
proxmox-kernel-6.8
  Depends: pve-firmware
 |Depends: proxmox-kernel-6.8.12-2-pve-signed
  Depends: proxmox-kernel-6.8.12-2-pve
...

Zu guter Letzt könnte der 6.2 "gepinned", also manuell festgenagelt sein, das solltest der Admin aber wissen. ;-)

Frag mal das boot-tool, welche Kernel installiert sind. Mein Homelab:
Code: 
~# proxmox-boot-tool kernel list
Manually selected kernels:
None.

Automatically selected kernels:
6.5.13-6-pve
6.8.12-1-pve
6.8.12-2-pve
 
Vermutlich mal Kernel angepinnt.
Einfach mal: proxmox-boot-tool kernel unpin ausführen.
 
ist kein kernel gepinnt

Code: 
root@pve:~# apt update && apt full-upgrade
Get:1 http://security.debian.org bookworm-security InRelease [48.0 kB]
Hit:2 http://ftp.de.debian.org/debian bookworm InRelease                      
Hit:3 http://ftp.de.debian.org/debian bookworm-updates InRelease              
Hit:4 http://download.proxmox.com/debian/pve bookworm InRelease
Get:5 http://security.debian.org bookworm-security/main amd64 Packages [190 kB]
Fetched 238 kB in 1s (385 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
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.
root@pve:~#

Code: 
root@pve:~# proxmox-boot-tool kernel list
Manually selected kernels:
None.

Automatically selected kernels:
6.2.16-10-pve
6.5.13-6-pve
6.8.12-1-pve
6.8.12-2-pve
 
Last edited:
etwas merkwürdig da mir der beim reboot auch nicht angezeigt wird ich werd den mal pinnen
 
Code: 
root@pve:~# proxmox-boot-tool kernel list
Manually selected kernels:
None.

Automatically selected kernels:
6.2.16-10-pve
6.5.13-6-pve
6.8.12-1-pve
6.8.12-2-pve

Pinned kernel:
6.8.12-2-pve
root@pve:~# pveversion
pve-manager/8.2.7/3e0176e6bb2ade3b (running kernel: 6.2.16-10-pve)
 
Ich bin kein Grub Experte aber ich würde mir mal anschauen wie die Konfiguration aussieht. Eventuell mal von jemand mit Ahnung drauf schauen lassen.
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back