Search results

  1. F

    Modify interface for multicast

    Since added window_size to 300 in cluster.conf, i have no more "corosync [TOTEM ] FAILED TO RECEIVE" and the cluster is up. No more news...
  2. F

    Container live migration problems

    Thank you for the information. Meanwhile, for container, i will use local storage... :(
  3. F

    Container live migration problems

    Hi, I got problem to migrate a Container in my cluster of 3 nodes. The vm migrate to the second node but can't start. I have to start it in the gui. Jul 05 15:42:58 starting migration of CT 100 to node 'prox' (*.*.*.155) Jul 05 15:42:58 container is running - using online migration Jul 05...
  4. F

    Modify interface for multicast

    Thanks for your answer. Otherwise, before playing with routing, i would test how to eliminate this infamous log [TOTEM] Retransmit list. According to http://www.hastexo.com/resources/hints-and-kinks/whats-totem-retransmit-list-all-about-corosync and...
  5. F

    Modify interface for multicast

    Hi, I have three nodes in a cluster with Proxmox ve 2.1. Everything seems ok except that i notice in my corosync log some message like this: corosync [TOTEM ] Retransmit List: 4ea806 4ea7f6 4ea7f7 4ea7f8 4ea807 4ea808 4ea809 4ea80a 4ea7e7 4ea7e8 4ea7e9 4ea7ea 4ea7eb 4ea7fb 4ea7fc 4ea7fd 4ea7ec...

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!