Search results

Hi, To help you better, please provide us with the Proxmox VE network configuration `cat /etc/network/interfaces` and the VM config `qm config <VMID>` replace the `<VMID>` with the ID of the VM mentioned. That can help us to identify if the issue is in the network config or the VM config.

If you want to know what happened exactly and how fixed the issue, you can post more information for the syslog/journalctl!

Glad to hear that you fix the issue yourself! If the old folder not needed, please move it to another path.

Yes. This won't help if the cluster itself loses quorum.

Hi, Could you please tell us which storage type your old Proxmox VE setup was using? e.g., ZFS, Ceph, or something else?

May you try to commit the `search local` in the `/etc/resolv.conf` and test ping google.com or 8.8.8.8?

Hi, Can you please check the `pct enter 101` of the LXC? And did you see other above provided output in the syslog? you can run `journalctl -f` and try to access the LXC Console in the Proxmox VE Web UI.

Ceph needs a MON majority for quorum; losing this halts operations.... An option is to add a lightweight `tiebreaker` node to the cluster, which doesn't need to store data but can maintain quorum. Plus consider using the `noout` flag during maintenance to avoid triggering recovery processes.

By default, a Ceph cluster requires a majority of nodes to maintain quorum! Note, with min_size=1, there is a risk of data loss if only one replica is available during a write operation.

Hi, Thank you for the outputs! Could you please post the output of `hostname -A` command as well? EDIT: and the output of the below command, please! ls /etc/pve/nodes

Hi, You could install the QDevice on a Raspberry Pi, it's an affordable way to provide the necessary 3rd vote for qourm without the need for a full node + will not cost like add a 3th node.

Hi, Our forum is only in German and English. Please consider posting in one of these languages to get a quicker reply.

Have you checked the firewall? if enabled. I would check the tcpdump to see where is the issue.

Hi, You need to assign PVEDatastoreUser on the PBS storage and PVEVMUser on the specific VMs they need access to. Please test these permissions to ensure they meet your requirements.

Hi, If you want to avoid quorum loss, consider installing QDevice [0] on a Raspberry Pi to maintain quorum with minimal power usage. [0] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_corosync_external_vote_support

Hi, Did you checked our wiki [0] regarding the network considerations? [0] https://pve.proxmox.com/wiki/Proxmox_VE_inside_VirtualBox#Network_Considerations

Hi, Did you try same your config but without `bridge_maxwait`? i.e.: auto lo iface lo inet loopback auto enp5s0 iface enp5s0 inet manual auto vmbr0 iface vmbr0 inet static address 192.168.86.204/20 gateway 192.168.86.1 bridge-ports enp5s0 bridge-stp off bridge-fd 0

Yes, should don't cause any problem. Since this was a solution for many users. And yes since you have enough RAM memory your server don't have to use the swap.

Hi, Did you check the syslog during the joining cluster? You can use `journalctl -f` to see the syslog for any interesting error or warning! Why you changed the SSH keys? Does the Proxmox VE servers have the same version?

Hello, You can disable swap in your node, that is was a solution of some users. You can stop/disable the swap using the following: To disable the Swap, run the following command: swapoff -a In order to disable it permanently, edit the /etc/fstab file and disable the following line by...