My VIRTUAL machine cannot start. What do I need to do?

13524470402

New Member
Feb 26, 2022
2
0
1
36
My VIRTUAL machine cannot start. What do I need to do? The pveDaemon service has some errors as follows :

Code:
 pvedaemon.service - PVE API Daemon
   Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2022-02-26 19:50:59 CST; 1min 51s ago
  Process: 21132 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
 Main PID: 21139 (pvedaemon)
    Tasks: 4 (limit: 19660)
   Memory: 148.4M
   CGroup: /system.slice/pvedaemon.service
           ├─21139 pvedaemon
           ├─21140 pvedaemon worker
           ├─21141 pvedaemon worker
           └─21142 pvedaemon worker

Feb 26 19:50:59 slytherin pvedaemon[21139]: starting server
Feb 26 19:50:59 slytherin pvedaemon[21139]: starting 3 worker(s)
Feb 26 19:50:59 slytherin pvedaemon[21139]: worker 21140 started
Feb 26 19:50:59 slytherin pvedaemon[21139]: worker 21141 started
Feb 26 19:50:59 slytherin pvedaemon[21139]: worker 21142 started
Feb 26 19:50:59 slytherin systemd[1]: Started PVE API Daemon.
Feb 26 19:52:10 slytherin pvedaemon[21939]: start VM 207: UPID:slytherin:000055B3:00050BD7:621A146A:qmstart:207:root@pam:
Feb 26 19:52:10 slytherin pvedaemon[21142]: <root@pam> starting task UPID:slytherin:000055B3:00050BD7:621A146A:qmstart:207:root@pam:
Feb 26 19:52:35 slytherin pvedaemon[21939]: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
Feb 26 19:52:35 slytherin pvedaemon[21142]: <root@pam> end task UPID:slytherin:000055B3:00050BD7:621A146A:qmstart:207:root@pam: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)


An error occurs when the VM is started:
Code:
Error: org.freedesktop.DBus.Error.TimedOut:Failed to activate service 'org.freedesktop.systemd1':timed out (service_start_timeout=25000ms)

My System_bus_socket file exists.
How can I solve this problem? thank you.
 

Attachments

  • 微信截图_20220226201229.png
    微信截图_20220226201229.png
    106.6 KB · Views: 15
  • 微信截图_20220226201613.png
    微信截图_20220226201613.png
    57.7 KB · Views: 13
Hello 13524470402,
I hope you are doing very well.

Look at the logs in the VM/Container 207, there you might find more information. A problem like an nonexistent drive could be the problem

In order to isolate the problem you may disable the flat start at boot" from CT/VM 207 and see if on this way pvedaemon starts normally.
 
Hello 13524470402,
I hope you are doing very well.

Look at the logs in the VM/Container 207, there you might find more information. A problem like an nonexistent drive could be the problem

In order to isolate the problem you may disable the flat start at boot" from CT/VM 207 and see if on this way pvedaemon starts normally.
Hi Matiaspecchia, how can I check?
 

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!