Recent content by jsabater

Thanks for reporting this. Good to know!

Thanks a lot for your report, @leiwang15 . Much appreciated. Incidentally, I found this thread on these forums regarding E1000E vs VirtIO on Proxmox.

Hi, Fabian. Thanks for the link to the bug tracker. I have contributed to it. I hope it can be solved soon.

This is what I do to remove a node (e.g., proxmox5) from the cluster (Proxmox 7.4-19) after the pvecm delnode proxmox5 command has finished its execution at another node (e.g., proxmox1) and the deleted node has been shut down: rm --recursive --force /etc/pve/nodes/proxmox5 sed -i.bak...

I have come up with these two solutions for my plays/provision.yml Ansible playbook, that provisions LXC in the Proxmox cluster: Reinstall all packages containing the setcap command: apt-get --reinstall install iproute2 iputils-ping libcap2-bin. Fix permissions of the affected binary: setcap...

I followed the same procedure when re-adding a re-installed node and the first time it went fine (pvecm updatecerts did the job). But the second time I had to re-add the same node, after re-installing it again due to hardware issues, it did not. So I had to go through all the...

I presume that you executed the command in the PVE node, not inside the VM, correct? Moreover, what other guests did you have in the node? I have a mix of VMs and LXCs and this behaviour only happens where I have VMs. Would that be your case, too?

In my case, it turned out that the firewall had gone crazy (for whatever reason). Restarting the firewall in the destination node (the one holding the VM that could not be contacted by the other VM) solved the problem. Kind of weird, to say the least.

For future reference, after hours of log-checking and dealing with firewall rules, network addresses, and all sort of tests using nmap, ping, traceroute, and more, it turned out that the firewall on the node where the destination VM was had turned crazy. Fortunately, the solution was quick and...

Hey everyone! I have a Proxmox 7.4 cluster with several nodes. Across them, there are two VMs, live and test, both based on Ubuntu 18.04, both with a private IP address for communication among LXCs and VMs, and with a public IP address to access the Internet. Firewall is open for specific ports...

Hi, @Veidit! I am facing a similar issue in which two VMs running Ubuntu 18.04 were migrated (via PBS) from a Proxmox 6 cluster to a Proxmox 7 cluster. The first can connect to the second, but the second cannot connect to the first. Both can be connected from a LXC I use as Ansible Controller...

Hi, @chris. I have been having random reboots of the two nodes hosting my big PostgreSQL database and my big MongoDB database, respectively. Both on LXC running Debian 11 on Proxmox 7.4. I have always suspected it was the heavy (disk?) load of either, but I have never been able to prove it. I...

Unless I have misunderstood you, yes, you would have to change all the IP addresses at once. Otherwise, they would not be able to talk to each other.

Okay, so I went through all the LXC in my cluster and only this one did not have a disk size in its configuration file, so I'll consider this a bug that happened for whatever reason. I stopped the container, edited the file manually to add the disk size, run pct fsck 109 and started the...

Alright, so for some reason this container does not have a size in its configuration file /etc/pve/lxc/192.conf, whereas others do (all those I have checked, which are not all there are). I will create a script tomorrow to check all the containers, see if this is just some exception. Question...