[SOLVED] pve-guests service failed to start

I

itret

Member
Proxmox Subscriber
Jul 4, 2022
70
10
13
Poland
Anyone know what to do to fix this issue?
This gives me a critical error on my monitoring site.
Why is is unable to lock the file .active.lock?

Code: 
systemctl status pve-guests
● pve-guests.service - PVE guests
     Loaded: loaded (/lib/systemd/system/pve-guests.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Fri 2023-06-02 16:18:51 CEST; 1 day 16h ago
    Process: 1802 ExecStartPre=/usr/share/pve-manager/helpers/pve-startall-delay (code=exited, status=0/SUCCESS)
    Process: 1803 ExecStart=/usr/bin/pvesh --nooutput create /nodes/localhost/startall (code=exited, status=25)
   Main PID: 1803 (code=exited, status=25)
        CPU: 3.891s

Jun 02 16:18:27 node2 pve-guests[1804]: <root@pam> starting task UPID:node2:00000C78:00004DBB:6479FA33:qmstart:110:root@pam:
Jun 02 16:18:27 node2 pve-guests[3192]: start VM 110: UPID:node2:00000C78:00004DBB:6479FA33:qmstart:110:root@pam:
Jun 02 16:18:35 node2 pvesh[1803]: Starting VM 111
Jun 02 16:18:35 node2 pve-guests[3380]: start VM 111: UPID:node2:00000D34:00005113:6479FA3B:qmstart:111:root@pam:
Jun 02 16:18:35 node2 pve-guests[1804]: <root@pam> starting task UPID:node2:00000D34:00005113:6479FA3B:qmstart:111:root@pam:
Jun 02 16:18:51 node2 pvesh[1803]: can't lock file '/var/log/pve/tasks/.active.lock' - got timeout
Jun 02 16:18:51 node2 systemd[1]: pve-guests.service: Main process exited, code=exited, status=25/n/a
Jun 02 16:18:51 node2 systemd[1]: pve-guests.service: Failed with result 'exit-code'.
Jun 02 16:18:51 node2 systemd[1]: Failed to start PVE guests.
Jun 02 16:18:51 node2 systemd[1]: pve-guests.service: Consumed 3.891s CPU time.
 
itret said:
Finally I ended up with host restart, problem's gone. Please mark as solved.
Click to expand...
Only you can mark is as solved by editing your first post in this thread. Almost everybody here does not have permissions to do that for you.
I have no idea why it did not work before the reboot. Glad you got it solved.
 
You must log in or register to reply here.
Top Bottom