Recent content by Loki

  1. L

    Problems with cluster...

    Try to downgrade kernel to 2.6.32. According to spirit's post kernel 3.10 has a disabled multicast_querier. And sorry for me, I've forgot to mention that I use 2.6.32 kernel with 3.3 pve. Maybe that's why I don't have such issue after upgrade.
  2. L

    Problems with cluster...

    Because with 3.3 you updated corosync too. I would suggest you to use tcpdump. Try to capture multicast packets (see address from pvecm status) when node is failed. Also try to use omping when node is failed to see if it stops to receive heartbeat. And as a final workaround for 3 nodes cluster...
  3. L

    Problems with cluster...

    I would suggest you to use tcpdump to debug your problem. Try to capture multicast address (from pvecm status) and see if it stops to comming/sending.
  4. L

    Problems with cluster...

    More than 1 day passed since update :) Everything is still fine. So I guess you' problem lies in igmp snooping on vmbr.
  5. L

    HPN-SSH on proxmox (faster storage/computer migration?)

    Hello! Just add "migration_unsecure: 1" (without quotes) into /etc/pve/datacenter.cfg and migration speed will increase dramatically :)
  6. L

    Problems with cluster...

    auto lo iface lo inet loopback iface eth0 inet manual iface eth1 inet manual iface eth2 inet manual iface eth3 inet manual auto bond0 iface bond0 inet static address 192.168.8.2 netmask 255.255.255.0 gateway 192.168.8.254 slaves eth0 eth1...
  7. L

    Problems with cluster...

    So, guys! I've also decided to update 3 nodes from 3.2 to 3.3 and updating went fine. I've been already monitoring these 3 nodes about 1 hour and it seems everything OK. BUT I don't use vmbr for heartbeating, I use physical interfaces.
  8. L

    Problems with cluster...

    Hello,sirtech! Does your heartbeat between nodes work through vmbr or it uses physical interface? Did you try to use ethX/bondX for heartbeat? This may be important 'cause vmbr is bridge and it acts as software switch for tap-devices connected to it and it has its own igmp snooping settings like...
  9. L

    Problems with cluster...

    Hello! Did you try to disable igmp snooping on cisco switch? conf t no ip igmp snooping
  10. L

    qdisk and quorum

    Thanks, dietmar! Is it safe to just remove qdiskd from cluster.conf?
  11. L

    qdisk and quorum

    Hello! I've found this interesting article: http://magazine.redhat.com/2007/12/19/enhancing-cluster-quorum-with-qdisk/ According to it, I can enhance cluster quorum with qdisk. How do you think is it good idea to use qdisk with non-two_nodes cluster and assign more than 1 vote for qdisk (as...
  12. L

    create a screenshot of the virtual machine

    If it's annoying so just use NoVNC-console or SPICE :)
  13. L

    Feature request: add ability to start HA VM on specific host via GUI

    Hello! I would like to suggest you adding ability to start HA VM on specific host by selecting it through the PVE.form.NodeSelector (as it's done in Migrate window). I mean, when you click "Start" button then window with PVE.form.NodeSelector appears and after clusvcadm -e VMID -m $target...
  14. L

    Remove qdisk from cluster

    Hello! I have cluster with 3 nodes and 1 qdisk (1 vote for each nodes and 2 votes for qdisk) and qdisk uses /dev/sdb1. But now I want to set qdisk into small LVM partition. Is it enough to just remove it from cluster.conf and add it again or it maybe dangerous? __ Thanks

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!