QDevice no vote

hello Moayad,

thanks for your reply. attached the corosync file. since today i got the message, that the "file corosync.conf is beeing edited by root". i am not able to edit the file anymore....


  • Bildschirmfoto vom 2023-10-03 17-39-25.png
    Bildschirmfoto vom 2023-10-03 17-39-25.png
    47.9 KB · Views: 15
Your first config screenshot (text would be nicer) shows tha you said the qdevice should have two votes, in which case you made it a single point of failure, it should only always provide one vote (as it does by default).

I'd check the qdevice service on the host that provides the external node, maybe you get an actual error message there, or maybe it simply doesn't run.

Where is the QDevice actually located, on some RaspberryPi or some other host?
@t.lamprecht this was a try by myself to raise the vote for the qdevice. i hoped that it would change something - but it didn't succeed. i don't know what happend after, but i was not able to edit the corosync.conf anymore

nevertheless it is now running.

your hint with the service on the qdevice (pi) was right. the service on the pi was not running correctly. it said that it was not able to connect to the database. (shame on me, that I didn't check this before...). sorry for not creating a screenshot of this error.

my steps were:
I completely deleted the cluster on both nodes according this guide https://pve.proxmox.com/wiki/Cluster_Manager#_remove_a_cluster_node (Seperate a node without installing) and created a new one. after trying to add the second node, i received an error that it was not possible to join. the error lead me to remove all "old" entries in the /etc/pve/nodes on both nodes

after this i was able to add the second node to the cluster.
I also reinstalled the pi and followed the steps in the last post https://forum.proxmox.com/threads/qdevice-not-voting.108871/

for me, it is a learning process and I am not sure if some steps can be skipped or not. please correct me if some steps were wrong

thanks all for your support

EDIT: one last hint. the reason for deleting the cluster was, because after my previous post and a reboot, the cluster was also not ready anymore. maybe that was the reason, why the qdevice also didn't work...
Last edited:


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!