status change startup => wait_for_agent_lock


Active Member
May 20, 2019
Hi, I have 1 of the 3 cluster nodes in IDLE mode.
My log shows me this:

# journalctl -u pve-ha-lrm -l
-- Logs begin at Tue 2019-05-21 10:33:10 -03, end at Tue 2019-05-21 11:05:01 -03. --
May 21 10:33:18 h1 systemd[1]: Starting PVE Local HA Ressource Manager Daemon...
May 21 10:33:19 h1 pve-ha-lrm[2234]: starting server
May 21 10:33:19 h1 pve-ha-lrm[2234]: status change startup => wait_for_agent_lock
May 21 10:33:19 h1 systemd[1]: Started PVE Local HA Ressource Manager Daemon.

# ha-manager status
quorum OK
master h3 (active, Tue May 21 11:11:11 2019)
lrm h1 (idle, Tue May 21 11:11:15 2019)
lrm h3 (active, Tue May 21 11:11:14 2019)
lrm h6 (active, Tue May 21 11:11:14 2019)
service vm:100 (h3, started)
service vm:102 (h3, started)
service vm:108 (h3, started)
service vm:116 (h6, started)
service vm:120 (h6, started)
service vm:121 (h6, started)
service vm:122 (h6, started)
service vm:123 (h6, started)

What should I do?


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!