Replying to myself as I'm at office right now and can't check this feature/workaround.
The "failing" node is based on Core i5 2500M and to 2 "working" ones are based on Core i3 6100U and Atom C2538 (it's a VM only used as "virtual" 3rd node for HA).
It appears that only the failing one as Intel...
Thanks for your answer Fabian !
I understand downgrade is not a good solution but I try to solve the problem I have explained in this thread:
https://forum.proxmox.com/threads/pve-ha-lrm-keeps-failing.27261/
If (maybe) it comes from the testing packages I'd prefer to return in the "safe realm"...
I've tried to stop pve-ha-crm and lve-ha-lrm (which was already failed) in order to start failed watchdog-mux manually but:
root@pve2:~# systemctl start watchdog-mux.service
root@pve2:~# systemctl status watchdog-mux.service
● watchdog-mux.service - Proxmox VE watchdog multiplexer
Loaded...
Hello,
I've configured apt to use the pvetest repo. But is it possible to return to pve-no-subscription or pve-enterprise repos without reinstalling all nodes ?
Thanks in advance !
Hi Gosha. That's exactly what I did yesterday after posting on this thread. I've added a 3rd "virtual node" on the cluster and created a PHYS group on the 2 physical nodes and bound the VMs on this group :)
But now I have another issue with watchdog-mux and pve-ha-lrm services failing on one of...
Service pve-ha-lrm is online at boot even if softdog is not loaded and watchdog-mux failed:
root@pve2:~# systemctl status pve-ha-lrm.service
● pve-ha-lrm.service - PVE Local HA Ressource Manager Daemon
Loaded: loaded (/lib/systemd/system/pve-ha-lrm.service; enabled)
Active: active (running)...
I've followed this discussion: https://forum.proxmox.com/threads/4-1-ha-software-watchdog-reset-does-not-work.25474/
And it looks like I have the same symptoms. Right after a reboot, softdog module is not loaded and watchdog-mux is failed as well:
root@pve2:~# lsmod | grep softdog...
Hello,
I have a 3 nodes cluster based on pvetest. Nothing has been installed on pve nodes but proxmox distrib.
One of the node has its pve-ha-lrm failed all the time. It fails in few seconds when started from the GUI (or after reboot) with the following messages in syslog:
May 5 15:26:32 pve2...
The "virtual node" will run on a separate hypervisor on a NAS (phpvbox on x86_64). It will just be there for the quorum, that's why I have to take care no VM will migrate on it (inception syndrome ...).
Ok thanks, got the point (fencing) !
It explains the "with at least 3 nodes" requirement ...
But in my current situation, what will happen if a node crashes ? Will HA VMs restarted on the second node despite the "2 nodes" configuration or just nothing ?
Can I add a 3rd "virtual node"...
Hello all,
I'm quite new to proxmox and I directly started using 4.x (pvetest) for my lab@home few weeks ago.
I have a 2 nodes HA cluster with NFS/iSCSI storage provided by 2 NAS.
I've been able to configure my VMs to be live migrated in a few clicks (including storage), PM is quite impressive...
Hello,
First of all thanks a lot for this great piece of software !
I did not knew about Proxmox 2 weeks ago when I was about to set up a lab@home based on 2 NUC in order to play arround with ESXi. Main goal was to "consolidate" several virtualboxes/dockers (running on 2 Syno) and few...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.