[SOLVED] [pvescheduler] <defunct>

loomes

Renowned Member
May 22, 2018
113
27
68
44
Nach dem Update auf 7.4 habe ich auf einem meiner Nodes das Problem das der pvescheduler in den defunct state fällt.
Reboot hat auch nicht geholfen. Die anderen Nodes im Cluster laufen. Ist halt doof weil er meine Backup Tasks auf dem Node mit dem fehlerhaften pvescheduler nicht mehr automatisch ausführt. Manuel gestartet laufen sie einwandfrei durch.
Irgendjemand eine Idee wie ich vorgehen kann um das Problem zu beheben? Ansonsten läuft alles einwandfrei.

Code:
systemctl status pvescheduler.service
● pvescheduler.service - Proxmox VE scheduler
     Loaded: loaded (/lib/systemd/system/pvescheduler.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2023-03-25 20:52:47 CET; 1h 14min ago
    Process: 6106 ExecStart=/usr/bin/pvescheduler start (code=exited, status=0/SUCCESS)
   Main PID: 6141 (pvescheduler)
      Tasks: 3 (limit: 76956)
     Memory: 101.8M
        CPU: 907ms
     CGroup: /system.slice/pvescheduler.service
             └─6141 pvescheduler

Code:
ps | grep pvescheduler
root      273946  0.0  0.0   6264   644 pts/0    S+   22:07   0:00          \_ grep pvescheduler
root        6141  0.0  0.1 336696 109296 ?       Ss   20:52   0:00 pvescheduler
root        6144  0.0  0.0      0     0 ?        Z    20:52   0:00  \_ [pvescheduler] <defunct>
root        8039  0.0  0.0      0     0 ?        Z    20:52   0:00  \_ [pvescheduler] <defunct>

Hier tut sich auch nicht viel. Auf den anderen Nodes rauschen da allerhand Daten durch.
Code:
strace -yyttT -f -s 512 -p 6141
strace: Process 6141 attached
23:48:27.518378 restart_syscall(<... resuming interrupted read ...>) = 0 <32.577207>
23:49:00.095752 clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=60, tv_nsec=0}, 0x7ffc7eb02e30) = 0 <60.000102>
23:50:00.096743 clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=60, tv_nsec=0}, 0x7ffc7eb02e30) = 0 <60.000113>
23:51:00.097065 clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=60, tv_nsec=0},

Code:
systemctl status pve-guests.service
● pve-guests.service - PVE guests
     Loaded: loaded (/lib/systemd/system/pve-guests.service; enabled; vendor preset: enabled)
     Active: active (exited) since Sat 2023-03-25 20:52:46 CET; 1h 21min ago
    Process: 1894 ExecStartPre=/usr/share/pve-manager/helpers/pve-startall-delay (code=exited, status=0/SUCCESS)
    Process: 1904 ExecStart=/usr/bin/pvesh --nooutput create /nodes/localhost/startall (code=exited, status=0/SUCCESS)
   Main PID: 1904 (code=exited, status=0/SUCCESS)
        CPU: 1.981s

Code:
systemctl status pve-storage.target pve-cluster.service
● pve-storage.target - PVE Storage Target
     Loaded: loaded (/lib/systemd/system/pve-storage.target; static)
     Active: active since Sat 2023-03-25 20:52:08 CET; 2h 45min ago

● pve-cluster.service - The Proxmox VE cluster filesystem
     Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2023-03-25 20:52:09 CET; 2h 45min ago
   Main PID: 1569 (pmxcfs)
      Tasks: 7 (limit: 76956)
     Memory: 51.0M
        CPU: 13.642s
     CGroup: /system.slice/pve-cluster.service
             └─1569 /usr/bin/pmxcfs

Mär 25 21:52:08 proxmox pmxcfs[1569]: [dcdb] notice: data verification successful
Mär 25 22:52:08 proxmox pmxcfs[1569]: [dcdb] notice: data verification successful

Code:
pveversion -v
proxmox-ve: 7.4-1 (running kernel: 6.1.15-1-pve)
pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a)
pve-kernel-6.1: 7.3-6
pve-kernel-5.15: 7.3-3
pve-kernel-6.1.15-1-pve: 6.1.15-1
pve-kernel-5.15.102-1-pve: 5.15.102-1
ceph-fuse: 14.2.21-1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-3
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-1
libpve-rs-perl: 0.7.5
libpve-storage-perl: 7.4-2
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.3.3-1
proxmox-backup-file-restore: 2.3.3-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.1-1
proxmox-widget-toolkit: 3.6.3
pve-cluster: 7.3-3
pve-container: 4.4-3
pve-docs: 7.4-2
pve-edk2-firmware: 3.20221111-2
pve-firewall: 4.3-1
pve-firmware: 3.6-4
pve-ha-manager: 3.6.0
pve-i18n: 2.11-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-1
qemu-server: 7.4-2
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.9-pve1
 
Last edited:
Vielen Dank für den Link. Das ist es. Paket enfernt und pvescheduler läuft wieder.
 

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!

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!