[SOLVED] Issue with HA on CEPH

killmasta93

Renowned Member
Aug 13, 2017
960
56
68
30
Hi,
Currently I have a test CEPH cluster. I was trying to simulate a hardware failure by disconnecting on of the nodes. It moves the VM but gets stuck when i try to see on VNC and when it tries to start im getting these erros any ideas?

Code:
()
task started by HA resource agent
2019-03-24 15:33:51 starting migration of VM 101 to node 'prometheus2' (192.168.100.252)
2019-03-24 15:33:51 copying disk images
2019-03-24 15:33:51 starting VM 101 on remote node 'prometheus2'
2019-03-24 15:33:52 VM 101 already running
2019-03-24 15:33:52 ERROR: online migrate failure - command '/usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=prometheus2' root@192.168.100.252 qm start 101 --skiplock --migratedfrom prometheus3 --migration_type secure --stateuri unix --machine pc-i440fx-2.12' failed: exit code 255
2019-03-24 15:33:52 aborting phase 2 - cleanup resources
2019-03-24 15:33:52 migrate_cancel
2019-03-24 15:33:53 ERROR: migration finished with problems (duration 00:00:02)
TASK ERROR: migration problems


task started by HA resource agent
TASK ERROR: start failed: command '/usr/bin/kvm -id 101 -name 101 -chardev 'socket,id=qmp,path=/var/run/qemu-server/101.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/101.pid -daemonize -smbios 'type=1,uuid=733a5e2d-3ce2-45f4-a5bb-2e52bb9c1db2' -smp '2,sockets=1,cores=2,maxcpus=2' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc unix:/var/run/qemu-server/101.vnc,x509,password -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 4000 -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=c0e184f0-6067-4cc1-b328-bf503d555b92' -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/101.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:de613c325' -drive 'file=rbd:datavms/vm-101-disk-0:conf=/etc/pve/ceph.conf:id=admin:keyring=/etc/pve/priv/ceph/datavms.keyring,if=none,id=drive-virtio0,cache=writeback,format=raw,aio=threads,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=4E:A8:43:15:EA:84,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -machine 'type=pc'' failed: got timeout
Thank you
 
Hi,
does this happen only with this VM or also with others? Can you post the VM config `cat /etc/pve/qemu-server/VMID.conf`?
VM 101 already running
 
Thanks for the reply, it happened because i had some messed up OSD i fix the storage and it started to work
 

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!