can not migrate - expected votes do not match

otto001

Member
Jul 11, 2019
90
6
13
50
Hi,
I am using proxmox (5.4.11) in a homelab.
I am having a server which is on 24/7 and a backup machine I am using also as workstation.
I can not migrate VMs anymore, the error is:
kvm: could not acquire pid file: Resource temporarily unavailable
I suppose that there is a problem with corosync. On the workstation I get Expected votes: 3, on the 24/7 server: Expected votes: 2.
This is not matching. The corosync.cfg is the same on both machines.
Could anyone please help?
Thanks and best regards,
Otto
 
Hmm... still nothing. But starting the first command in shell, brings up:
/usr/bin/kvm -id 106 -name media -chardev socket,id=qmp,path=/var/run/qemu-server/106.qmp,server,nowait -mon chardev=qmp,mode=control -chardev socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5 -mon chardev=qmp-event,mode=control -pidfile /var/run/qemu-server/106.pid -daemonize -smbios type=1,uuid=0d7ddbc4-2a22-4fba-ab12-e9eb94204d43 -smp 2,sockets=2,cores=1,maxcpus=2 -nodefaults -boot menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg -vnc unix:/var/run/qemu-server/106.vnc,x509,password -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 4096 -device pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f -device pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e -device vmgenid,guid=0c20468e-ce43-4ff9-bb4f-01f01c172012 -device piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -device usb-tablet,id=tablet,bus=uhci.0,port=1 -device VGA,id=vga,bus=pci.0,addr=0x2 -chardev socket,path=/var/run/qemu-server/106.qga,server,nowait,id=qga0 -device virtio-serial,id=qga0,bus=pci.0,addr=0x8 -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 -iscsi initiator-name=iqn.1993-08.org.debian:01:9668d177b27e -drive file=/mnt/k/virt/images/106/vm-106-disk-0.qcow2,if=none,id=drive-virtio0,format=qcow2,cache=none,aio=native,detect-zeroes=on -device virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=200 -netdev type=tap,id=net0,ifname=tap106i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on -device virtio-net-pci,mac=6A:B1:AD:3A:AA:D6,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300 -machine type=pc-i440fx-3.0 -incoming unix:/run/qemu-server/106.migrate -S​
then

fuser /run/qemu-server/106.pid
/run/qemu-server/106.pid: 4968

and
ps aux | grep 4968
root 4968 11.2 6.3 5121732 4212700 ? Sl Jul26 181:22 /usr/bin/kvm -id 106 -name media -chardev socket,id=qmp,path=/var/run/qemu-server/106.qmp,server,nowait -mon chardev=qmp,mode=control -chardev socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5 -mon chardev=qmp-event,mode=control -pidfile /var/run/qemu-server/106.pid -daemonize -smbios type=1,uuid=0d7ddbc4-2a22-4fba-ab12-e9eb94204d43 -smp 2,sockets=2,cores=1,maxcpus=2 -nodefaults -boot menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg -vnc unix:/var/run/qemu-server/106.vnc,x509,password -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 4096 -device pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f -device pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e -device vmgenid,guid=0c20468e-ce43-4ff9-bb4f-01f01c172012 -device piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -device usb-tablet,id=tablet,bus=uhci.0,port=1 -device VGA,id=vga,bus=pci.0,addr=0x2 -chardev socket,path=/var/run/qemu-server/106.qga,server,nowait,id=qga0 -device virtio-serial,id=qga0,bus=pci.0,addr=0x8 -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 -iscsi initiator-name=iqn.1993-08.org.debian:01:1a1a68e8518 -drive file=/mnt/k/virt/images/106/vm-106-disk-0.qcow2,if=none,id=drive-virtio0,format=qcow2,cache=none,aio=native,detect-zeroes=on -device virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=200 -netdev type=tap,id=net0,ifname=tap106i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on -device virtio-net-pci,mac=6A:B1:AD:3A:AA:D6,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300 -machine type=pc
 
Well, does anyone have a hint where to start looking for the problem?
best regards,
Otto
 
I suppose that there is a problem with corosync. On the workstation I get Expected votes: 3, on the 24/7 server: Expected votes: 2.
* please post the output of `pvecm status` on both nodes
* please post both configs (/etc/corosync/corosync.conf)
* check the logs/status of corosync and pve-cluster services - `journalctl -u corosync -u pve-cluster`

hope this helps
 
Hi,

thanks for your help!
In the meantime (before your answer) I have de-installed and re-installed pve on the second node and everything is working again.
Nevertheless thanks for your help!
Best regards,
Otto
 

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!