[SOLVED] can't start VM after cluster reboot 'ha-manager set vm:105 --state started' failed: exit code 255'

scyto

Active Member
Aug 8, 2023
359
68
28
I shut down my cluster by issuing sequential shutdown commands to my nodes, after reboot one VM on one node won't start with the errors below

Code:
Oct 08 15:04:51 pve3 pvedaemon[1626]: <root@pam> starting task UPID:pve3:00005304:00039B66:65232783:hastart:105:root@pam:
Oct 08 15:04:51 pve3 pvedaemon[21252]: command 'ha-manager set vm:105 --state started' failed: exit code 255
Oct 08 15:04:51 pve3 pvedaemon[1626]: <root@pam> end task UPID:pve3:00005304:00039B66:65232783:hastart:105:root@pam: command 'ha-manager set vm:105 --state started' failed: exit code 255

1. i guess I should stop all VMs manually before shutting all nodes down? (i.e. can't rely on shutdown command from UI to do the right thing?)
2. what do i do to fix this?
 
Last edited:

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!