Recent content by ghusson

My ideas : Reliability : use several firewalls/routers, with VRRP protocol for example in order to have Active/Passive firewalls. Security : use dedicated cluster servers with low level hardware in order to avoid lateral attackers moves. You are welcome.

Nodes shouldn't do any function other than virtualization ( and maybe CEPH storage ). Thus one or several VMs should do routing / firewalling. Be careful with your overlapping networks as it can be dangerous (security) and prone to mistakes in network flow understanding.

@abhabitat : you didn't search in the forum, right ? https://forum.proxmox.com/threads/aer-correctable-error-message-received.156497/ ;)

Did you install a 5th node for quorum in case of split ? Is 172.16.8.0/24 your management network ?

Ok thank you for the info.

WARNING : YOU CAN LOOSE DATA, thus backup what you have to before doing this (example : VMs and /etc on each nodes) In order to FORCE local node operations : pvecm expect 1 Then you will have to pay attention to what you are doing in /etc/pve as it won't be synchronized to other hosts.

Yes, and I think that your corosync cluster speak on the management traffic. That's why I said it was expected. In order to avoid this, you should add a second ring for corosync on the other switch network.

Hello. Just to be precise : in case of no quorum, and if HA is unconfigured, then no host is rebooted and no VM is shutdown. You would simply be unallowed to do any modification on state (configuration, VM stop/start and so on). But if HA is configured and there is no quorum, each node is...

Hello. You could try to install a SNTP client on each VM ?

You can read this to understand : https://pve.proxmox.com/pve-docs/pve-admin-guide.html#ha_manager_fencing

Hello. Do you use HA ? If yes, the servers reboot was expected.

Conclusion : do not log as root if you think it is inconsistent :-)

Indeed it should work. And sadly there is plenty of reasons that can make it crash :-)

As I wrote : You should try a low level disk test.

Hello. The problem could be located to a kernel crash using bridges. But as seen many times in this forum with small form factor units, it rather comes from the processor. Can you try to : - re-enable bridges and reproduce the problem - put a fan on your miniPC in order to cool it well - tell us...