可能原因：

• 原因1：PVE集群状态出错

• 查看：
  systemctl status pvestatd

  root@pve2:~# systemctl status pvestatd
  × pvestatd.service - PVE Status Daemon
   Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; preset: enabled)
   Active: failed (Result: signal) since Thu 2024-02-29 12:37:24 CST; 4 days ago
  Duration: 1w 3h 43.057s
  Main PID: 1685 (code=killed, signal=SEGV)
      CPU: 1h 31min 12.516s
  Feb 22 09:37:36 pve2 pvestatd[1685]: VM 1002 qmp command failed - VM 1002 qmp command 'query-proxmox-support' failed - unable to connect to VM 1002 qmp socket>
  Feb 22 09:37:36 pve2 pvestatd[1685]: status update time (8.253 seconds)
  Feb 22 09:37:43 pve2 pvestatd[1685]: status update time (6.114 seconds)
  Feb 22 21:13:29 pve2 pvestatd[1685]: got timeout
  Feb 24 17:14:59 pve2 pvestatd[1685]: IO::Multiplex: write error: Bad address
  Feb 27 21:21:35 pve2 pvestatd[1685]: VM 114 qmp command failed - VM 114 not running
  Feb 28 04:16:04 pve2 pvestatd[1685]: IO::Multiplex: write error: Bad address
  Feb 29 12:37:24 pve2 systemd[1]: pvestatd.service: Main process exited, code=killed, status=11/SEGV
  Feb 29 12:37:24 pve2 systemd[1]: pvestatd.service: Failed with result 'signal'.
  Feb 29 12:37:24 pve2 systemd[1]: pvestatd.service: Consumed 1h 31min 12.516s CPU time.
  root@pve2:~# systemctl restart pvestatd
  root@pve2:~# systemctl status pvestatd
  ● pvestatd.service - PVE Status Daemon
   Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; preset: enabled)
   Active: active (running) since Tue 2024-03-05 09:20:40 CST; 1s ago
  Process: 332713 ExecStart=/usr/bin/pvestatd start (code=exited, status=0/SUCCESS)
  Main PID: 332720 (pvestatd)
    Tasks: 1 (limit: 153605)
   Memory: 81.8M
      CPU: 226ms

• 解决：
  systemctl restart pvestatd

指尖风暴终身VIP

收藏 海报分享