Cannot start pvedaemon after rebooting.

W

Wanabekeats

Member
Jul 17, 2022
2
0
6
Hi Guys ,I meet this problem when I found that the webUI couldn`t open.
I try to check pve service and found this .
Code: 
[root@pve ~]# systemctl | grep pve
  etc-pve.mount                                                                                                                  loaded active     mounted   /etc/pve
  mnt-pve-mirror.mount                                                                                                           loaded active     mounted   Mount storage 'mirror' under /mnt/pve
  pve-cluster.service                                                                                                            loaded active     running   The Proxmox VE cluster filesystem
  pve-firewall.service                                                                                                           loaded active     running   Proxmox VE firewall
● pve-guests.service                                                                                                             loaded failed     failed    PVE guests
● pve-ha-crm.service                                                                                                             loaded failed     failed    PVE Cluster HA Resource Manager Daemon
● pve-ha-lrm.service                                                                                                             loaded failed     failed    PVE Local HA Resource Manager Daemon
  pve-lxc-syscalld.service                                                                                                       loaded active     running   Proxmox VE LXC Syscall Daemon
  pve-query-machine-capabilities.service                                                                                         loaded active     exited    PVE Query Machine Capabilities
  pvebanner.service                                                                                                              loaded active     exited    Proxmox VE Login Banner
● pvedaemon.service                                                                                                              loaded failed     failed    PVE API Daemon
  pvefw-logger.service                                                                                                           loaded active     running   Proxmox VE firewall logger
  pvenetcommit.service                                                                                                           loaded active     exited    Commit Proxmox VE network changes
● pveproxy.service                                                                                                               loaded failed     failed    PVE API Proxy Server
● pvescheduler.service                                                                                                           loaded failed     failed    Proxmox VE scheduler
● pvestatd.service                                                                                                               loaded failed     failed    PVE Status Daemon
  dev-pve-swap.swap                                                                                                              loaded active     active    /dev/pve/swap
  pve-storage.target                                                                                                             loaded active     active    PVE Storage Target
  pve-daily-update.timer                                                                                                         loaded active     waiting   Daily PVE download activities

I don`t know why too many pve service couldn`t start. So try to check the problem

Code: 
May 28 20:51:41 pve systemd[1]: Starting pvestatd.service - PVE Status Daemon...
░░ Subject: A start job for unit pvestatd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pvestatd.service has begun execution.
░░
░░ The job identifier is 104.
May 28 20:51:41 pve pvestatd[4546]: Bareword "PVE::Syscall::fallocate" not allowed while "strict subs" in use at /usr/share/perl5/PVE/Storage/Common.pm line 105, <DATA> line 960.
May 28 20:51:41 pve pvestatd[4546]: Compilation failed in require at /usr/share/perl5/PVE/Storage/Plugin.pm line 18, <DATA> line 960.
May 28 20:51:41 pve pvestatd[4546]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Storage/Plugin.pm line 18, <DATA> line 960.
May 28 20:51:41 pve pvestatd[4546]: Compilation failed in require at /usr/share/perl5/PVE/Storage.pm line 27, <DATA> line 960.
May 28 20:51:41 pve pvestatd[4546]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Storage.pm line 27, <DATA> line 960.
May 28 20:51:41 pve pvestatd[4546]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvestatd.pm line 19, <DATA> line 960.
May 28 20:51:41 pve pvestatd[4546]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvestatd.pm line 19, <DATA> line 960.
May 28 20:51:41 pve pvestatd[4546]: Compilation failed in require at /usr/bin/pvestatd line 9, <DATA> line 960.
May 28 20:51:41 pve pvestatd[4546]: BEGIN failed--compilation aborted at /usr/bin/pvestatd line 9, <DATA> line 960.
May 28 20:51:41 pve systemd[1]: pvestatd.service: Control process exited, code=exited, status=255/EXCEPTION
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit pvestatd.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 255.
May 28 20:51:41 pve systemd[1]: pvestatd.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pvestatd.service has entered the 'failed' state with result 'exit-code'.
May 28 20:51:41 pve systemd[1]: Failed to start pvestatd.service - PVE Status Daemon.
░░ Subject: A start job for unit pvestatd.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pvestatd.service has finished with a failure.
░░
░░ The job identifier is 104 and the job result is failed.
Code: 
[root@pve ~]# journalctl -xeu pveproxy.service
░░ A start job for unit pveproxy.service has begun execution.
░░
░░ The job identifier is 1068.
May 28 20:51:44 pve pveproxy[4603]: Bareword "PVE::Syscall::fallocate" not allowed while "strict subs" in use at /usr/share/perl5/PVE/Storage/Common.pm line 105, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: Compilation failed in require at /usr/share/perl5/PVE/Storage/Plugin.pm line 18, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Storage/Plugin.pm line 18, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: Compilation failed in require at /usr/share/perl5/PVE/Storage.pm line 27, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Storage.pm line 27, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: Compilation failed in require at /usr/share/perl5/PVE/GuestHelpers.pm line 8, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/GuestHelpers.pm line 8, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 8, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 8, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line 13, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 13, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: Compilation failed in require at /usr/bin/pveproxy line 11, <DATA> line 960.
May 28 20:51:44 pve pveproxy[4603]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11, <DATA> line 960.
May 28 20:51:44 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=255/EXCEPTION
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit pveproxy.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 255.
May 28 20:51:44 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pveproxy.service has entered the 'failed' state with result 'exit-code'.
May 28 20:51:44 pve systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.
░░ Subject: A start job for unit pveproxy.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has finished with a failure.
░░
░░ The job identifier is 1068 and the job result is failed.
May 28 20:51:44 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit pveproxy.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
May 28 20:51:44 pve systemd[1]: Stopped pveproxy.service - PVE API Proxy Server.
░░ Subject: A stop job for unit pveproxy.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit pveproxy.service has finished.
░░
░░ The job identifier is 1179 and the job result is done.
May 28 20:51:44 pve systemd[1]: pveproxy.service: Start request repeated too quickly.
May 28 20:51:44 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pveproxy.service has entered the 'failed' state with result 'exit-code'.
May 28 20:51:44 pve systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.
░░ Subject: A start job for unit pveproxy.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has finished with a failure.
░░
░░ The job identifier is 1179 and the job result is failed.
I don`t have any idea , what should I do?
 
You either had an incomplete/failed upgrade or a failing disk. There are a few discussions of similar symptoms that may be helpful, i.e.:
N

[SOLVED] Thread 'Issue after update'

I updated my server today from the UI and rebooted, not realizing the download server was unavailable. After poking around in the command line for a while, I realized the issue and changed to one of the other cdn servers and ran the update-distro command. Now, I'm having issues with pve-proxy, pve-guests, and pvedaemon. All three give me the following error:

Code: 
Mar 13 12:52:35 *********** pvedaemon[2372]: Experimental "my" subs not enabled at /usr/share/perl5/PVE/APIClient/LWP.pm line 278.
Mar 13 12:52:35 *********** pvedaemon[2372]: Compilation failed in require at...

Good luck

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Hi,
please share the output of pveversion -v, apt update and apt list --upgradable.
 
You must log in or register to reply here.
Top Bottom