Search results

Test multicast traffic, please see https://pve.proxmox.com/wiki/Multicast_notes#Testing_multicast.

Not sure, but try to run this on all nodes: # mv /root/.ssh/known_hosts /root/.ssh/known_hosts.BAK And try again (and start/test a SSH session from each node to all other nodes). If this doesn't help, just run the following to restore the old situation: # mv /root/.ssh/known_hosts.BAK...

What's the preffered watchdog for PVE 4.x, hardware or software based? I'm asking because I've had a issue last days with a Dell idrac module in one of my nodes (https://forum.proxmox.com/threads/ipmi-couldnt-get-irq-info-and-runs-to-slow.27846/). It seems this module is faulty and it will be...

Yup, I'm sure. As far as I know this is done already automaticly (I can't remember I've added it manually). No idea why it isn't added in your setup automaticly. For example when you install PVE on a clean Debian Jessie install, Proxmox also recommand to add your hostnames/IP's to /etc/hosts...

Your welcome! :) BTW, I would recommend to also add the hostnames/IP's to your hostfile, because your cluster core communications depends on it (if you don't have WAN, for example when your ISP have a problem, you still don't want your cluster to screw up). Besides that, a lookup from your...

Normally it's done by /etc/hosts as you expected. Maybe you have added a custom DNS-zone to the old nodes resolver(s)? Check /etc/resolv.conf for your nameservers and run "host -t a vh04 IP.OF.FIRST.DNS" to see if it answer correct.

On a 5-node cluster (all Dell servers with idrac enterprise) running fine for some months, yesterday a node had a watchdog timer expired and rebooted. Last night same issue twice, but since second reboot the logs are full of: Jun 14 05:59:59 host01 kernel: [ 3527.075573] ipmi_si ipmi_si.0...

Hi Francesco, Thank you for your feedback. I'm glad it works as expected. Enjoy your PVE cluster! :)

Prices of VMware licenses can vary from country to country and from supplier to supplier and is also (like PVE subscriptions) dependent of your setup. Probably your company make use of some kind of SPLA (Service Provider License Agreement) model for monthly payment, within your company someone...

No, I don't. But are there changes in the transfer proces that can fix these errors? Unfortunately I can't update right now, because I'm out for a holiday in about 2 weeks, and I don't want to make any changes to config/servers that are not critical within 2 weeks before I'm out of office for...

Hi Alexandre, Not a big problem (no VM's are corrupted), but since I use the unsecure migration flag I still do have sometimes a migration problem on 1 VM when using the 'migrate all' option. I have some logs now: () task started by HA resource agent Jun 06 12:42:30 starting migration of VM...

I think you are trying to have redundant links? You need to make use of bond interfaces for this and add the bridge on top of the bond. So, for example: eth0 and eth1 in bond0 (active-backup), vmbr0 and vmbr1 uses bond0. What is your subnet? Since the IP's you use are very close to each other...

Not really. If you have 2 physical nodes and 1 virtual node running on 1 of the physical nodes for quorum, you lose quorum when the physical node that serves the virtual node have a total system crash. So you still have a SPOF.

That's definitely not the issue. In fact, PVE is a Debian based system. I think about 90% of all our VM's running on PVE are Debian (Wheezy and Jessie).

You can simply define HA groups to achieve the thirth node isn't used for VM's. But, as far as I know PVE will only work on AMD64 and/or EMT64, not on ARM. So I don't think a RPi will work. On non-production envoirement a low end /power server will do the job and if one HDD is large enough for...

You need to have at least 3 nodes for a real cluster because you need to have a odd number of nodes (not really true since you can also have 4, 6, 8 etc nodes, but for example a 4 node cluster may still lose only 1 node (like a 3 node cluster), while a 5 node cluster may lose 2 nodes. A 6 node...

Still very strange. I currently have no more ideas for you for a fix. Maybe some other user or someone from Proxmox staff have a clue?

We only use shared storage on all PVE nodes we have and all our production servers are in a HA cluster. In fact, we even don't have/sell any VM that's not HA. But, for testing purposes and for others (including some colo customers with own hardware) that run PVE on a single node I think this...

Strange. Try this command also: # lspci | grep -i eth What's the output? You should see something like: 00:12.0 Ethernet controller: Red Hat, Inc Virtio net work device If so just try "ifconfig eth1 up", "ifconfig eth2 up" etc. The one that don't gives an error is your device you need to...

Okay so there's no eth0 device. I guess your system has another/new interface name (possibly eth1?) for your networkcard. Run: # ls /sys/class/net Then you should see something like: eth0 eth1 lo Change in /etc/network/interfaces to right interface name and reboot VM. If you only see 'lo'...