Search results

Hello everyone, For information, we have solved our problem. Virtual machine network interfaces were no longer attached to vmbr1. Via the web interface, we attached them to vmbr0 then back to vmbr1 and everything is back to normal.

Hello everyone, I have a problem on a node of a Proxmox cluster. Interfaces and bridges appear to be well configured but VMs do not have network access. But the virtual interfaces of the VMs are not associated with the vmbr1 bridge. Does anyone have a guess on the problem? Thanks in...

Sorry, I did not post on the correct forum. I recreated the topic on the network forum.

Hello everyone, I have a problem on a node of a Proxmox cluster. Interfaces and bridges appear to be well configured but VMs do not have network access. But the virtual interfaces of the VMs are not associated with the vmbr1 bridge. Does anyone have a guess on the problem? Thanks in...

Hi, I don't have a "name" column : Do i miss something ?

The problem is solved. For information, following the reboot of the node, the network configuration was reinitialized and the CEPH storage was therefore unreachable.

Hello all, A node in my Proxmox cluster restarted this morning (I don't know why yet - in which logs should I look?). Since then, some VMs of this node have not been able to start: qm start 206 start failed: command '/usr/bin/kvm -id 206 -name be-eva -chardev...

I supervise the host and the container but as the container uses the host's CPU, I normally have the same values. I will find out about this option and try to configure it correctly. Thank you for the information.

Perfect. The nodes have been deleted: Thanks a lot for your help @Fabian_E !!

Hi @Fabian_E, I added a VM in the resources and the HA master has changed well but I always see the servers that I deleted :

I actually have no resource currently configured on the HA. So you think that if I configure one, the CRM services will activate and update everything?

Same output for each nodes :

On my Nagios + Centreon monitoring server. The incident is over on the be-resasmm container.

Hello, An LXC container had an incident (still undetermined) which caused a very large increase in its sysload average (36,32,19 on 1 CPU). This led to a very strong increase in the sysload average of the hypervisor that hosts it and consequently impacted all the other containers of this...

Hello, galaxie17 is no longer part of the cluster. It is one of the nodes that I removed. Do you want me to try the commands with galaxie6 for example?

I deleted the galaxie12 node folder but it is still present in the HA menu of the GUI.

Hello, Yes, there are still directories corresponding to deleted nodes: Do I have to delete them manually?

Hello, I deleted nodes from my Proxmox cluster following this doc. they are no longer members of the cluster but they are still visible in the HA menu of the GUI: Did I forget to do something? Thank you in advance for your help.